EnderDashAccess Model
Understand how organization roles, server grants, plan limits, and target capabilities combine to control what each person can see and do.
Membership and access are separate ideas
Being in an organization does not automatically mean full access to every server or page.
EnderDash evaluates access in layers:
- organization role
- server grant
- plan features
- target capabilities
That layered model is why two people in the same organization can see different pages or panels.
Organization roles
| Role | Typical meaning |
|---|---|
| Owner | Full organization control |
| Admin | Day-to-day operational control |
| Member | Access limited to what has been granted |
Owners and admins are the elevated roles.
What elevated roles can usually access
Elevated roles can typically access pages and actions such as:
- Downloads
- server creation and deletion
- agent-key rotation
- Billing
- Activity
- Ocelot Settings
- organization-wide member and grant management
Members should not expect those setup and administrative surfaces to appear.
Why a page or panel can still be missing
Even if a user has the right role, visibility can still depend on:
- whether they were granted access to the server
- whether the organization plan includes the feature
- whether the connected target exposes the capability behind that panel
That is why access questions and capability questions are related, but not interchangeable.
The most common source of confusion
The most common access complaint is:
I can see the organization, but not the server or panel I need.
That is usually a missing server grant, not a frontend bug.
Frozen servers
If an organization has more servers than its current plan allows — for example, after downgrading from a larger plan — the servers above the cap become frozen rather than deleted. EnderDash sorts the organization's servers by creation date and keeps the oldest ones active up to the plan's server limit. Anything newer than that is frozen.
A frozen server:
- appears in the servers list with a Frozen badge instead of Online or Offline
- cannot be opened, connected to, or acted on from the dashboard
- rejects new agent connections at the signaling layer
- can still be deleted by an admin
To restore access, delete servers until the total number of servers is at or below the plan's limit, or upgrade the plan. Once the organization is back within its cap, nothing is frozen. Frozen servers keep their configuration and agent key; they are not purged until an admin explicitly deletes them.
Related pages
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on