Security and User Access in Jobpac

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.

How security works in Jobpac

Jobpac uses multiple layers of security to control what users can see and do. When a user signs in with their USERID and password, Jobpac checks their access across several areas.

• Which WorkIDs (companies) they can access
• Which Jobs/Projects they can view or update
• Which menus and functions appear based on their Menu Structure
• Whether they can view or process payroll information

Together these layers help you provide the right access for each user while protecting sensitive data.

WorkID security

WorkID security controls which companies a user can access. This is the first and broadest layer of security, especially in environments with multiple entities or business units.

You can use WorkID security to:

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

This keeps company financial and operational data separated while still working in a single Jobpac system.

Job security

Job security controls which Jobs/Projects a user can work with inside the WorkIDs they are allowed to access. It provides a more detailed level of control over project visibility.

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. This is managed through Menu Structures and security levels.

Key elements include:

• 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.

By assigning specific Menu Structures to defined roles, you can ensure users only see the functions they need.

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

This helps ensure payroll information is visible only to authorised staff.

How the layers work together

A user’s overall access is defined by the combination of WorkID security, job security, Menu Structure and payroll settings. These layers work together to shape each user’s Jobpac experience.

Examples include:

• A project manager may access project costing and forecasting, and only the Jobs/Projects they manage.
• A finance user may access general ledger, accounts payable and accounts receivable across multiple WorkIDs.
• A payroll officer may access payroll processing but have limited access to project costing and financial menus.

This layered design reduces menu clutter, supports segregation of duties and improves data control.

Designing role‑based security

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

Good practices include:

• 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.

This approach ensures new users can be set up quickly and consistently.

Good practices for ongoing security

To keep access accurate and secure, review and maintain settings regularly.

• 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.

Putting it all together

Jobpac security brings together WorkID access, job security, menu and function access and payroll security. When these layers are built around clear roles, each user receives the access they need while protecting company, project and employee data.

You may want to continue with articles on creating USERIDs or setting up Menu Structures.