Sharing Individual Resources
Roles control what a member can do across a whole organisation or project. Sometimes you want to give one person access to a single resource — one container, one registry, one secret — without changing their role. That's what sharing does.
Roles control what a member can do across a whole organisation or project. Sometimes you want to give one person access to a single resource — one container, one registry, one secret — without changing their role. That's what sharing does.
Sharing is additive: it only ever adds access to that one resource. It never removes anything a member already has through their role, and it doesn't affect any other resource.
How it works
Open the resource you want to share (for example a container's detail page) and choose Share access. Then:
- Pick an existing organisation member.
- Choose which permissions to give them on this resource — Read, Create, Update, or Delete.
- Share.
The member immediately gains exactly those permissions on that one resource, on top of whatever their role already allows.
You can only share with people who are already members of your organisation. Invite them first if they are not.
Who can share a resource
Anyone who can already manage the resource can share it. In practice that means owners and admins, members whose role lets them manage that resource, and anyone the resource has already been shared with at the Update level.
Seeing and removing access
The share panel lists everyone who currently has direct access to the resource, along with the permissions they were given. To remove someone's direct access, revoke it from that list. Revoking only removes what sharing added — it never touches the access they have through their role.
Sharing vs roles
- Use roles for ongoing, organisation- or project-wide responsibilities (see Team Management).
- Use sharing for one-off, resource-specific access — handing a single container or credential to one person without widening their role.