> For the complete documentation index, see [llms.txt](https://docs.korewireless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.korewireless.com/iam/users/rbac.md). # Role Based Access Control (RBAC) ## Roles A user can belong to one of the following roles. | Role | Description | | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Owner | An owner is the main point of contact assigned during registration; the owner is the user who completes registration. There can be only one owner, and ownership can be transferred. A user can be an owner of multiple accounts. | | Admin | An admin has similar permissions to the owner, and an account can have multiple admins. An owner or other admins can invite an admin. | | Developer | A developer has permissions similar to the admin but does not have access to manage the account itself, such as account settings, users, and billing. | | Default |

The default role is view only in the KORE Console. The user can edit their profile but will be limited to viewing access for all other functions.

Other products may further define this role. Review their respective documentation for more details.

| ## Access Control Each role has a predefined set of permissions.
ResourcePermissionOwnerAdminDeveloperDefaultPermissionOwnerDefaultDeveloperAdmin
AccountsView✔️✔️✔️✔️View✔️✔️✔️✔️
Edit✔️✔️✖️✖️Edit✔️✖️✖️✔️
Transfer Ownership✔️✖️✖️✖️
UsersView✔️✔️✔️✔️View✔️✖️✖️✔️
Invite✔️✔️✖️✖️Invite✔️✖️✖️✔️
Edit✔️✔️✖️✖️Edit✔️✖️✖️✔️
BillingView Invoices✔️✔️✖️✖️View Invoices✔️✖️✖️✔️
Manage Credit Cards✔️✔️✖️✖️View Credit Card✔️✖️✖️✔️
--- # 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://docs.korewireless.com/iam/users/rbac.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.