Roles and what each can do

Everyone who signs in has a role. It decides what they see and what they can change, and iComply checks it on every action, not just in the menu. Choose the smallest role that lets each person do their job.

Every kind of organisation

• Association admin (an Administrator for builders and businesses): everything, including Users & access, Settings, packs, billing, requirements and the Audit log. Every association needs at least one; two is safer, so one can reset the other's two-step sign-in.
• association team member in a association with a providers register: sign people in at the front desk, invite providers, review and approve their documents, record Working with Children Check register checks and download one provider's evidence pack. Only admins approve SWMS, issue or run permits, export the whole-association evidence pack and the yearly compliance review, and change requirements, users and settings.
• association team member in a club, charity or peak body: add people, record checks and send reminders. Only admins change checks and profiles, users, billing and settings.

Builders and other businesses: the six roles

Builders and other businesses give each person one of six roles. Other businesses see some under their own names (in brackets). A team member with no role shows as (general) and works like any team member across every site, without the extra powers below.

What an Administrator can do

Everything, on every site: users, sites, settings, packs and billing, the API keys, webhooks and single sign-on, and every capability below.

What a Safety officer (HSEQ) can do

(Compliance or safety officer in another business.) On every site: approve documents; create and switch inductions; review SWMS; issue, renew and sign off permits; the gate, overriding a refusal, and the stop list (entries take effect at once); the yearly requirements review; incidents, corrective actions, inspections and their checklists, hazards and toolbox talks; reveal masked ticket numbers; internal audits and audit packs; vetting question sets and reviews of the WHS sections, and ratings; bookings; the asset register; planning (templates, approving plans) and chemicals; insights and hours worked. No users or billing.

What a Project or site manager can do

(Site manager in another business.) Their sites only: the gate; approving documents their sites require; signing off permits; investigating incidents, corrective actions, inspections, hazards and toolbox talks; revealing numbers for providers on their sites; bookings; ratings; assets, plans, the day's diary and chemicals on their sites; insights for their sites.

What a Gate user can do

(Front desk or gate user in another business.) Their sites only: the gate, signing people in and out, who's on site, the evacuation list, stop-list notes (a safety officer confirms them), reporting incidents and hazards, Take 5s and diary notes, and reading the chemicals register. Offered only while the front desk is on.

What a Director or executive can do

(Owner or manager (read-only) in another business.) Read-only across every site: the Overview, dashboards and reports, safety records, vetting, internal audits, planning, chemicals, assets, insights, the whole-association evidence pack and the audit log. Can't change anything.

What a Panel coordinator can do

(Contractor vetting coordinator in another business.) Vetting: panels and jobs, prequalification question sets and reviews of their sections, ratings and modern slavery statements. Read-only everywhere else (the register, sites, assets, chemicals). Offered only while vetting is on.

When a role can't do something

• Site roles see only their sites. Opening another page takes them to My sites; an action outside their sites says You can see your sites only. Ask a company admin if you need company-wide access.
• Read-only roles start on Overview. A change is refused with Your role can view only. Ask a company admin if something needs to change.
• Anything else outside a role says Your role doesn't include that. Ask a company admin. In a association without these roles, admin-only actions are refused for everyone but admins.