Skip to content

Roles and permissions

Every member of an organization has one role. The role decides what that person can do with the organization’s robots, suites and purchases.

Role Meant for
Owner The person responsible for the organization. Can do everything, including manage billing. Whoever creates an organization becomes its owner.
Admin Runs the team day to day: manages members, robots and content, and can buy. Can view billing but not manage it.
Technician Sets up and maintains rigs: configures robots, installs suites, deploys to stations. Cannot buy.
Event operator Runs sessions at an event: can operate robots, including emergency stop. Cannot install, configure or buy.
Viewer Can look but not change anything. Good for observers and stakeholders.
Member The older default role from before the other roles existed. It keeps what members could always do: use, install, configure and buy. Prefer one of the roles above for new people.

Yes means the role can do it.

Action Owner Admin Technician Event operator Viewer Member
See the Fleet tab, the Library and the Store Yes Yes Yes Yes Yes Yes
Control a robot and use emergency stop Yes Yes Yes Yes No Yes
Save robots and recent sessions to the organization Yes Yes Yes No No Yes
Get free suites and request restricted ones Yes Yes Yes No No Yes
Install suites and deploy them to a station Yes Yes Yes No No Yes
Buy paid suites Yes Yes No No No Yes
Check the status of an order Yes Yes No No No Yes
Register a new robot to the organization Yes Yes No No No Yes
Lock and unlock robots Yes Yes No No No No
Create and manage events Yes Yes No No No No
Operate events Yes Yes Yes Yes No Yes
Manage billing Yes No No No No Yes
Manage members and invitations Yes Yes No No No No

Emergency stop goes to everyone who may control a robot. A role can stop someone from doing more with a robot, but never from stopping it.

Some of these actions belong to features that are not in the app yet (events, robot locks and billing screens). The role you give someone today already decides whether they will be able to use them.

Roles are checked by Katena’s online services: the Store, your Library, the Fleet tab, and saving robots and sessions to your organization. If you try something your role does not allow, the app shows an error and nothing changes.

Steps you run directly on your rig network, such as the Setup Session wizard and the emergency stop in the session bar, work for anyone signed in at that workstation. Keep workstations signed in only as the person who is actually operating them.

Until it does, the organization owner asks Katena to:

  • add a member: send their email address and the role they should have. They need a Katena account with a verified email first (see Join your team).
  • change a member’s role: send their email address and the new role.
  • remove a member: send their email address. Once removed, they can no longer use the organization’s Library, Fleet or purchases.

Katena staff have their own staff roles, separate from your organization’s roles. They do not appear in your member list. Katena staff will never ask for your password. See Account security.