# Access for other roles

Administrators always use all of Track. To let other people in without making
them administrators, for example editors or a client role, choose their roles
in the **Access** section of Track's **Settings**, which only administrators
see. The older address `#/track/access` still opens it.

## View dashboards

Roles under **View dashboards** get the `sleek_track_view` capability. Their
users open the workspace with Track alone and read every site's and group's
dashboard and **All sites**: the metrics, chart, cards, filters, groups of
pages, saved views, realtime count and exports, including the [summary for AI
tools](/docs/track/dashboard.md#summary-for-ai-tools). They see goals, funnels
and annotations but change none of them. They do not see Track's settings, the
site and group settings, share links, email reports or the rest of the
workspace, and nothing they read carries a site's webhook secret or site
token. Their posts can [embed a dashboard](/docs/track/embedding.md).

## Manage Track

Roles under **Manage Track** get `sleek_track_manage` as well as
`sleek_track_view`. Their users do everything in Track an administrator does:
add and edit sites and groups, change the collection settings, and manage
goals, funnels, annotations, saved views, share links, embedded dashboards and
[email reports](/docs/track/email.md). Choosing the roles in **Access** and the
license stay with administrators.

A role chosen for both counts as managing. The capabilities are granted while
SleekTrack runs and are not written to the roles, so removing SleekTrack
leaves the roles as they were. To give a single user access, give them a role
of their own with a plugin that manages roles, then choose that role here.