> For the complete documentation index, see [llms.txt](https://docs.unifize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unifize.com/user-guide/user-and-role-management.md). # User & role management This section covers how to manage users, define roles, and structure your organization in Unifize. From granting permissions to deactivating accounts, you’ll find everything needed to maintain secure, well-governed access to your data and workflows. ## Explore
Understanding roles & accessLearn how roles, groups, and access levels work together to control visibility and action.
Managing permissionsGrant, restrict, or fine-tune access to features, fields, and processes.
Deactivating usersRemove access for inactive users without disrupting your records or workflows.
Team & OrganizationView and manage all users, groups, and org settings in one place.
A strong permission structure keeps your organization secure, compliant, and organized. Use this section to build a scalable access model that aligns with your processes and teams. --- # 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.unifize.com/user-guide/user-and-role-management.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.