Positions
A Position is a descriptive label that correlates exactly to an Employee’s job in the Organization. Positions are associated with a Position Category (typically FOH, BOH, Management) for Labor Reporting.
Common examples include:
- Server
- Bartender
- Dishwasher
- Line Cook
- Cashier
- Floor Manager
- General Manager
- Director of Operations
In larger Organizations with multiple Brands and Locations, Positions might be further separated to account for more specific needs:
- Tom's Bistro Server
- Tom's Bistro Bartender
- Tom's Bistro Manager
- Tom's Take Away NYC Server
- Tom's Take Away Boston Server
- Tom's Take Away Manager
Roles
A Role is a defined set of permissions governing Employee access to various features of both the SALIDO POS and the SALIDO Bridge. Roles are assigned to Positions. A single Position can have multiple Roles, and a single Role can be assigned to multiple Positions.
See Create a Role.
Recommended Best Practices:
There are nearly endless possible combinations of Roles and Positions. Some Organizations prefer one discrete Role that corresponds exactly to one discrete Position (i.e. the Position of Tom's Bistro Server has the Role of Tom's Bistro Server and the Position of Tom's Take Away NYC Server has Role ofTom's Take Away NYC Server). Others create "universal" Roles that are assigned to multiple Positions (i.e. the Tom's Bistro Server, Tom's Take Away NYC Server, and Tom's Take Away Boston Server Positions all use the same Role of Server). Neither is right or wrong, but they represent two very different approaches.
This kind of variability gives each operation enormous control over how they manage permissions for their Employees but can also make it a little overwhelming when trying to make changes for an Organization.
Our best recommendation is to create a handful of core Roles and augment those core Roles with modular supplemental Roles that contain smaller subsets of permissions. By creating Roles in this manner, Positions can be managed as collections of multiple Roles stacked together.
As an example, we might create the following Roles for Tom's Hospitality:
Core Roles:
- Server
- Manager
Supplemental Roles:
- +Manage Banks and Pop Drawer
- +Voids
- +Transfer/Merge Checks
- +Split Checks
- +Manage Employees
- +Manage Timecards
- +Manage Devices
and then apply those to our Positions:
- Position: Tom's Bistro Server
Roles: Server, +Transfer/Merge Checks, + Split Checks - Position: Tom's Bistro Bartender
Roles: Server, +Transfer/Merge Checks, + Split Checks, +Manage Banks and Pop Drawer - Position: Tom's Take Away NYC Server
Roles: Server, +Split Checks - Position: Tom's Bistro Manager
Roles: Manager, +Manage Employees, +Manage Timecards, +Manage Devices - Position: Tom's Take Away Manager
Roles: Manager, +Manage Timecards
Again, there's no right or wrong here, but it is important to choose a convention and be cautious about how permissions are managed.
As a reminder, Employees, Positions, and Roles are all created and managed by Organization. The ability to access and adjust these permissions should be tightly controlled by Administrators within the Organization as changes to Positions and Roles could have unintended consequences at other Brands and/or Locations if not done with care. When in doubt, please contact SALIDO Support.