Understand access
Connecting an app and granting access are separate decisions.
Effective access is determined in this order:
- The app must be executable and available to the workspace.
- The app must have a usable shared or personal connection.
- Group and direct user policy add allowed apps or individual tools.
- Explicit tool restrictions remove access.
- Tool risk and confirmation rules still apply when a call is made.
An explicit restriction is not overridden by adding the same tool through
another group.
Roles
Roles control administrative capabilities such as managing billing, apps,
members, policy, and Audit. Roles do not by themselves mean that every provider
tool should be available.
App grants and tool grants
An app grant is broad: it includes the tools currently allowed for that app.
Use it when the group genuinely needs the application as a whole.
A tool grant is narrower. Prefer it for workflows that need only a few reads or
when the app also exposes write-capable operations.
Groups and direct policy
Use groups for access shared by a job function or team. Use direct user policy
for exceptions with a clear owner and review date.
Before saving a change, review Effective access for the affected user.
After saving, run a bounded test and inspect Audit.
Restrictions and confirmation
Restrictions are appropriate when an otherwise useful app exposes a tool a
group should never use. Confirmation is a separate runtime safeguard for
operations that require an explicit decision before execution.
Neither replaces provider-side least privilege. The credential itself should
also be limited to the intended tenant and permissions.