Access Control

Access control in Duckie is layered. Workspace roles control human access, API keys and MCP scopes control machine access, connected app permissions control external data, agent tool access controls what agents can do, and approvals add review before sensitive side effects.

​

Start With Workspace Roles

Manage teammate access from Team Members & Roles. Use roles to separate responsibilities: Create custom roles when a built-in role is broader than the job requires. Review roles regularly, remove departed users, and keep the number of admin users small.

​

Separate Human Access From Machine Access

API keys are for integrations and external clients, not individual teammate login. Create API keys in Settings -> API & MCP. Each key has a name, scopes, creator, created time, last-used time, expiration, and status. The full key is shown only once; after creation, Duckie stores a hash and preview. Use separate keys for separate integrations so you can:

• Grant different scopes.
• Rotate one integration without affecting another.
• Set different expiration schedules.
• Revoke unused or compromised access quickly.

Duckie rejects revoked, expired, or insufficient-scope API credentials.

​

Scope API and MCP Clients

Duckie API keys use scopes. Customer API scopes control direct /api/v1 requests, while Duckie Assistant MCP scopes control the first-party MCP core object tools. MCP clients see only the wrapper tools allowed by the credential’s scopes. Prefer read-only scopes unless the client must create or update Duckie configuration. Learn more in MCP and API-Key Management.

​

Limit Connected App Access At The Source

Connected apps determine what Duckie can read or update in external systems. Before connecting an app, decide which account, workspace, project, repository, channel, or knowledge source should be available. Use Connections to manage integrations, and use provider-side permissions where possible. For example, connect accounts and tokens that have only the external access needed for the intended agent workflow. For supported app categories, see Supported Integrations.

​

Limit What Each Agent Can Do

Tool access is configured per agent and for the internal assistant. Enable only the tools that match the agent’s job. For agents that can update customer records, combine tool access with Account-Safe Actions, workflows, and approvals.

​

Require Approval For Sensitive Actions

Use approval before sensitive or high-impact changes, especially when a tool can:

• Change billing, plans, entitlements, account ownership, or security settings.
• Send a customer-visible message.
• Update external systems.
• Delete, close, resolve, or transfer records.
• Change Duckie configuration through MCP write tools.

Custom tools can be marked as write actions and configured to require approval before execution. When approval is enabled, a run can pause until the action is approved or rejected. See Write Actions and Approvals for custom tools.

​

Review Run History

Use Run History to review what the agent did. Run details show the triggering conversation, execution steps, knowledge retrieved, tool calls, inputs, outputs, status, and final response. For access reviews, sample recent runs for agents with write tools or broad knowledge access. Confirm that the agent used expected tools, record selectors, and guardrails.

​

Least-Privilege Checklist

​

Related Docs