Sharing connectors
Access profiles — giving people access to specific sources.
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.
- Name it after the group, not the content — "Platform team", not "backend repos". Membership outlives any particular source.
- Add connectors
- Add people
- Pick a level
Levels
| Level | Can |
|---|---|
| Read | Find and read the content |
| Write | Read, and edit content from those sources |
| Manage | Read, write, and change the connector's settings |
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.
Prefer profiles over making things global. Global is not reversible in any meaningful sense — once everyone has seen it, unsharing does not unsee it.