Organizations Overview

An organization is the billing and ownership boundary in the portal - the thing that owns your invoices, your payment methods, your team, your API keys, and the projects underneath. 

• Most pages under an organization are role-gated. Owners and admins see everything; billing sees billing-only; technical members see resources but not billing; read-only members can view but not change anything. The exact mapping is in Roles and Permissions.

The active organization is named at the very top of the sidebar. Below it are the org-level links - Billing, Team, API Keys, BGP, Settings - followed by the projects in this org, and your profile button at the bottom.

If you belong to more than one organization, click the org name at the top to open the switcher. The sidebar reloads with the new org's data - its projects, its billing, its team. Only one org is loaded at a time.

For switching specifically, see Switching Between Organizations.

The dashboard at /dashboard is the default landing page when you switch into an organization. It gives you the at-a-glance summary across the whole org:

1. Resources: total count of VPS, dedicated, transit, etc., across all projects.

2. Billing: outstanding balance, credit balance, and the next invoice date.

3. Team: member count and any pending invites.

4. Recent activity: the last few entries from the activity log, with a link through to the full log.

Anyone with any role on the org can see the dashboard; the cards each respect the same role checks as the underlying pages, so a billing-only member won't see resource details and vice versa.

Invoices, payment methods, credits, and services subscribed to. The full walkthrough is Billing Overview.

Visible to: owners, admins, and members with the billing role.

Programmatic tokens scoped to this organization. Keys belong to the org, not to a person, so they keep working when an individual leaves. Each org can have up to 10 active keys at a time.

The page has two tabs:

• Keys: list of active and revoked keys, with scopes, IP allowlist, last-used time. See Creating an API Key and Rotating and Revoking an API Key.
• Activity: every request a key has ever made, charted and filterable. See API Key Activity.

Visible to: anyone with a role that can create or view keys. The Activity tab is gated separately to owners and admins (it exposes sensitive request data).

ASNs, peers, and prefix lists for customers running IP transit. Most accounts won't see this - it only matters if you've ordered transit. See the networking section for the full set of BGP docs.

Visible to: owners and admins.

The catch-all configuration page for the organization. It opens with a row of tabs across the top:

• Details: org name, type (personal or business), legal entity, billing address, tax ID.
• Team: same data as the Team sidebar link, reached a different way.
• Projects: list, rename, or delete projects.
• Security: 2FA requirement, claimed domains, SSO settings. See Requiring 2FA for Your Organization and Verifying a Domain.
• Domains: claim and verify email domains for your organization.
• Activity: the organization activity log. See Organization Activity.

Mentally, an org is four pools of state:

1. Identity: the legal entity and the address. Lives under Settings > Details.
2. Money: invoices, payment methods, credits, refunds. Lives under Billing.
3. People: members, roles, invites. Lives under Team (and Settings > Team).
4. Resources: the actual servers and services. Lives under each project.

Almost any task in the portal maps to exactly one of these. If you're not sure where to look for something, ask "is this about identity, money, people, or resources?" and the answer points you at the right sidebar entry.

Every member of an organization has one role. The role decides which sidebar entries they see and what they can do inside each.

• Owner: full control. Can transfer ownership, delete the org, change anything.
• Admin: full control except transferring or deleting the org.
• Billing: sees Billing and can pay invoices, manage payment methods, etc. Doesn't see resources or team management.
• Technical: sees projects and resources they're scoped to, but doesn't see Billing.
• Read-only: sees projects and resources they're scoped to, but doesn't see Billing. Cannot interact with resources.

A Technical or Read-only role can also be scoped to specific projects - a contractor might be Technical on the Production project only. For the full matrix, see Roles and Permissions.

Two things only the owner can do, and they're not advertised loudly anywhere else in the portal:

• Transferring ownership to another member. The new owner must already be in the org as an admin. See Transferring Ownership.
• Closing the organization. From  Account on the bottom left > Organizations > Trash icon next to the org name. The org has to have no active resources and no outstanding invoices.

If you're the only person in the org and you need to leave, transfer first, then leave - you can't leave an org you own.

• 2 organizations owned per account. Membership in others is unlimited.
• 3 projects per organization by default. Contact support if you need more.
• 10 active API keys per organization.
• Up to 5 claimed domains per organization.