> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/gettingstarted/devops-portal/users.md). # Users The **Users** section manages access to the selected Runtime. This can only be edited by admins on that specific runtime. Access is granted based on runtime specific user tokens and permissions. ### Tokens * The first token becomes available after the first login. * Additional tokens can be generated at any time via the user menu. * Tokens are Runtime-specific. ### Adding a User To add a user to a Runtime: 1. The user must log in to the DevOps Portal at least once. 2. After the first login, the user can generate a token via: -> User menu (top right corner) -> Generate token 3. The user provides this token to the Runtime administrator, or sends in a support ticket if runtime administrators are unknown or unavailable. 4. In the Users page, any Runtime Admin can add the user with the provided token and then set the permissions. After adding the user, the **Edit User Mapping** screen opens to configure the following permissions. * Manage Basic Settings * Manage Hostnames * Manage Response Headers * Manage IP access control rules * Manage SMTP Settings * Manage Scheduled Tasks * ManageAIAgentSettings * Manage Trace Points and custom logs * View Application Log * View Custom Logs * View Mail Log * View Task Log * View System Log * ViewAIAgentSettings ### Global Users Users in the right table are **Global Users**. * Global Users can only be modified by **Global Administrators**. * Global Users cannot be disabled. * They are required for runtime management and system control. --- # 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.wem.io/platform/gettingstarted/devops-portal/users.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.