Protect workspace-level settingsKeep sensitive configuration and account controls with the people who own them.
Access that follows responsibility
Give people the controlstheir work actually needs.
Keep permissions close to the responsibility behind them. Workspace owners can protect account-wide controls while managers and supervisors stay focused on the employees, teams and records they are responsible for.
Scope managers to the right peopleKeep team and department visibility aligned with real management responsibility.
Separate viewing from changingLet reviewers see the records they need without automatically giving them editing control.
Workspace access mapOperations workspace
Role basedRolePeopleReportsSettings
OwnerFullFullFull
AdminManageViewManage
ManagerTeamTeam—
EmployeeSelfSelf—
Least-access principleReview permissions by responsibility
Clear starting points
Start with roles that matchthe way teams operate.
Use a small number of clear responsibility levels, then narrow visibility by team or department where needed. The goal is simple: enough access to do the job, without unnecessary exposure.
Workspace Owner
Account-wide responsibility for the workspace, billing and the highest-level access decisions.
Full workspace scopeAdmin
Operational control for people, configuration and recurring management work across the workspace.
Administrative scopeManager
Team-level visibility for the people, time records and reports connected to their operational responsibility.
Scoped team accessEmployee
Access centered on personal work records and the employee-facing areas enabled for the workspace.
Personal scope
Permission scope in motion
01
02
03
See access narrow fromworkspace to team.
Start with the responsibility attached to the role, then narrow the visible people, reports and controls to the smallest useful scope. The result is clearer ownership without giving every manager an account-wide view.
WorkspaceOwners keep account-wide responsibility.
DepartmentManagers see the group they operate.
IndividualEmployees stay focused on personal records.
Permission profileSupport Manager
Custom scopeView team time recordsEmployees in Support
Review screenshotsSupport team only
Edit employee profilesRestricted
Change workspace settingsOwner/Admin only
ScopeSupport department · 18 employees
Responsibility before title
ViewDecide which workforce records can be seen.
ManageSeparate day-to-day people actions from account administration.
ScopeLimit responsibility to the right team, department or individual.
Build access aroundwhat the role must do.
A manager may need to review time and activity without changing workspace settings. A supervisor may need day-to-day team visibility without access to other departments. Keep permissions close to the action each role is expected to take.
Visibility with a boundary
01 02 03
Keep department accessinside the right boundary.
Give managers the records their role depends on without widening access to unrelated departments. Worklix keeps the selected team, permitted record types and restricted areas visible in one clear permission map.
Start with the departmentChoose the people a manager is responsible for before adding record permissions.
Layer in record accessAllow the time, attendance or activity views the role actually needs.
Keep admin controls separateWorkspace-level settings remain outside the department boundary unless explicitly granted.
Changes that stay understandable
Keep permission changeseasy to review.
Role changes should be deliberate and easy to understand later. Keep the person, scope and access decision together so workspace administrators can review who received additional responsibility and why.
Explore SecurityRecent access changesToday
Amanda MilesManager scope changed to Support
Ravi JoshiReport access enabled for Operations
Lena HartWorkspace settings access removed
Permission review ready3 changes today
Roles & permissions FAQ
Keep access clearas the team grows.
Use role and scope together so managers can do their work without unnecessary workspace access.
What is role-based access?
Role-based access groups permissions around a person’s responsibility, helping a workspace decide what they can view, manage or change.
Can managers be limited to their own team or department?
Yes. Worklix is designed around scoped workforce responsibility so manager visibility can stay connected to the people they actually manage.
Should every manager have administrative access?
No. Operational responsibility and workspace administration are different jobs. Permissions should reflect the actions each role actually needs to perform.
Can employee access stay limited to personal records?
Employee-facing access can stay centered on personal records and the workspace areas enabled for employees rather than exposing management controls.
Clear responsibility, controlled access
Give every role the accessits responsibility requires.
Keep people, reports and workspace controls inside one permission model that can grow with the team.