Appearance
Roles and project permissions
Access depends on an organization role and a project scope. An account can have different roles in different organizations.
Compare roles
| Action | Read-only | Operator | Manager | Owner |
|---|---|---|---|---|
| View permitted projects, devices, and data | ✓ | ✓ | ✓ | ✓ |
| View schedules and rules | ✓ | ✓ | ✓ | ✓ |
| Control points | — | ✓ | ✓ | ✓ |
| View and handle notifications and alerts | — | ✓ | ✓ | ✓ |
| Create export tasks and download files | — | ✓ | ✓ | ✓ |
| Edit devices, points, and project settings | — | — | ✓ | ✓ |
| Manage schedules, rules, and notification methods | — | — | ✓ | ✓ |
| Manage organization point types and data forwarding | — | — | ✓ | ✓ |
| Create projects and change asset ownership | — | — | — | ✓ |
| Manage members and access tokens | — | — | — | ✓ |
| Edit organization settings and delete the organization | — | — | — | ✓ |
These are role permissions. An action also requires a compatible device, access to the resource, and an appropriate plan status. Read-only accounts can view their own export task history but cannot create tasks or download files.
Project scope
When adding or editing a member, the Owner can grant access to All Projects or Specific Projects. Assign site-specific staff to the projects they need.
Organization-wide settings have a different scope. Data forwarding, for example, can send data from the organization. A Manager's specific-project scope does not isolate these shared settings to those projects.
Missing or disabled buttons
- Check the selected organization and project.
- Ask the Owner to verify your role and project scope.
- Check whether the plan has entered read-only mode.
- For actions such as serial settings or point configuration, check device support.
Access token permissions
API clients use separate access tokens. The token's role, project scope, and expiry are set when it is created. See Create and manage access tokens.