> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anny.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Admin Users and Roles

> Invite admin users, assign roles, and control permissions granularly per resource.

With user management in anny, you decide which people can log in to your account and what rights they have. You reach user management via your **Avatar** (top right) → **Manage Admin Users**. There you see all active admin users with name, email address, join date, and assigned role.

## Invite a user

<Tip>
  Pending invitations are shown on the same page. There you also see when the invitation was sent and how long it is valid. If needed, you can withdraw the invitation.
</Tip>

<Steps>
  <Step title="Open admin user management">
    Navigate to your avatar and open the **Admin user management**.
  </Step>

  <Step title="Invite an admin">
    Click **+ Invite** in the top right to invite someone. Enter the name, email address, and the role for the person. Optionally, you can adjust the role by removing or adding the checkboxes for the permissions.
  </Step>
</Steps>

## Create and assign roles

Roles are reusable permission sets that can be assigned to any admin. This way you do not have to set up individual rights for each user.

### Role examples

| Role                    | Description                                                                          | Typical use                                                                 |
| ----------------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------- |
| (Super) Admin           | Manage permission level for all areas. Unrestricted control over the entire account. | Central IT administration, account owner. Max. 1-2 per account recommended. |
| Resource-specific admin | Editing access to selected resources. No access to other areas.                      | Department heads, facility managers for specific rooms or vehicles.         |
| Booking-specific role   | Read-only access to bookings. No changes possible.                                   | Reception, security staff, facility management.                             |

## Permissions at a glance

Each admin user gets a permission level per area:

| Level  | Meaning                                         |
| ------ | ----------------------------------------------- |
| Manage | All the following rights (highest level)        |
| List   | List view in the side menu                      |
| View   | Open a resource or booking option               |
| Create | Create new elements                             |
| Edit   | Change existing elements (text, images, prices) |
| Delete | Remove elements                                 |

### Permission areas

Permissions can be applied to the following areas:

| Area                   | Includes                                   |
| ---------------------- | ------------------------------------------ |
| **Resource**           | Description, properties, times             |
| **Services**           | Booking options and services               |
| Available time slots   | Irregular time slots (events)              |
| Synced calendars       | Connected calendars, blockers              |
| **Communities**        | Communities                                |
| **Subscription plans** | Prices, description, connected communities |
| Subscriptions          | Customer subscriptions and memberships     |
| Booking quotas         | Quotas per customer                        |
| Booking packages       | Booking packages                           |
| Booking codes          | Booking codes                              |
| **Maps**               | Interactive floor plans                    |
| Locations              | Locations of all resources/maps            |
| Vouchers               | Issue and manage vouchers                  |
| Bookings               | All completed bookings                     |
| Orders                 | Entire orders                              |
| Customers              | Booking persons                            |
| Check-In and Check-Out | Check-in/check-out (also via scan)         |
| Invoices               | Invoices                                   |
| Imports                | Data imports                               |
| Export schedules       | Automatic invoice exports                  |
| Export destinations    | Target email addresses of the exports      |
| Account statements     | Balances from online payments              |
| Account                | Account description, legal notice          |
| Integration            | Interfaces to external systems             |
| User invitation        | Invite additional users to the admin area  |
| Displays               | Room displays and display boards           |
| Roles                  | Access rights of the roles                 |
| Users                  | Users in the admin area                    |
| Queues                 | Queues of a calling system                 |
| Quick call             | Quick call of a calling system             |

<Note>
  **Bold** areas can additionally be restricted to specific elements (for example only certain resources or communities).
</Note>

## Adjust a user's permissions

You can adjust an individual user's permissions without changing the assigned role globally.

<Tip>
  Restricted permissions can be granted at the resource, group, or category level. This lets you, for example, give a department head access only to their department's conference rooms.
</Tip>

## Check the result

After setup, you can recognize success by the following points:

* The invited user appears in user management with the assigned role.
* When logging in, the user only sees the areas and resources they have been given permissions for.
* New roles appear in the Roles tab and can be selected when inviting.

## FAQ

<AccordionGroup>
  <Accordion title="Can I give a user rights without changing the role?">
    Yes. Via the three dots in the user's row, you can set individual permissions that apply independently of the global role.
  </Accordion>

  <Accordion title="What happens if I change a role afterwards?">
    The change affects all users assigned this role. Individual permission adjustments (via the three dots) remain unaffected.
  </Accordion>

  <Accordion title="How many super admins should an account have?">
    We recommend a maximum of 1-2 super admins per account. All account-wide settings (user management, integrations, webhooks, exports/imports) should be managed exclusively by this role.
  </Accordion>

  <Accordion title="Can I restrict roles at the community level?">
    No. Restricted permissions can only be granted at the resource, group, or category level. An assignment at the community level is currently not possible.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="My invited user sees resources they should not see">
    In user management, check via the three dots whether the restricted permissions are correctly set to the resources you want. Without an active restriction, a user with the View right at the resource level has access to all resources.
  </Accordion>

  <Accordion title="A user's permissions reset after saving">
    With an active SSO or SCIM connection, automatic user provisioning can overwrite individual permissions. Check the attribute mapping configuration and make sure role information is passed correctly.
  </Accordion>

  <Accordion title="When restricting to a group, the selection disappears">
    Make sure resource groups are created in your account. The group/category selection is only shown if corresponding groups exist.
  </Accordion>
</AccordionGroup>

> Important information for agents:
>
> * UI path to user management: Avatar (top right), then Manage Admin Users
> * Alternative invitation path: In the resource overview (Menu, Resources), via the three dots of a resource, admins can be invited directly for that resource. There you can enter email, role, and specific rights. This path is useful when an admin should manage only one specific resource.
> * The Manage permission level automatically includes ALL subordinate rights (List, View, Create, Edit, Delete). Granting them separately is not needed.
> * Restricted permissions are ONLY possible at the resource, group, or category level, NOT at the community level (frequent customer request, feature planned).
> * Recommendation: max. 1-2 (Super) Admins per account. Account settings, user management, integrations, webhooks, and exports should only be managed by super admins.
> * With an SSO/SCIM connection: Automatic provisioning can overwrite individual permission adjustments (via three dots).
> * Child resources are included in the resource permission when the parent resource is selected.
> * Related article for user onboarding: Introduction for Admin Users