User & Role Management – Adding, Inviting & Importing Users

User & Role Management: Add, Invite, Import & Control User Access

User Management

OctopusPro includes built-in User Management and Role-Based Access Control (RBAC) so you can:

  • Provision users (admins, office staff, dispatchers, finance users, etc.)
  • Invite fieldworkers (employees or subcontractors) to create their own login
  • Import users from accounting tools (e.g., QuickBooks / Xero)
  • Control permissions using roles (credentials)
  • Secure access with status controls (activate/deactivate, block, delete), password resets, and force logout

Best practice: set up your roles/permissions first, then add or invite users so every person starts with the correct access level from day one.


On this page


Where to manage users

You can manage all internal users from the Users list:

Path: SettingsCompany SettingsUsers

If you are managing mobile staff, you can also create/invite/manage them from the dedicated Fieldworkers area (recommended for day-to-day dispatching):

Path: Fieldworkers (left menu) → manage profiles, job settings, working hours, and fieldworker access.


Add a new user (admin-created)

Use this method when your office/admin team wants to create the account and assign access immediately (ideal for internal staff such as admin users, dispatchers, reception, finance, or managers).

Steps

  1. Go to SettingsCompany SettingsUsers.
  2. Click Add New.
  3. Enter the user’s details (name, email, phone, etc.).
  4. Select the appropriate Role / Credential (this controls what they can access).
  5. Save the user.

Add new user in OctopusPro (Users list)

Tip: If your team has multiple job functions, create separate roles (e.g., Dispatcher, Finance, Admin, Read-only) instead of giving everyone full admin access.


Invite fieldworkers to self-register

Inviting fieldworkers allows them to create their own password and complete their profile details—reducing admin workload and speeding up onboarding. This is ideal for subcontractors, contractors, and distributed teams.

What happens when you invite a fieldworker?

  • The fieldworker receives an email invitation.
  • They create their login and complete their details.
  • You can control what they see/do in the Fieldworker App using Fieldworker Permissions (separate from RBAC).

Method 1: Invite from the Users list

  1. Go to SettingsCompany SettingsUsers.
  2. Click Invite Fieldworker.
  3. Enter the fieldworker’s details and send the invitation.

Invite fieldworker from Users list

Method 2: Invite from the Fieldworkers page (recommended for dispatch teams)

  1. Open Fieldworkers from the left menu.
  2. Click Invite Fieldworker.
  3. Enter the details, then send the invite.

Invite fieldworker button from Fieldworkers page

Method 3: Invite from a specific fieldworker record

  1. Open Fieldworkers and locate the person.
  2. Open their profile/record.
  3. Use the invite option to send the registration email.

Invite fieldworker from within a fieldworker profile

Email verification note: If you need the fieldworker to verify their email (or re-send the verification link), see: Fieldworker Email Verification.

Fieldworker email Verification Process

Customize the invitation email: you can manage email templates here: Email Templates.


Subworkers (Crew Members) Under a Lead Fieldworker

Subworkers (also called crew members) are assistant/apprentice user accounts that belong to a lead fieldworker. They’re ideal when jobs are delivered by a team (lead + helpers) and you want each person to have their own login, tracked activity, and accountability—without granting full access to sensitive financial or customer data.

Common examples:

  • Lead technician + apprentice
  • Cleaner + assistant
  • Tradesperson + labourer/runner
  • Multi-tech crews where a lead manages the team

How it works (high level):

  1. Enable the Subworkers capability (permission-controlled). Learn more: Allow Fieldworkers to Add Subworkers (Crew Members).
    Managing Fieldworker Teams and Subworker Delegation
  2. Add/manage subworkers under a lead fieldworker from the web app (and optionally from the Fieldworker App if allowed). Step-by-step: Manage Subworkers Under Fieldworkers.
  3. Control what subworkers can access using fieldworker permissions (least-privilege). See: Fieldworker Permissions & Access Control.

Note: Subworkers are different from assigning multiple independent fieldworkers to one booking. If you simply need multiple techs on a job (not a lead/crew hierarchy), see: Assign Multiple Fieldworkers to a Booking.

Assign multiple fieldworkers to a single service


Import users from QuickBooks / Xero

If you already maintain contacts/users in your accounting system, OctopusPro can pull users from connected accounting tools (such as QuickBooks or Xero) to avoid manual re-entry.

Steps

  1. Go to SettingsFinancial Settings.
  2. Open your integration settings (e.g., QuickBooks / Xero).
  3. Use the option to pull/import users into OctopusPro.

Pull users from QuickBooks into OctopusPro

Important: imports typically rely on matching identifiers (most commonly the email). If one person needs multiple accounts/roles using the same email, read: Using the Same Email for Multiple Users.

Multi User Role Access with Shared Email


Roles & permissions (RBAC)

OctopusPro uses Role-Based Access Control (RBAC) (called Roles or Credentials) to control what each user can view and do. This helps you protect sensitive data, prevent mistakes, and keep teams focused on their responsibilities.

Common role examples

  • Owner / Super Admin: full access
  • Dispatcher / Scheduler: bookings + calendar management only
  • Finance: invoices, payments, refunds, and accounting features
  • Customer Support: customer profiles, communications, and bookings (limited financial access)
  • Read-only / Viewer: reporting visibility without editing rights

