LOCAS Portal User Guide
Your step-by-step guide to the Local Content Assessment System
User Management
Company Administrator Only
Company Administrators manage who has portal access and what they can do. Access this from Quick Links → User Management.
Portal Roles
Each user is assigned a role when they are invited. The role determines what security group they belong to:
| Role | What They Can Do |
|---|---|
| Reporting Officer | Create and edit submissions (procurement, employment, SDP). Cannot approve or submit to the Ministry. |
| Compliance Officer | Everything a Reporting Officer can do, plus approve and submit documents to the Ministry. |
| Company Administrator | Full access — manages users, views compliance reports and penalties, and can do everything officers can. |
Granular Permissions
In addition to a role, each user has individual permission toggles that fine-tune what they can do:
| Permission | Default | What It Controls |
|---|---|---|
| Can Upload | On | Create and upload new documents (procurement plans, tenders, employment returns, SDP reports). Documents are saved as draft. |
| Can Edit | On | Edit documents that are still in draft state. |
| Can Approve | Off | Review and approve documents submitted by other users. Required for the maker-checker workflow. |
| Can View Reports | On | Access compliance reports and analytics dashboards. |
Administrators Always Have Full Access
Users with the Administrator flag automatically have all permissions enabled regardless of the individual toggles.
Minimum User Requirement
Every mining company must have at least 2 active users to use the maker-checker approval workflow. The system tracks this and displays a warning if the requirement is not met.
Why Two Users?
The maker-checker workflow requires one person to create a document and a different person to approve it. If your company only has one user, documents cannot be approved and submitted to the Ministry.
Inviting a New User
Click "Add New User" on the User Management page:
Enter Their Details
Provide the person's name (required), email address (required), phone number, and job title. The system checks in real time whether the email is already in use.
Assign a Role
Select Reporting Officer or Compliance Officer. Company Administrator cannot be assigned here — there is only one admin per company.
Set Permissions
Toggle the individual permission checkboxes: Can Upload, Can Edit, Can Approve, and Can View Reports. Defaults are already set but you can customise them.
Send Invitation
Click "Create User". The system creates the account and sends a welcome email with login instructions. The user sets their own password from the email link.
Email Validation
As you type the email address, the system checks whether it is already used by another user in LOCAS. If it is, you will see an error before submitting the form. Each user must have a unique email address.
Managing Existing Users
The User Management page shows a table of all team members with their role, status, and last login date. For each user (except yourself), you can:
| Action | What It Does |
|---|---|
| Edit | Update the user's name, phone, job title, role, and permissions. |
| Suspend | Temporarily disable the user's access. They cannot log in but their account is preserved. Use when someone is on extended leave or under review. |
| Reactivate | Restore a suspended user's access. |
| Resend Invite | Send a new password reset email if the user never set up their account or forgot their password. |
| Change Password | Set a new password for the user directly. Use this if the user cannot receive email. |
User Statuses
| Status | Meaning |
|---|---|
| Pending | Invitation sent but the user has not yet set up their account. |
| Active | User can log in and use the portal normally. |
| Suspended | Access temporarily disabled by admin. Can be reactivated. |
Important
Every company must have at least one Company Administrator. The system will not allow you to remove or suspend the last admin.