Blame
|
1 | # Organizations |
||||||
| 2 | ||||||||
|
3 | Organizations are shared administrative spaces for people, teams, projects, permissions, and platform resources. |
||||||
|
4 | |||||||
|
5 | <div class="docs-section-heading"> |
||||||
| 6 | <h2>Organization model</h2> |
|||||||
| 7 | <p>Use organizations when work needs shared ownership instead of a single personal account.</p> |
|||||||
| 8 | </div> |
|||||||
|
9 | |||||||
|
10 | An organization can represent a company, studio, community, foundation group, lab, internal team, or project owner. It provides the boundary for access control, project grouping, billing or operations, and audit history. |
||||||
| 11 | ||||||||
| 12 | ## What organizations contain |
|||||||
| 13 | ||||||||
| 14 | - Members and roles. |
|||||||
| 15 | - [[Teams]] for grouped access. |
|||||||
| 16 | - [[Projects]] and project resources. |
|||||||
| 17 | - API credentials and integrations. |
|||||||
| 18 | - Policies and operational records. |
|||||||
| 19 | ||||||||
| 20 | ## Admin checklist |
|||||||
| 21 | ||||||||
| 22 | 1. Define the organization owner. |
|||||||
| 23 | 2. Invite members through verified identities. |
|||||||
| 24 | 3. Use teams for repeatable access patterns. |
|||||||
| 25 | 4. Grant least-privilege roles. |
|||||||
| 26 | 5. Review access during team or project changes. |
|||||||
| 27 | ||||||||
| 28 | <div class="docs-grid"> |
|||||||
| 29 | <a class="docs-card" href="/Teams">Teams</a> |
|||||||
| 30 | <a class="docs-card" href="/Projects">Projects</a> |
|||||||
| 31 | <a class="docs-card" href="/Permissions">Permissions</a> |
|||||||
| 32 | <a class="docs-card" href="/Multi-Tenancy">Multi-Tenancy</a> |
|||||||
| 33 | </div> |
|||||||