Creating a New User
A user is anyone from your company who logs into HammerTech with a Main Contractor role. To add one:
- Go to Administration > User Management.
- Click + and enter the user’s email.
- Validate it, then complete name, phone, and job title.
- Select a User Type (Admin, Standard, or Company-level role).
- Assign project or region access and tick permissions (Project Admin, Region Admin, Confidential Data, etc.).
- Optionally apply a User Permission Set.
- Choose whether they should auto-join new projects.
- Click Create. The user receives an activation email.
Deleting a User
Deleting removes login access but retains their historical activity.
- Go to Administration > User Management.
- Search and open the profile.
- Select Options > Delete.
- Confirm deletion.
Assigning Users to Multiple Roles
A single email can be tied to multiple employers or roles.
- Add an existing email as a Primary Contact or Nominated Representative for another employer.
- HammerTech links all roles under one login; users choose the account after logging in.
User Permission Sets
User Permission Sets define exactly what each role can see and do across HammerTech.
They let you narrow or expand access beyond the default role permissions — for example, allowing a Standard User to edit inspections but not incidents.
Create a Permission Set
- Go to Administration > User Permission Sets.
- Click the blue + icon in the top-right corner.
- Enter a clear Name that reflects its purpose (e.g. Std User – No Equipment Review).
- Choose a Base Role (Admin, Standard User, etc.).
- Each Permission Set can only apply to users with that same base role.
- Add or remove permissions by clicking the dots next to each module or action:
- Small dot = no access
- Large ticked dot = access granted
- Toggle whole modules on/off using the ON/OFF button at the module header.
- Turning a module off hides it from that user and suppresses its notifications.
- Click Create when finished.
Edit an Existing Permission Set
- Open Administration > User Permission Sets.
- Select the set name.
- You can edit the name and change permissions, but not the base role or assigned users.
- Click Save Changes.
Delete a Permission Set
Only unused sets (no users assigned) can be deleted.
- Open the set > click the Options cog > Delete.
- Type the on-screen confirmation phrase.
- Click Delete.
Apply a Permission Set to a User
System-Level Application
Applies across all projects the user can access.
- Go to Administration > User Management.
- Select the user.
- In Applicable Permission Set, choose the relevant set.
- Save Changes.
Project-Level Application
Overrides any system-level set for that single project.
- Go to Project Settings > Users.
- Select the user.
- Click Change the User Permission for this Project.
- Choose a set and save.
Project-level sets override system-level ones where both exist.
Bulk-Assign Permission Sets
Use this when applying the same set to many users at once.
- Go to Administration > User Management.
- Click the Options cog > Bulk Assign User Permission Set.
- Select the User Type to include (Admin, Standard User, etc.).
- Download User List and review it in Excel.
- Optional filters: Job Title, Existing Permission Set, Status (Active/Awaiting).
- Return to HammerTech > click Continue.
- Upload the reviewed file. Check the summary for errors.
- Choose the Permission Set to apply and decide how to handle existing project-level sets:
- Override = replace project-level set.
- Keep = retain project-level set.
- Review and click Submit.
Note: Bulk-unassigning is not supported. To remove a set, edit each user individually.
System vs Project Scope
| Scope | What It Affects | Typical Use |
| System-Level | All projects and the Company Overview view. | Apply to users with the same duties everywhere. |
| Project-Level | One specific project; overrides system-level. | Adjust temporary site-specific access. |
Best Practice
- Keep Permission Set names short and descriptive.
- Review sets quarterly to match any role or compliance changes.
- Use project-level sets sparingly to avoid confusion.
- Always test new sets with a dummy Standard User account before assigning widely.