> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/groups-users-and-permissions.md). # Groups, Users and Permissions ## Create a group and test document access With group permissions already enabled, create an isolated reviewer group and add a non-admin test user. Allow listing, viewing and editing assigned invoices; leave deletion, bulk changes and approvals unavailable. Save and reopen the settings, then sign in as the ordinary user: the assigned invoice is visible and an unassigned control document is absent. {% embed url="" %} [Watch with subtitles](https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/groups-permissions-admin/v1/en.html) These settings answer three different questions: who can sign in, which sub-organisation they work in, and what their group may do. | If you need to… | Open… | | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Add or edit a person's account | **Settings** → **Users**; then read [Users](/administration-and-setup/settings/global-settings/groups-users-and-permissions/users.md). | | Organise access across company units | **Settings** → **Sub-Organizations**; then read [Sub-Organizations](/administration-and-setup/settings/global-settings/groups-users-and-permissions/sub-organizations.md). | | Control access by group | **Settings** → **Groups and Permissions**; then read [Groups and Permissions](/administration-and-setup/settings/global-settings/groups-users-and-permissions/groups-and-permissions.md). |
Group selection panel.

Group selection panel.

If a user cannot see a document or action, check their account and organisation first. Then check the relevant group permissions. Use a non-admin test account to confirm the access a normal user will actually have before changing a live organisation. --- # 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.docbits.com/administration-and-setup/settings/global-settings/groups-users-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.