Members and Roles

The Members tab in your organization account allows administrators to manage team access and user roles.

User Management

• Add Member: Click the + ADD MEMBER button in the top right to invite new users to the organization.
• Member List: Displays a table of all current members with their Avatar, Name, Email, and Phone number.
• Remove Access: Click the Trash Can icon on the far right of a row to remove a member from the organization.

Organization Roles

When assigning roles within the organization, you can choose between Organization Admin, User, and Client.

Feature / Permission	Organization Admin	User	Client
Access Organization Section	✅	➖	➖
Create/Edit Licenses and Organizations	✅	➖	➖
Block / Delete Users	✅	➖	➖
Delete robot	✅	➖	➖
Access Robot/Fleet Monitoring	✅	✅ (If Shared)	✅ (If Shared, only as operator)

• Organization Administrator: Has full access to organization settings, billing, and member management. They can also edit organization details like the name, logo, and allowed external domains.
• User: Has standard access to robots and fleets but only if they were shared with him. Generally cannot change organization-level settings.
  • An Organization User only has access to robots and fleets if they are specifically members of them.
  • Their permissions on those specific robots/fleets are determined by their assigned role (Administrator, Developer, or Operator).
• Client: Designed for external stakeholders or customers who need limited visibility.
  • Read-Only Access: Clients have read-only access to robots and fleets specifically shared with them.
  • Operator Permissions: A Client always has Operator permissions on any robot or fleet shared with them.
  • Restrictions: They cannot create new robots or fleets, nor can they access favorites, configurations, simulation, or the resource center.

Robot and Fleet Roles

Permissions can also be granularly assigned at the specific robot or fleet level.

Note: Permissions on a robot are derived from the robot’s specific permission if it exists; otherwise, they are inherited from the fleet permissions.

Role Definitions

• Administrator: Full control over the robot/fleet, including managing members, changing settings, and deleting resources.
• Developer: Can deploy configurations, upgrade agents, and access all robot tabs for monitoring and debugging.
• Operator: Primarily for monitoring and basic operations like starting/stopping recordings or components.

Permission Matrix

Feature	Administrator	Developer	Operator
Access all robot tabs	✅	✅	➖ (Monitoring only)
Deploy configuration	✅	➖	➖
Upgrade agent	✅	✅	➖
Rename / Change Description	✅	✅	➖
Manage Members	✅	➖	➖
Connect via SSH	✅	✅	➖
Reboot Robot	✅	✅	✅
Start/Stop Components	✅	✅	✅
Start/Stop Recordings	✅	✅	✅
Change License	✅	✅	➖

Important Notes on Inheritance:

• If you share a fleet with a user, robots in that fleet not currently shared with them will be shared using the fleet-level role.
• If a user already has a specific role on a robot, that role remains unchanged even if the fleet role is different.
• Organization Admins are automatically considered owners of all robots and fleets inside the organization.