A call must pass all three, and the session’s permission profile too. See How an integration call is checked.
Limit a connection or a custom type
A policy on a connection applies to everyone who calls through it: you, your teammates, and Script.it itself, such as a Slack bot posting status updates. Built-in integrations take a connection policy only. A custom integration type can also carry a type policy that limits all of its connections.1
Open the integration
Go to Settings → Integrations. Open the ⋮ menu on the connection and select Edit.
2
Find the policy
The modal shows Permission policy for this connection. For a connection of a custom type, it also shows Permission policy for all type connections. Each one is marked Restricted or Unrestricted.
3
Choose what's allowed
Set the integration’s row to Deny, Only listed, or All. With Only listed, select Add rule, describe it, and add the requests it allows.
4
Save
Select Save Changes. Script.it checks the policy before it stores it, and every later call meets it at once.
What the row states mean
Each rule has a plain-English description and one or more requests. A request is Any endpoint or a URL, with the methods it allows, such as
GET.
Describe a change instead
Under the policy, type what you want into Describe a change to this permission policy… and stage it. Script.it closes Settings and puts the request in the chat composer, naming the policy, so the agent makes the change with you. Nothing is sent until you send it.Edit the YAML
The policy has a YAML view for conditions the rows don’t show, such as limits on a request’s query or body. Here is a policy that lets a HubSpot connection read and nothing else:The policy format
A policy is a list ofallow rules and, optionally, deny rules. A request is allowed when an allow rule matches it and no deny rule does.
- Every rule names its integration under
resource. A connection’s or a type’s policy names only the integration it’s stored on. - Every allow rule needs a
descriptionin plain English, written for the people the policy affects. call: "*"allows every request. Otherwisecallis a list of request entries, and a request is allowed when every condition of one entry matches.- A deny rule refuses every call to its integration.
Two rules about meaning:
- No policy limits nothing. An empty policy allows nothing.
- Allow rules add up. Two allow rules whose scopes overlap without being equal are refused, because the narrower one would limit nothing.
scriptit CLI. The agent’s own permissions skill has worked examples for common integrations, so you can ask it to write one with you.
Integration calls for members and roles
Integration calls are your organization’s limit on a person, not on a connection. They follow the member across every integration they reach, including connections teammates shared with them. Each connection’s own policy still applies on top. Set them in Settings → Organization:- For a role: select Roles, pick the role, and find Integration calls under Integrations.
- For one member: open the member’s permissions from the member list.
- Integration calls bind the member and everything they run: sessions, Agents, scripts, triggers, and the CLI.
- Changing a role’s Integration calls reaches everyone with the role right away. A member who was given their own keeps them.
- Only holders of Manage integration permissions change them. Owners and Admins hold it by default, and the Member role never can.
- They never apply to the Owner, a Personal account, or a guest.
When a policy refuses a call
The call fails, and the error names what refused it: the session’s profile, the type’s policy, the connection’s policy, or your organization. Retrying the same call fails the same way.- If a connection’s or a type’s policy refused it, ask one of its editors to change the policy.
- If your organization refused it, an Owner or Admin changes your Integration calls. Switching your session’s profile doesn’t lift it.