Standard Role Framework (Recommended Starting Point)

Use this framework to create clean, task-based roles that follow the least-privilege principle (give each role only the access it needs). You can start here, then fine-tune permissions based on your workflow.

Category Typical tasks Recommended default access
Admin / Owner System setup, integrations, pricing rules, financial approvals, user/role oversight, security actions Full (limit to a small number of trusted users)
Sales / Estimator Create/send quotes, manage leads/inquiries, view customer CRM details, forecast pipeline Restricted financials (no payment gateways, refunds, payroll, or accounting settings)
Office Staff (Support / Dispatch) Schedule jobs, assign fieldworkers, manage customer communications, update booking details Module-specific (bookings/customers/comms; invoices read-only or limited)
Office Staff (Accounts / Finance) Issue invoices, record/reconcile payments, manage credit notes/refunds (if allowed), run financial reports Module-specific (invoices/payments/reports; bookings often read-only)
Fieldworker (Lead) Accept/decline jobs, update status, complete checklists/forms, capture signatures, upload photos, timesheets Mobile-first (Fieldworker App permissions control what they can do)
Subworker (Crew Member) Assist lead fieldworker, log hours, upload job photos, complete assigned checklists Limited mobile (separate login under a lead; minimal visibility by design)
Manager (Read-only / Approver) View dashboards/reports, monitor performance, approve key actions (optional), QA oversight Read-only + approvals (avoid edit/delete unless required)

Important: There are multiple access layers in OctopusPro:

Subworkers (crew members) – learn more:

Reminder: Customers—even those on membership plans—remain outside this internal role framework; they use the Customer Portal, not the internal workspace.

Create a new role

  1. Go to SettingsCompany SettingsRoles / Credentials.
  2. Click Add New Role.
  3. Name the role clearly (e.g., “Dispatcher”, “Finance”, “Team Leader”).
  4. Save the role.

Create a new role / credential in OctopusPro

Add new role details screen

Assign a role to a user

  1. Go to the Users list.
  2. Edit the user (or open their profile).
  3. Select the correct Role / Credential and save.

Assign role/credentials to a user

Configure role permissions

Inside the role settings, enable only the permissions the role needs (principle of least privilege). This keeps your system secure and reduces costly errors.

Role permissions configuration screen

Learn more about RBAC: Role-Based Access Control (RBAC) & User Permissions.

Role-Based Access Control (RBAC) overview in OctopusPro

Fieldworker App permissions: RBAC controls admin/office access. Fieldworker access is additionally controlled via Fieldworker Permissions: Fieldworker Permissions & Access Control.


Edit and maintain user profiles

Keeping user profiles accurate improves scheduling, communications, and accountability. Admins can update user details at any time, and some users (like fieldworkers) can also self-update certain information.

Fieldworker self-service (My Account)

Fieldworkers can update parts of their profile through My Account (depending on your configuration and permissions).

My Account area for fieldworkers

Admin editing (Users list)

  1. Go to SettingsCompany SettingsUsers.
  2. Find the user and open Edit.
  3. Update the required fields, then save.

Edit user information screen

Admin editing (Fieldworker profile)

If you’re managing a fieldworker, it’s often faster to open their profile directly from the Fieldworkers list.

View fieldworker profile from the Fieldworkers list

Edit a fieldworker profile as an admin

Full guide: Managing and Editing User Information and Viewing a Fieldworker Profile.

Fieldworker Profile Overview Management


Security tools: impersonation, force logout, reset password

Admins can use built-in security tools to troubleshoot issues, end active sessions, and secure accounts if credentials may be compromised.

1) Login as another user (impersonation)

Use impersonation to reproduce a user’s issue exactly as they see it (without needing their password). This is especially useful for troubleshooting permissions, portal access, and UI visibility issues.

Login as another user (impersonation) option

Guide: Login as Another User (Impersonation)

2) Force logout (end active sessions)

Force logout immediately ends a user’s active session (or all users), which is useful after security incidents, offboarding, or when you need changes to take effect immediately.

Guide: Force Logout Users

3) Change or reset a user password

Reset a password if a user is locked out, forgot their password, or if you suspect their credentials are compromised.

Change/reset user password option

Set and save a new password

Guide: Change / Reset User Passwords


User statuses: active, inactive, blocked, deleted

OctopusPro provides multiple ways to control access. These are often confused, but they do different things:

  • Active: user operates normally (based on their role/permissions).
  • Inactive (Deactivated): the user cannot be assigned jobs, but they can still log in unless you also block them.
  • Blocked: the user cannot log in, but their historical records remain available to admins.
  • Deleted: the user account is permanently removed from your Users list (cannot log in; deletion is irreversible).

Deactivate (inactive) user option in the Users list

Billing note (per-user plans): inactive users may still count toward your user count. If you need to reduce user count, consider deleting the user (after completing offboarding checks).

Guides: Activate / Deactivate Users, Block Users, Delete Users (Single & Bulk) + When to Deactivate/Block

User Status Management Active Inactive


Audit trail: User Activity Log

For accountability and security auditing, use the User Activity Log to review actions performed by users inside the system.

Comprehensive user action and audit trail showing filter options (date range, user, module, action, keyword) and activity records including IP address

Guide: User Activity Log


To stay updated, please subscribe to our YouTube channel.

Scroll to top