EnderDash

Missing servers, pages, or panels

Check membership, server grants, plan limits, and agent capabilities in order.

Check the four requirements

  1. Organization: select the organization that owns the resource and confirm accepted membership.
  2. Server grant: a member must be assigned to the server. Owners and admins have elevated access.
  3. Plan: confirm the needed feature and whether the server is frozen.
  4. Capability: the connected agent must report support for the panel or action.

Do not use another person's key or session to work around a missing grant. Ask an owner or admin to correct the access.

If Setup is missing

Setup and key management require owner or admin access. A member's server grant does not allow key rotation or record administration.

If an organization page is unavailable

Members need the team-collaboration feature for organization workspace operations. Alert configuration, audit history, publication settings, and Ocelot settings require elevated access as described in their guides.

An organization admin is not an EnderDash platform admin. Admin > OAuth Clients uses the separate platform role.

If one server panel is missing

Check server panel requirements. Confirm that a required companion plugin is installed and loaded. Check Info for the runtime identity before assuming the agent is a Paper backend.

A proxy cannot provide the backend world's metrics. A native host does not provide a game-console capability. A container socket must be usable before the agent can manage that daemon.

If the record is Frozen

Use plan and frozen-server recovery. Reinstalling the agent does not increase the organization allowance.

Next: invite and grant access or platform tools.

Was this page helpful?

Send a quick note if anything is missing or unclear.

Last updated on

On this page