> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-getting-started/verifone-central/training-videos/create-a-new-user.md). # Create a new user You can create new users to add to your organization and assign them specific permissions in a few easy steps. Watch this tutorial on how to create new users. You can also read or step-by-step [documentation](/verifone-central-getting-started/verifone-central/administration-tools/users-and-merchants-roles.md#creating-new-users). {% embed url="" %} ### Before you start Confirm that your role permits this task. Use a non-production configuration when testing a change. ### Follow the workflow Pause the video at each action. Complete the same action in Verifone Central before continuing. ### Verify the result Confirm that the saved setting, record, or report shows the expected result. Use the written guide linked above for field-level details and troubleshooting. {% hint style="info" %} Access and available options depend on your role and organization configuration. {% endhint %} --- # 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.verifone.com/verifone-central-getting-started/verifone-central/training-videos/create-a-new-user.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.