> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/administration-new-ui/general-settings/user-management.md). # Users View list of users in JFrog Connect. Users and Roles are managed in JFrog Platform under the Administration tab. User permissions for [JFrog Connect](https://jfrog.com/connect/) are managed in Connect under the User Permissions tab. To view the list of users in Connect, go to **General** **Settings** in the left navigation pane and click the **User Permissions** tab. The User Permissions tab shows the same list of users that appear in JFrog Platform and indicates the following user attributes: * Name * Email * Projects * Admin * Last Login Each user is defined as either an administrator or non-administrator. ### Administrator An *administrator* is a user that has the Admin role defined in the Platform, has access to all Connect fleets, and has all Connect permissions. An administrator cannot be edited in Connect. An administrator has access to all functions and features in Connect and can perform various management tasks such as creating, viewing, editing, and deleting of non-admin users. In addition, there are certain features in Connect, e.g. Audit Log, that by definition only the administrator user has access to. An administrator user in JFrog Platform is also an administrator in Connect. ### Non-administrator A *non-administrator* is any Connect user that does not have the Admin role defined in the Platform. An administrator can determine which fleets a non-administrator has access to and can set specific permissions in each project for the non-administrator. ## What’s Next? Learn how to [add a Connect user](/administration-new-ui/general-settings/user-management/add-user-from-jpd-artifactory.md). --- # 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.connect.jfrog.io/administration-new-ui/general-settings/user-management.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.