product-example 1 linked patterns checked
Atlassian Support: Assign space permissions in Confluence Cloud
Documents adding and removing users, groups, guests, and anonymous access in Confluence space permissions, checkbox permission matrices, additive permission behavior, View, Add, Delete, Restrictions, Export, Space Admin permissions, and revocation requirements.
Read with a purpose
What this source can teach
Use this source to inspect a concrete implementation and the decisions visible in its context.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Permission sharing | Choose permission sharing when users manage durable access grants, role assignments, group permissions, effective access, inheritance, anonymous access, or revocation for a protected resource. | Opening the permission sharing surface loads direct grants, inherited grants, group or team grants, anonymous access, service credentials, and owner or admin constraints before edits are saved. | Atlassian documents user, group, guest, anonymous, additive, matrix, revoke, and individual permission behavior in Confluence spaces. |
Comparisons supported by this source
- Permission sharing vs share dialog vs invite user vs permission recovery
Atlassian documents user, group, guest, anonymous, additive, matrix, revocation, and individual permission behavior in Confluence spaces.
Evidence Role
This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.
Publisher: Atlassian Support. Last checked: .