Start here as an administrator or support colleague¶
Administration begins by identifying the scope of the problem. A personal account, organization membership, product assignment, workspace lifecycle and platform service are different responsibilities.
An organization administrator manages their own workspace. Platform staff have separately assigned support, commercial and operational powers. Entering an administration console does not grant permission to perform every action it contains.
Draft and availability: The detailed guides follow reviewed source behavior and intended final-screen journeys. Tenant Admin management controls and several staff experiences remain unfinished; the inspected Tenant Admin frontend is outside the initial staging rollout. These pages do not establish a live administration experience.
Find the right administrative path¶
| Need | Start with |
|---|---|
| Establish a new organization and its owners | Organization setup |
| Investigate access, payment or lifecycle confusion | Access, billing and lifecycle |
| Invite people or decide membership requests | Account invitations and joining |
| Review a member, product access or retained assignment | Membership administration |
| Maintain branches or organization-head designations | Workspace structure |
| Set workspace-wide access requirements and calendar | Access policy |
| Review licensed capacity and usage | Usage and capacity |
| Review a commercial change, payment or invoice | Billing |
| Understand platform-staff authority | Staff roles and support responsibilities |
Use the capability map for process, document, assistance and reporting administration beyond these starting areas.
Establish authority before changing access¶
Confirm the workspace, the person or item, the intended change and your actual authority. An organization-head designation is distinct from an administrator role, and signing authority is distinct from voting or membership.
The current member-removal and branch-deactivation paths do not universally protect the last accessible administrator. Arrange another eligible administrator before a change that could remove administrative access. Follow the precise membership and branch guidance rather than assuming a safeguard will reject every risky change.
Access changes can affect unfinished work and retained allocations. Involve the process owner when a person leaves or changes responsibility. Membership deactivation does not automatically transfer all tasks or release every add-on assignment.
Confirm the outcome at the owning layer¶
A saved invitation still needs its recipient's acceptance. A purchased capacity increase still needs application and, where relevant, assignment. A restored workspace does not reactivate an independently deactivated account.
After an uncertain response, check the original action and current saved state before repeating it. A changed preview page is not evidence that the connected service saved the change. The canonical task guide identifies the current implementation differences.
For background work, distinguish acceptance, processing and final application. A service health indicator answers a different question from successful completion of a particular customer action.
Support with useful evidence¶
Collect the environment, workspace, affected account or business item, attempted action, approximate time and visible result. Share the minimum necessary through the authorized support route.
Do not request passwords, one-time verification codes or browser-session credentials. When guided support is appropriate, follow the public explanation of its boundaries and the user's Support ID guidance. Refreshing the identifier does not end an active session.
Staff procedures, engineering references and operational recovery commands remain in private GitHub documentation for authorized readers. Public role explanations do not grant staff authority or disclose a new recovery bypass.
Keep configuration and instructions current¶
When a policy, role, commercial arrangement or lifecycle behavior changes, identify which people and work are affected. Update the appropriate instructions and verify the actual result before communicating completion.
Use governance and commercial responsibilities and process ownership to coordinate the business consequences. Keep deployment and reader acceptance separate from a successful source review or a saved setting.