Roles and permissions
Every member of an organization has one of two roles:
- Admin. Manages the organization: invites people, changes roles, manages models and API keys.
- Member. Uses the organization: connects devices, sees the fleet, models and usage, and calls the API with keys an Admin created.
The person who creates an organization is its first Admin. An organization always has at least one active Admin.
Permissions
Section titled “Permissions”| What | Member | Admin |
|---|---|---|
| Connect devices with the desktop app | ✓ | ✓ |
| See the Fleet, Live and Models pages and usage charts | ✓ | ✓ |
| See the team and the organization’s plan | ✓ | ✓ |
| See the list of API keys (keys stay masked) | ✓ | ✓ |
| Make API requests with an organization key | ✓ | ✓ |
| Create and delete API keys | ✓ | |
| Add, enable, disable and remove models | ✓ | |
| Invite people and revoke invitations | ✓ | |
| Change members’ roles | ✓ | |
| Leave the organization or delete your own account | ✓ | ✓ ¹ |
¹ An organization’s only Admin can’t leave while other members remain. Promote someone else to Admin first.
Changing a member’s role
Section titled “Changing a member’s role”Admins can change other members’ roles:
- Open Team in the console.
- Click Edit role next to the member.
- Choose Admin or Member and click Save.
Some rules:
- You can’t change your own role.
- You can’t demote the last Admin. Promote someone else first.
Roles and API keys
Section titled “Roles and API keys”API keys belong to the organization, but each key keeps track of the Admin who created it. A key only works while that Admin is an active member of the organization. If they leave or are deactivated, their keys stop working, and the API keys page marks them Disabled. See API keys.
Before changing an Admin’s role or removing them, check which keys they created. Replace the keys that are still in use.