Blame
|
1 | # Teams |
||||||
| 2 | ||||||||
|
3 | Teams group organization members so access can be managed by responsibility instead of one person at a time. |
||||||
|
4 | |||||||
|
5 | <div class="docs-section-heading"> |
||||||
| 6 | <h2>Team model</h2> |
|||||||
| 7 | <p>Teams make permissions easier to understand, review, and revoke.</p> |
|||||||
| 8 | </div> |
|||||||
|
9 | |||||||
|
10 | Teams usually exist inside [[Organizations]]. They can represent departments, project crews, maintainers, moderators, developers, artists, operators, or support staff. |
||||||
| 11 | ||||||||
| 12 | ## Common teams |
|||||||
| 13 | ||||||||
| 14 | - Owners or administrators. |
|||||||
| 15 | - Developers and maintainers. |
|||||||
| 16 | - Support or moderation staff. |
|||||||
| 17 | - Studio or content teams. |
|||||||
| 18 | - Security reviewers. |
|||||||
| 19 | - Community managers. |
|||||||
| 20 | ||||||||
| 21 | ## Access workflow |
|||||||
| 22 | ||||||||
| 23 | 1. Add users through verified identities. |
|||||||
| 24 | 2. Assign them to teams by responsibility. |
|||||||
| 25 | 3. Grant teams access to projects or resources. |
|||||||
| 26 | 4. Review access during role changes. |
|||||||
| 27 | 5. Remove users from teams when access is no longer needed. |
|||||||
| 28 | ||||||||
| 29 | <div class="docs-grid"> |
|||||||
| 30 | <a class="docs-card" href="/Organizations">Organizations</a> |
|||||||
| 31 | <a class="docs-card" href="/Projects">Projects</a> |
|||||||
| 32 | <a class="docs-card" href="/Permissions">Permissions</a> |
|||||||
| 33 | <a class="docs-card" href="/Profiles">Profiles</a> |
|||||||
| 34 | </div> |
|||||||