Permissions
Workspace admins set agent policy per role in Settings → Permissions. Members inherit the bundle for their role. They cannot raise their own ceiling from the chat composer.
Tool classes use Deny, Require approval, or Allow from the outline control. Grant approvals is a privilege checkbox, not a tool row.
Open Permissions
- Open Settings from the footer account menu.
- Select Permissions in the settings rail (its own section, not under Team).
You need manage team or an admin role to edit bundles. Everyone else sees read-only policy.
Role tabs
The strip runs Admin → Creator → Editor → Viewer, plus any custom roles you add. Pick a tab to edit that role only. Changes save for the whole workspace.
Reset to default restores the built-in bundle for the active tab.
Agent chat modes
Checkboxes set which chat modes the role may pick in the composer:
| Mode | Typical use |
|---|---|
| Read only | Safest. Table reads only |
| Ask | Default posture. Risky tools pause for approval |
| Allow session | Wider session allowance after confirm |
| Full access | Widest Appenda tool allowance (Admin / Creator only by default) |
Members only see modes their role allows. Full access is hidden for Viewer and Editor unless an admin enables it.
Tools
Each row is a tool class with Deny, Require approval, or Allow:
| Tool class | Covers |
|---|---|
| Tables (read) | Read tools on table data |
| Tables (write) | Row mutations |
| Tables (create/delete) | Create or delete tables |
| Fields (add/delete) | Schema changes on a table |
| List import | Search jobs that add many rows |
| Enrichment run | Paid provider column runs |
| Agent filesystem | Native adapter file access (off by default) |
| Agent terminal | Native adapter shell access (off by default) |
Editor defaults (typical): list import Allow, enrichment Require approval, agent filesystem and terminal Deny. Admin and Creator match similar safe defaults for native adapter tools.
Require approval sends the turn to an approval card when the active chat mode does not already auto-allow the call.
Runs without approval
Rows per run caps how many rows a role may touch in one enrichment or bulk write before an approval card appears, even when the tool class is Allow.
Privileges
Privileges are separate checkboxes. They gate workspace admin actions, not a single agent tool call:
| Privilege | Meaning |
|---|---|
| Invite members | Send workspace invites |
| Manage team | Edit roles and Permissions |
| Create API keys | Workspace API keys |
| Export lists | Table export actions |
| Delete workspace | Destructive workspace delete |
| Manage agent access | Provider allowlists under Settings → Agents |
| Grant approvals | Resolve pending approval requests and save durable grants |
| Configure integrations | Integration policy under Settings → Integrations |
| Manage billing | Plan and billing screens |
Grant approvals is a privilege only. It does not appear as a Deny / Require approval / Allow tool row.
How Permissions fits chat and approvals
| Layer | Where | What it controls |
|---|---|---|
| Permissions | Settings → Permissions | Role ceilings for modes and tool classes |
| Chat mode | Agent composer | Session posture for this tab |
| Runtime cards | In chat | One tool call that still needs an answer |
Chat mode cannot bypass Deny. Require approval still shows cards unless the mode and run limits already cleared the call.