Organization

What this menu is for

Organization is where admins structure the workspace: members, teams, roles, projects, guests, and workspace boundaries.

Good organization hygiene improves cost allocation, alert ownership, approvals, audit trails, and reporting.

Tabs

• Teams: group users around operational ownership.
• Members: invite, review, and manage internal users.
• Roles: control permissions with least privilege.
• Projects: map usage and spend to the right product or initiative.
• Guests: provide limited external access when needed.
• Workspaces: manage workspace-level structure and context.

Recommended operating model

1. Create projects before major production rollout.
2. Map teams to ownership areas.
3. Assign roles based on job responsibility, not convenience.
4. Use guests only when external collaboration is required.
5. Review membership and elevated roles regularly.

Security practices

• Keep owner and admin seats limited.
• Prefer role-based access over shared accounts.
• Remove inactive users quickly.
• Use Security for SSO, SCIM, MFA, audit, and compliance controls when available.
• Use Settings for retention and privacy posture.

How it affects other menus

Projects and teams improve Costs, Guardrails, Alerts, Optimizations, and Reports. Role policy controls whether users can mutate sensitive settings such as provider keys, reports, integrations, billing, and security posture.