Locate yourself in the account structure
Sessions, clusters, and workspaces all sit inside an organization, the account that owns workspaces, holds the pricing plan, and forms the boundary for billing and membership.
Three minutes of looking at your own account tells you more than a diagram would.
Try this
Open your organization. Answer these from what is on screen:
1. What is the organization called, and how many workspaces does it own?
The dashboard lists them. This is the boundary everything else lives inside.
2. What role do you hold?
Find yourself in the member list. The answer determines the next question.
3. Which of these can you actually do?
Look for the controls, do not click them:
| Can you… | If yes, you hold at least |
|---|---|
| See workspaces, dashboards, activity | viewing access |
| Open a session, launch a cluster | using access |
| Create or delete a workspace, invite someone | administering access |
| Change the plan | ownership |
Where the controls stop is where your role stops.
The property that surprises people
Not merely what you can see. A member who can view a workspace may not be able to delete it, change its plan, or invite others into it.
So hold the narrowest role that lets you work. Widening access later is a two-minute conversation. Recovering a workspace someone deleted is not.
Current role definitions are in the administration documentation, which stays authoritative as they change.
One fact worth carrying forward
Plan limits apply at the organization level, so workspaces share the ceiling.
Two teams in separate workspaces have isolated environments, with separate storage and separate libraries, but they draw on the same plan. A team running hard against the limit affects the others.
This matters because the symptom is slow session and cluster starts, which people report as "the platform is slow" rather than "we are at a limit." If you ever hear that, this is the first thing to check.
Membership is at the organization, not the workspace
Adding someone is an invitation to the organization. Workspace access follows from it, and each person gets their own sessions. Nobody shares a session.
They do share workspace storage, which is why teams need an output convention. That is covered properly in onboard your first member.
What you now know
- Your own organization, role, and where your permissions stop, checked rather than assumed.
- That roles govern change rather than visibility.
- That workspaces share the plan ceiling even though they isolate environments, and that this shows up as apparent slowness.
Next: plans, limits, and what they govern, the one distinction that explains most billing surprises.
The operational side (inviting people, assigning roles, watching spend) is covered by workspaces & organizations, written for whoever owns those decisions.