Security and User Access in Jobpac

Simona Riftin

Updated 08 June 2026 11:38

System Administration

Security and user access in Jobpac

How Jobpac's layered security model controls access to company, project and payroll data.

Overview

This article explains how Jobpac security works and why each layer matters when managing access to company, project and payroll data. It is designed for administrators who set up USERIDs and apply role-based access.

When a user signs in, Jobpac checks their access across four areas: which companies they can access, which jobs they can see, which menus and functions appear, and whether they can view payroll information.

The four security layers

Layer	Controls
WorkID security	Which companies (WorkIDs) a user can access.
Job security	Which Jobs/Projects a user can view or update within their allowed WorkIDs.
Menu and function access	Which modules, menus and functions appear based on their Menu Structure and security level.
Payroll security	Whether a user can view or process payroll information. Operates separately from the other layers.

WorkID security

WorkID security is the first and broadest layer, especially in environments with multiple entities or business units. You can use it to:

Give access to a single WorkID.
Allow access to selected WorkIDs only.
Restrict users to the parts of the business they work in.

Job security

Job security controls which Jobs/Projects a user can work with inside the WorkIDs they are allowed to access. With job security you can:

Limit access to the Jobs/Projects the user manages or supports.
Prevent users from viewing unrelated projects.
Reduce the risk of accidental updates to the wrong project.

Menu and function access

Menu and function access determines what a user can do after signing in, managed through Menu Structures and security levels.

Menu Structure	Controls which modules and menu options appear.
Module options	Group related functions such as finance, projects or payroll.
Security level	Determines whether the user can see or run each function.

Payroll security

Payroll security is an additional layer that protects sensitive employee information. It operates separately from WorkID, job and menu access. Common configurations include:

No payroll access for most users.
Full payroll access for payroll and HR teams.
Restricted access to specific employee groups where required.

How the layers work together

A user's overall access is defined by the combination of all four layers. Examples include:

Project manager	Access to project costing and forecasting, limited to the Jobs/Projects they manage.
Finance user	Access to general ledger, accounts payable and accounts receivable across multiple WorkIDs.
Payroll officer	Access to payroll processing with limited access to project costing and financial menus.

Designing role-based security

Starting with roles rather than individual users helps you maintain consistent access and onboard new staff more efficiently.

Define standard roles such as project manager, site administrator, finance officer and payroll officer.
Create Menu Structures for each role based on required functions.
Apply WorkID and job security so each role sees only relevant companies and Jobs/Projects.
Grant payroll access only where needed.

Good practices for ongoing security

Review user access periodically to confirm it is still required.
Disable USERIDs when people leave the organisation.
Limit high-impact functions to trusted and trained users.
Document your role and access patterns for consistency.

You're done when:

✓ USERIDs have been created with the correct WorkID and job security

✓ Menu Structures have been assigned based on defined roles

✓ Payroll access has been granted only where required