Skip to main content
Each person in an organization has one role: Owner, Admin, or Member. The role decides what the person can do. Stout checks the role on the server for each action. Owners and admins have the same permissions, except for some organization settings that only an owner can change. The tables on this page show owners and admins in one column, and they mark each action that only owners can do. Members can use only the boxes that an owner or admin assigns to them. The dashboard sometimes shows a control that a member cannot use. If a member selects that control, Stout refuses the action. Stout does not let anyone remove or demote the last owner of an organization.

Boxes

Locks

You must have a display name before you can lock a box. A lock does not stop an owner or admin from editing, updating, or deleting a box. See Locks.
Do not depend on a lock alone to keep other people off a box. A lock does not stop a UART console, a firmware flash, a script from Import Test, or a Factory run. Tell the people who share the box before you start work that must not be interrupted.

Workbench and tests

Factory

Organization and settings

To save an SSO configuration, an owner must also have a verified email address. See Single sign-on.

Features that your organization controls

Each organization has Home, Boxes, Audit Log, and Settings. Stout turns on the other features, such as Workbench, Factory, and CI Metrics, for each organization. Stout calls these features modules. To see the modules of your organization, owners and admins go to Settings > Modules. To add a feature, contact Stout. A feature with a Beta label is new. Stout can change it before it is complete. Every member sees every feature that your organization has. The role and the box access of a member control what the member can do. See Members and invitations.

The Developer role

Stout staff who help your organization show the role Developer on the Team Permissions page. They do not have an owner, admin, or member role in that list.