AllProtocolCommunity
Most recentAll versions (59)

Files authority — governs saving files into the Files connector on this computer and looking them up. Saving takes a file from the shared folder and keeps an unchangeable copy; nothing leaves the computer. Sending a saved file is governed by the email profile, which names the files it may attach. No content binding: saving leaves nothing outside.

Records authority — governs accessing and managing personal structured data

Customer authority — governs CRM operations: contacts, activities, deals, tasks

Delegation authority — lets an agent propose changes to its own setup: the agent brief and new mandates. Every proposal waits for a person's approval; nothing takes effect before it. Also lets the agent read the setup guides.

Payments authority — governs collecting money from customers through a payment provider: payment links and payments, seeing whether money came in, and managing payment customers. Invoices and credit notes are Invoicing; refunds, subscriptions and outgoing money are not covered.

Purchase authority — governs spending company money: subscriptions, supplies, services, advertising

Calendar authority — governs calendar access: reading, drafting, and booking events

Publishing authority — governs posting public content to social media, blogs, and other platforms

Reporting authority — lets an agent read the evidence a gateway holds (tickets, approvals, mandates, records in the systems it connects) and write one report stored on that machine. Changes no system.

Sales authority — governs quote-to-order in an ERP: draft quotes, send quotes to customers, convert quotes to orders. No invoicing, delivery, payments or master data.

Master data authority — governs the customer records and the catalogue that quotes and invoices are built from: creating and changing customers, and creating and changing catalogue items. A change to a customer's tax data (name, address, country, VAT ID) and a change to an item's price or VAT rate are each a decision of their own. Kept apart from invoicing and sales so that the people who issue documents are not the ones who change the data behind them. A change to a customer's payment data (bank account / IBAN, payment terms, credit limit, dunning or payment method) is its own decision too — the classic entry point for payment fraud; it is governed here wherever a connector offers such a change (ERP Local offers none). Every action in this area is reviewed by a person. No invoices, quotes or payments.

Email authority — governs sending, drafting, and reading email via Gmail

Authority to make an already-built version live. Successor to deploy@0.6, which gated 'build and deploy this commit'; this gates the act of putting something in front of real users, because building is not consequential and going live is. The action is a RELEASE: it activates bytes that already exist, so the human can look at the artifact before approving and no rebuild can diverge from what was approved. Host-agnostic — the artifact identifier is a Vercel deployment id, a container image digest, an Azure slot — named by the connector manifest, never here.

Invoicing authority — governs issuing invoices and credit notes in the invoicing system (ERP). An issued invoice is never changed or deleted: a cancellation or correction is a credit note with its own number, as German and Austrian law require. No payments, reminders or master data.