> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/ixhello/administration/access-control.md). # Access Control Access Control manages elevated administrative access. Visible to SuperAdmins only. Contains two tabs: Super Admins and Org Admins. ### Super Admins Tab


Column	Description
Email	Login email address. Sortable.
Full Name	Display name. May be blank if not populated from identity provider.
Status	Active (green) = can log in. Inactive (red) = account deactivated.
Support	Shield icon indicating whether this account is a designated support account.
Created At	When this SuperAdmin account was provisioned.
Action	Edit (pencil) to modify. Delete (bin) to permanently remove SuperAdmin access.


WARNING: SuperAdmins can view and manage all data across all organizations. Only grant this role to users who require platform-level access. Review the list regularly and deactivate unused accounts.

### Org Admins Tab Lists all OrgAdmins scoped to their assigned organization. OrgAdmin roles are sourced from the iX Admin Portal. If an expected OrgAdmin does not appear, check the iX Admin Portal to confirm their role assignment there — changes may take a few minutes to sync. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ixhello.com/ixhello/administration/access-control.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.