---
question: Who can open the Platform settings screen?
kind: overview
---

# Platform settings

Platform Settings is the screen for the platform itself. The account menu shows it only when `is_superadmin` is true. It opens `/settings`. Anyone else sees "Platform superadmins only".

It is not a workspace role and not an organization role. Organization roles are owner, admin, and member. Workspace roles are owner, admin, member, and viewer. Those are assigned on [Organization settings](/user-guide/platform/organization-and-members) and [Workspace settings](/user-guide/platform/workspace-settings).

![Platform Settings dashboard](/abi/Screenshot_Platform_Settings.png)

*Platform Settings. The dashboard lists the Nexus tables. This shot is the super-admin account.*

The header says Platform Settings. The Dashboard lists every table in the Nexus database. Search, sort, and filter any column. Clicking a row shows that table's schema; its name opens the table. Export downloads every table. The nav starts with Dashboard, then the groups People & access, Sign-in & security, Chat, agents & models, Apps, Code, Maps, Graph, Ontology, and Search. Each item is `GET /api/admin/tables/{name}`.

The tables are read-only, with one exception: under Users, a super admin can promote or demote another super admin (`PATCH /api/admin/users/{id}` with `is_superadmin`). In the config, `is_superadmin: true` on a `users:` entry only promotes; turning it off does not demote.

The same menu has Account Settings. That is the profile and appearance page (`/account/profile`), not this screen. See [Account](/user-guide/platform/account).

Events and System on the dock are also limited to super admins. They are workspace sections, not this page. System is described on [Orientation and navigation](/user-guide/get-started/orientation).

A generated project sets `is_superadmin: true` on `admin@example.com`. That is the account in [Authentication](/user-guide/get-started/sign-in).