Getting started: assign permissions

The fourth setup task controls who gets access to the resources you have exposed. This is where you grant users and groups the ability to reach specific resources, at a specific level.

What this task is for

A resource is not accessible until someone is permitted to access it. Permissions are the mechanism: for each user or group you choose which resources they can use and at what level (for example read-only, read/write, or a named role in an application).

How to do it

Open Getting Started > Assign Permissions from the left navigation.
Identify the users or groups that should have access (create them first if needed, see Users and Groups).
Open the permissions screens:

For applications: Access > Application Permissions (Application permissions).
For resources (shares, desktops, databases, networks, SSH, launchers): Access > Resource Permissions (Resource permissions).

Select the user or group, then the resource (or resource group), then the permission level.
Repeat for every user or group that needs access.
Mark Assign Permissions complete on the task board.

Making permission management scale

Use groups instead of individual users so new team members inherit access automatically. See Groups.
Use resource groups to manage access to many resources at once. See Resource groups.
Use policies to add rules on top of permissions (for example geolocation restrictions). See Policies.

Configuration versus confirmation

Configuration: assigning permission levels in the permissions screens.
Confirmation: the platform shows a summary of what will be granted before you apply changes. Review it carefully, because granting a level of access is immediate once applied.

Troubleshooting

A user says they cannot access a resource: check their permission in the permissions screens, and check the audit for the denial reason.
If users are allowed to request access instead, see Resource requests.