Users start with a broad operating role such as recruiter or sales.
Security & Governance
Scoped permissions are central to how Omelion handles visibility.
Omelion does not rely on role labels alone. Access is shaped by enabled modules, menu permissions, extra menus, and reporting scope to fit real operating structures.
What It Covers
Scoped Permissions
Control access through roles, modules, menus, extra menus, and reporting scope so users only see the parts of the recruitment operating system they need.
Role plus scope
Admin, sales, account manager, recruiter, and CV approver roles are only one part of the access model.
Module and menu control
Admins can expose or hide product areas through module and menu configuration.
Reporting visibility
Account-manager and manager views can be limited to selected users or reporting lines.
Operational Signals
How this page fits the wider operating model.
PrecisionTeams get the operational visibility they need without defaulting to full-system access.
FlexibilityThe model supports both broad admin control and tightly scoped operational roles.
GovernancePermission design becomes part of the product operating model.
Operational Depth
The detail behind this function.
These are the product capabilities that make this part of Omelion feel operationally serious instead of generic.
Entire sections of the product can be turned on or off per user.
The visible navigation and pages can be narrowed further.
Users can be constrained to the people or accounts they are supposed to oversee.
Next Step
Review how scoped permissions fits your recruitment operating model.
Omelion is built for agencies that want their commercial process, delivery work, submissions, portal visibility, and governance connected in one system.