This page is part of the AeThex documentation system.
+
Teams group organization members so access can be managed by responsibility instead of one person at a time.
-
> [!NOTE]
-
> This article is a placeholder and should be expanded.
+
<div class="docs-section-heading">
+
<h2>Team model</h2>
+
<p>Teams make permissions easier to understand, review, and revoke.</p>
+
</div>
-
{{PageIndex}}
+
Teams usually exist inside [[Organizations]]. They can represent departments, project crews, maintainers, moderators, developers, artists, operators, or support staff.
+
+
## Common teams
+
+
- Owners or administrators.
+
- Developers and maintainers.
+
- Support or moderation staff.
+
- Studio or content teams.
+
- Security reviewers.
+
- Community managers.
+
+
## Access workflow
+
+
1. Add users through verified identities.
+
2. Assign them to teams by responsibility.
+
3. Grant teams access to projects or resources.
+
4. Review access during role changes.
+
5. Remove users from teams when access is no longer needed.
