Roles and Permissions
A user refers to any person with the ability to access Pulse by logging in. Every user is linked to a specific role that dictates their authorized actions within the system. These permissions define the activities that a user is capable of carrying out in the system.
| Permission | Server Admin | Team Admin | Editor | Viewer | Non-Logged in User |
|---|---|---|---|---|---|
| View applications | yes | yes | yes | yes | Public Only+ |
| Add, edit, delete applications* | yes | yes | yes | ||
| Query data sources directly | yes | yes | yes | ||
| Add, edit, delete data sources | yes, including global/public. | Yes. Team Only | |||
| Add and edit teams | yes | Yes. Team Only | |||
| Add and remove team members | yes | Yes. Team Only | |||
| Add and edit users | yes | ||||
| Configure server wide settings | yes |
* Editors can only edit applications either owned by themselves, owned by a team that they belong to, or applications explicitly shared with them (or with one of their teams) as Editor. This includes the ability to change the owner.
Public Only+. Non-logged in users can only view data where both the application and the data source is public.
Per-dashboard sharing
In addition to ownership-based access, anyone with edit rights on a dashboard can grant other users or teams Viewer (read-only) or Editor (read and edit) access to that single dashboard. Sharing is independent of the dashboard's owner and its public flag, and cannot grant Admin. Open the dashboard's settings dialog to manage its share list. Server Admins are never restricted by share lists. When a user, team, or dashboard is deleted the corresponding share entries are removed automatically.