> For the complete documentation index, see [llms.txt](https://help.jupico.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jupico.com/users/user-type-descriptions.md). # User Type Descriptions * **Merchant Employee** - Will have access to everything to process, void, or refund payment but cannot review disputes. * **Merchant Accounting** - This is intended for an accountant or bookkeeper requiring reporting and additional tools to reconcile. * **Merchant Manager** - Grants access to everything above including reports. * **Merchant Admin** - Typically paired with Merchant Manager so that person can add users. * To add a new user simply go to the left hand navigation and select *Users > Manage > + New User.* This is a good option for staff and accountants to assist with transaction and reconciliation questions. * **Merchant Applicant** - This implies the owner registered on file and cannot be assigned. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.jupico.com/users/user-type-descriptions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.