durin
Book A Demo
Knowledge base
Recipes

Scope a connection to a team

Make one installation available only to its assigned teams.

Admin2 min readUpdated

Assign the scope

Prepare the team and its membership before changing connection access.

  1. Open the connection in the Admin workspace.
  2. Use the team scope editor to assign the intended group or groups.
  3. Save and have an assigned member run a reviewed read with their own provider authorization.
  4. Confirm a member outside every assigned team cannot use that connection.

Restrict requests within the team

Connection scope controls who can reach an installation. For narrower rules, open Organization → Teams → the team → Policy and add a conditional rule for a tool, resource prefix or principal. Review inherited restrictions and the generated JSON before publishing.

Troubleshooting

A person retains access after leaving a team

Check their other team memberships and confirm directory changes have synchronized. Also check whether the installation now has an empty, organization-wide scope.

Frequently asked questions

What if a person belongs to two teams?

Membership in either assigned team can satisfy connection scope. Team policy denials and all other access checks still apply.

Are administrators exempt?

No. Administrators can inspect installation settings, but using a scoped connection still requires team access.

Try Durin with your MCP workflow.

Book a demo to explore agent access, policy checks, approvals, and audit records with our team.

Book a demo

Choose which optional purposes this browser allows. Cookies that keep the site working, keep you signed in and remember this choice are always on, as is the referral cookie a referral link sets for up to 90 days. Your choice is stored in a first-party cookie for 180 days. Saving a choice that turns analytics off reloads this page if analytics was running on it. Read the privacy notice.