SUMMARY
Use this guide to understand how user roles in Factbird control access to system functions through reading and writing permissions.
WHAT THIS IS
User roles in Factbird define what a user is allowed to see and do within the system. Each role is assigned a set of permissions that determine access to features and actions.
Permissions are generally divided into:
- Reading permissions → ability to view data and system functions
- Writing permissions → ability to interact with and modify data or system functions
Factbird includes default roles, but organizations can also create custom roles to match their needs.
WHY IT MATTERS
User roles ensure that the right people have the right level of access. This helps protect data integrity, prevents unintended changes, and aligns system access with job responsibilities.
By controlling permissions, organizations can safely allow operators, managers, and administrators to use the system without interfering with each other’s tasks.
WHEN YOU WOULD USE THIS
Use this when:
- Assigning access to new users
- Controlling who can edit or manage data
- Structuring system access based on job roles
- Managing permissions across teams or locations
HOW IT WORKS
Each user in Factbird is assigned a role that determines their permissions. These permissions define whether the user can:
- View data (read)
- Interact with or modify data (write)
Factbird provides four default roles:
- Super User → full access, including system configuration and administration
- Manager → full operational access, but without system administration rights
- Operator → limited access focused on shop floor tasks
- Read-only → view-only access with no ability to make changes
Roles can be applied at different levels (such as group or system-wide), which can affect what a user can access in different parts of the system.
Organizations can also create custom roles by defining their own combination of reading and writing permissions.
KEY TERMS / COMPONENTS
Role:
- A predefined or custom set of permissions assigned to a user
Reading Permission:
- Allows a user to view data and system functions
Writing Permission:
- Allows a user to interact with, edit, or create data
Super User:
- A role with full access, including system configuration and administration
Manager:
- A role with full operational access but without administrative control
Operator:
- A role with limited permissions focused on specific shop floor tasks
Read-only User:
- A role with access to view data only
COMMON MISUNDERSTANDINGS
-
All users can perform the same actions
- Access depends entirely on the assigned role and its permissions
- Access depends entirely on the assigned role and its permissions
-
Managers and Super Users have identical access
- Managers cannot perform system administration tasks
- Managers cannot perform system administration tasks
-
Roles only apply globally
- Roles can be assigned at different levels, affecting access scope
- Roles can be assigned at different levels, affecting access scope
-
Permissions are fixed
- Custom roles can be created to match specific needs
Related Articles