Setting Up OEE Roles

Not everyone in your facility needs the same level of access to Commander. An operator checking the Bingo Board on a station's monitor has different needs than a plant manager configuring analytics reports. Commander's role and permission system lets you control who sees what and who can change what.

Creating User Accounts

To add a new user, navigate to the User Management page in Commander. Click "Add User" and enter the person's name, username, and initial password. Each person who logs into Commander should have their own account. This keeps your audit trail clean and lets you assign different permission levels to different people.

The User Management page lets you create accounts and assign roles to each user.

Understanding Roles

A role is a permission template. Instead of setting permissions for each user individually, you create a role with the right access levels and then assign that role to users. If you need to change what a group of people can do, you update the role once and it applies to everyone assigned to it.

Permission Levels per Page

Commander lets you set permissions on a per-page basis. For each page in the application, a role can have one of three access levels:

• No Access - the user cannot see this page at all. It does not appear in their navigation.
• Read - the user can view the page but cannot make changes. They can see the Bingo Board, Map View, or analytics data, but they cannot rename teams, upload floor plans, or modify settings.
• Read & Write - the user can view and modify everything on the page. This includes renaming teams, uploading maps, configuring devices, exporting data, and managing other users.

Set No Access, Read, or Read & Write permissions for each page in Commander.

Example Role Structure

Here is a practical role setup that works for most facilities:

Operator Role

Read access to the Bingo Board and Map View. No Access to everything else. This is for the overhead monitors on the production floor and screens at operator stations. They see status but cannot change anything in the software. They interact with the physical Andon hardware on the floor.

Supervisor Role

Read & Write access to the Bingo Board and Map View (so they can toggle lights remotely). Read access to Data and Analytics. No Access to Devices and User Management. Supervisors monitor status, respond to calls from the software, and review recent data during shift handoffs.

Admin Role

Read & Write access to every page. This is for plant managers and designated IT staff who need to configure teams, manage devices, upload floor plans, create user accounts, and access all analytics.

When Roles Matter Most

For LAN and Cloud access deployments where Commander is reachable by many remote users, roles and permissions become essential. Every user should have their own login, and admin access should be limited to the people who need it.

Learn More

Continue setting up your Commander system:

• What Is Stack Light Commander?
• Getting Started with Commander
• How to Set Up the Bingo Board
• How to Set Up Map Views
• Reducing Bottlenecks and Downtime with Commander Data