> For the complete documentation index, see [llms.txt](https://docs.payengine.co/developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payengine.co/developer-docs/getting-started-1/2.-user-account-types-and-permissions.md). # 2. User Account Types & Permissions The following user access matrix displays the permission level for each user type in the partner console. Note: Developers have Admin level permissions within the **Sandbox** account for unrestricted testing & integration.
FeatureAdminUserDeveloper
Dashboard✔✔✔
Merchants
Invite to Merchant Portal✔✔
Create New Merchant✔✔
View Application✔✔✔
Edit Application✔✔
Update Merchant Status✔✔
Transactions✔✔✔
Settled Batches✔✔✔
Payouts✔✔✔
Disputes✔✔✔
Devices✔✔✔
Statements✔✔
Logs✔✔✔
Payment Link✔✔
Payment Page✔✔
Settings✔
Gateways✔✔
Transaction Monitoring Rules✔✔
Webhooks✔✔
Transactions✔✔✔
Disputes✔✔✔
Hosted Payments✔✔
Reports✔✔✔
API
Manage Keys✔✔
Manage Webhooks✔✔
Embedded Widget✔✔
Account
Profile✔✔✔
Email✔✔
Password✔✔✔
2FA✔✔✔
API Keys✔✔
Webhooks✔✔
Fee Schedules✔✔
Users✔
Settings
Plaid Credentials✔✔
Mailgun✔✔
Payrix API Key✔
Card Token Expiration Policy✔
Internal Settings✔
Onboarding Customization✔
Marketplace Settings✔
Other Settings✔
Partner Portal✔✔✔
Merchant Portal✔✔✔
PAX Device✔✔✔
Stripe Connect✔✔
Transaction Monitoring Rules✔✔
--- # 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.payengine.co/developer-docs/getting-started-1/2.-user-account-types-and-permissions.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.