> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/workbench-setup/get-started/add-and-manage-users/user-role-rights.md). # User Role Rights Learn how Expel features relate to Workbench user roles. {% hint style="info" %} At least these rights are available in Workbench. However, this list can change at any time and may not be accurate at any given viewing. {% endhint %} Workbench has two user roles: **Organization Admin** or **Organization Analyst**. Keep in mind that Organization Admin gives full administrator rights to your organization's Workbench. Any user can be designated *assignable* by selecting a checkbox in the User profile. After a user is assignable: * Their name appears in "Assign to" menus. * Their initials are visible to other Expel users after an alert or action is assigned to them.

Feature	Action	Organization Admin	Organization Analyst
Assign	assign to customer user	✅	✅
Assemblers	view page	✅	✅
	create/edit/delete	✅
Auto remediations	enable/disable	✅
	view	✅	✅
BOLO	view page	API only	API only
Customer context	view page	✅	✅
	add context	✅
Customer configuration^[1]	view/edit	✅
Hunting	view hunts (org specific with hunting service)	✅	✅
Investigative actions	pivot to console	API only	API only
Investigation findings	create/edit/delete	✅	✅
Investigation remediations	create/edit/delete	✅	✅
Timeline	upload CSV	✅	✅
	add/edit timeline event	✅	✅
My profile	edit email notifications	✅	✅
	change password	✅	✅
	reset Google Auth	✅	✅
	edit user	✅	✅
	"assignable" checkbox	✅
	"locked" checkbox	✅
Navigation bar	change organizations	Multi-org only	Multi-org only
My organization	view page	✅	✅
Organizations list	view page	Multi-org only	Multi-org only
	edit	Multi-org only
	configure/edit PagerDuty integration	✅
	show PagerDuty service key	✅	✅
	configure/edit Ticketing integration	✅
Organization Notifications	view	✅	✅
	add, edit, delete	✅
Resilience	view all recommendations	✅	✅
	show/hide recommendations	✅	✅
Security devices	view page	✅	✅
	add, edit, delete	✅
Workbench integrations (PD, ticketing, etc.)	configure/edit	✅
	test connection	✅
Users	view page	✅	✅
	"assignable" checkbox	✅
	change own role	✅
	change username	✅
	add, edit, delete	✅
	lock other users ("locked" checkbox)	✅
	resend enrollment email	✅

^\[1] Customer configuration defaults can only be created by expel\_admin but overrides can be set per customer by org\_admin. However, each configuration has internal write and visibility properties that can further change who can view or edit the setting to SYSTEM, EXPEL, or ORGANIZATION. --- # 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.expel.io/workbench-setup/get-started/add-and-manage-users/user-role-rights.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.