Sharing connectors

An access profile shares specific connectors with specific people, without changing anyone's role.

This is how you give someone access to one repository rather than to everything, or to nothing.

Why this exists

Roles decide what someone can do. Ownership decides what they can see. If those were the only two controls, sharing one private connector would mean making it global — visible to everyone — or promoting the person to an administrator.

Access profiles are the middle ground, and they are how most real sharing should happen.

Creating one

Settings → Access profiles → Create.

1. Name it after the group, not the content — "Platform team", not "backend repos". Membership outlives any particular source.
2. Add connectors
3. Add people
4. Pick a level

Editing one

The pencil on a share's row opens the same dialog pre-filled. You can rename it, change the level, add or remove connectors, and change who it reaches. The people list you save replaces the current one, so removing an address from the field removes that person's access as soon as you save. Only the owner of a share can edit it.

Levels

Each includes the ones above it.

How it interacts with everything else

Access profiles only ever add visibility. They never remove it.

• Global content is already visible to everyone; a profile changes nothing
• Personal content becomes visible to profile members
• Nobody loses access because of a profile

Removing someone from a profile removes that access immediately, including for any API keys they hold.

A worked example

An engineer connects a private repository to work with their agent. A colleague joins the project.

Without a profile: the connector is personal, so the colleague finds nothing. Making it global exposes it to the whole company.

With one: create "Project Atlas", add the connector, add the colleague at read level. They can find it; nobody else can. When the project ends, delete the profile.