> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/general/users/user-roles.md). # User Roles A matrix of every akenza user role and the actions it permits, at both organization and workspace level. The matrix below lists every action in akenza against every role that can perform it. Actions are grouped by the area they apply to (organization, workspace, asset inventory, device types, data flows, integrations), and the columns are split into the five **organization** roles and the three **workspace** roles. Read a row to find who may do something, or a column to find what a role can do. A user's effective rights are the combination of both: their organization role, if any, plus their role in the workspace they are working in. See [Users](/general/users.md) for how the two levels relate. Some rows worth knowing before you grant a role:

Action	Who can do it
Add, remove, or change users	Organization owner and admin. At workspace level, also the workspace admin. Editors cannot.
Delete an organization	The organization owner alone.
Manage billing	Organization owner and admin.
Create a workspace	Every organization role except member, viewers included.
Delete a workspace	Organization owner, admin, and editor, plus the workspace admin.

Scope	Action	Organization					Workspace
Scope	Action	Organization					Workspace
		Owner	Admin	Editor	Viewer	Member	Admin	Editor	Viewer
Organization
	Overview	✅	✅	✅	✅	✅
	Edit	✅	✅	✅	❌	❌
	Billing	✅	✅	❌	❌	❌
	Delete	✅	❌	❌	❌	❌
	Add user	✅	✅	❌	❌	❌
	Edit user role	✅	✅	❌	❌	❌
	Remove user	✅	✅	❌	❌	❌
	Create workspace	✅	✅	✅	✅	❌
	View workspace list	✅	✅	✅	✅	✅
	Edit Settings	✅	✅	✅	❌	❌
	View Asset list	✅	✅	✅	✅	❌
	Edit Asset	✅	✅	✅	❌	❌
	Delete Asset	✅	✅	✅	❌	❌
Workspace
	Overview	✅	✅	✅	✅	❌	✅	✅	✅
	Edit	✅	✅	✅	❌	❌	✅	✅	❌
	Delete	✅	✅	✅	❌	❌	✅	❌	❌
	Add user	✅	✅	❌	❌	❌	✅	❌	❌
	Edit user role	✅	✅	❌	❌	❌	✅	❌	❌
	Remove user	✅	✅	❌	❌	❌	✅	❌	❌
	Edit settings	✅	✅	✅	❌	❌	✅	✅	❌
	View Asset list	✅	✅	✅	✅	❌	✅	✅	✅
Asset Inventory
	View	✅	✅	✅	✅	❌	✅	✅	✅
	Create	✅	✅	✅	❌	❌	✅	✅	❌
	Edit	✅	✅	✅	❌	❌	✅	✅	❌
	Delete	✅	✅	✅	❌	❌	✅	✅	❌
Device Type
	View	✅	✅	✅	✅	✅
	Create	✅	✅	✅	❌	❌
	Edit	✅	✅	✅	❌	❌
	Delete	✅	✅	✅	❌	❌
Dataflow
	View	✅	✅	✅	✅	❌	✅	✅	✅
	Create	✅	✅	✅	❌	❌	✅	✅	❌
	Edit	✅	✅	✅	❌	❌	✅	✅	❌
	Delete	✅	✅	✅	❌	❌	✅	✅	❌
Integrations
	View	✅	✅	✅	✅	❌	✅	✅	✅
	Create	✅	✅	✅	❌	❌	✅	✅	❌
	Edit	✅	✅	✅	❌	❌	✅	✅	❌
	Delete	✅	✅	✅	❌	❌	✅	✅	❌

--- # 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.akenza.io/general/users/user-roles.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.