> For the complete documentation index, see [llms.txt](https://docs.santacruzsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.santacruzsoftware.com/gemini-home/guides/user-administration.md).
# User & Access Administration
Add, import, approve, and organize BrandingUI users and control their asset access.
The **Users** area controls site accounts, roles, organizational assignments, and asset visibility. BrandingUI site accounts are separate from any PrintUI or design-platform credentials used to upload assets; a person may need one or both account types.
***
## Adding and Importing Users
Administrators can add users individually, bulk-import them from an Excel (`.xlsx`) file, and export the current user list.
For each user, confirm:
* Name, email address, and sign-in details.
* One or more roles.
* Business Unit and Department, where applicable.
* Locale and profile information.
* Category access and any user-specific feature settings.
Use View As after saving to confirm the user's navigation, visible assets, and workflow.
## Account Requests and Automatic Rules
If the sign-in page allows account requests, new accounts begin as **Disabled** until approved. Notification recipients can activate the account and assign the correct roles.
Automatic account-creation rules can approve requests whose email contains a configured string:
* `@example.com` matches users from one domain.
* A full address matches one specific person.
* `@` matches any valid email address.
Automatically approved accounts receive the **User** role. If verification email is enabled, the account remains unverified until the user confirms the address; unverified accounts are deleted after seven days.
## Roles and Temporary Access
Users can hold multiple roles, such as Administrator and User or Designer and User. A **Guest** has standard User capabilities but expires after the duration configured in General Settings. Editing a Guest account resets its timer and can extend access.
Expired Guests cannot sign in and are cleaned up automatically. A **Disabled** account cannot sign in and is also used for requests awaiting approval.
## Assigning Asset Categories
Asset categories control visibility; keywords affect search only. Configure categories on the Template, Package, and Form management pages before creating user rules.
Rules can match values such as:
* Full or partial email address.
* Role or custom user fields.
* Country, time zone, language, or locale.
* Department on Enterprise sites.
If no rule matches, BrandingUI uses the **If no other match** selection. When several rules match, the system uses one matching source according to database order rather than merging all matches or relying on the visible rule order. Always verify important rules with **View As**.
## Account and Email Health
BrandingUI may disable an account whose address repeatedly bounces or is reported for abuse. Correct the mailbox problem, then use **Test Email** in Notifications to clear a successfully verified address from the bad-email list.
---
# 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.santacruzsoftware.com/gemini-home/guides/user-administration.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.