Security and User Access in Jobpac

Jobpac uses layered security to control what users can see and do. 

These controls help protect company and project data, and make sure each user only has access to information that is relevant to their role.

How security works in Jobpac

Access in Jobpac is controlled through a combination of user IDs, menu structures and security settings. When a user signs in with their USERID and password, the system checks:

• which companies (WorkIDs) they can access
• which jobs they can see
• which menus and functions are available to them
• whether they can view or process payroll information

By configuring these areas carefully, you can support role based access and maintain strong control over sensitive data.

WorkID security

WorkID security controls which company ledgers and projects a user can access. This is the first layer of security for multi company environments.

Using WorkID security you can:

• grant access to one WorkID only
• grant access to a selected group of WorkIDs
• restrict access to particular WorkIDs for users who only work in part of the business

This helps you separate regional operations, business units or legal entities while still running them in the same Jobpac environment.

Job security

Job security controls which jobs a user can see and work with inside the WorkIDs they have access to.

With job security you can:

• limit a user to specific projects that they manage or support
• prevent users from viewing projects they are not involved in
• reduce the chance of accidental updates to the wrong project

Job level security is particularly useful in organisations with many concurrent projects or where different teams manage different portfolios.

Menu and function access

Menu and function access controls what a user can do within Jobpac once they have signed in. This is managed mostly through menu structures and security levels.

Key elements include:

• Menu structure – defines which modules and options appear for a USERID.
• Module options – group functions such as finance, projects or payroll.
• Security level – determines whether a user can see a particular menu option or function.

By assigning different menu structures to different roles, you can give users access to only the functions they need, such as project costing for project teams or financial processing for finance teams.

Payroll security

Payroll security provides additional protection for sensitive employee information. It allows you to strictly control who can see and process payroll data.

Typical payroll security setups include:

• no payroll access for most users
• access for payroll and human resources teams only
• restricted access to certain groups of employees, if required

By keeping payroll security separate from general job security and menu access, you ensure that employee data is only visible to authorised staff.

How menus and security work together

Menu structures and security settings work together to create role based access in Jobpac. A user’s experience is shaped by:

• their USERID and assigned menu structure
• their WorkID and job security settings
• any payroll security restrictions

For example:

• a project manager may have access to project costing and forecasting menus, and to only the jobs they manage
• a finance user may have access to general ledger, accounts payable and accounts receivable, across one or more WorkIDs
• a payroll officer may have access to payroll processing and employee records, but limited access to project costing

This layered approach reduces clutter for users and supports segregation of duties for control and audit purposes.

Designing role based security

When you design security and user access in Jobpac, it helps to start with roles rather than individual users.

Good practices include:

• define standard roles such as project manager, site administrator, finance officer and payroll officer
• create menu structures for each role, focused on the functions they need to use
• apply WorkID and job security so each role sees only the relevant companies and jobs
• grant payroll access only to roles that require it

Once roles are defined, new users can be set up faster and more consistently by assigning them to the appropriate role based access pattern.

Good practices for managing security

To keep security and user access in Jobpac reliable and well controlled, consider the following practices:

• Review access regularly to make sure users still need the roles and WorkIDs they have.
• Remove or disable USERIDs promptly when people leave the organisation.
• Limit powerful functions to users who need them and understand the impact of their actions.
• Document your role designs so they can be applied consistently over time.

These practices help maintain data security and reduce the risk of errors or unauthorised changes.

Putting security and user access together

Security and user access in Jobpac combine:

• WorkID security to control which companies users can access
• job security to control which projects they can see
• menu and function access to control what they can do
• payroll security to protect sensitive employee information

When these layers are designed around clear roles, Jobpac can give each user exactly the access they need, while keeping company, project and payroll data protected.