Freshbooks User Management Guide

• Model type: role-based
• Description: FreshBooks uses a fixed set of predefined roles (Owner, Manager, Employee, Contractor, Accountant/Bookkeeper). Admins assign one role per team member. There are no custom roles or granular permission toggles within the standard UI.
• Custom roles: No
• Custom roles plan: Not documented
• Granularity: Role-level only; no per-feature or per-client permission toggles available within a role.

1. Log in as the account Owner or Manager.
2. Navigate to Settings → Team Members.
3. Click 'Add a Team Member'.
4. Enter the team member's first name, last name, and email address.
5. Select a role (Manager, Employee, Contractor, or Accountant/Bookkeeper).
6. Optionally assign the team member to specific projects.
7. Click 'Send Invitation'.
8. The invitee receives an email and must accept the invitation to activate their account.

Required fields: First name, Last name, Email address, Role

Watch out for:

• Team members are not available on the Lite plan; the account must be on Plus, Premium, or Select.
• Each additional team member costs $11/user/month and is billed immediately upon invitation acceptance, not upon sending the invite.
• The invitee must have or create a FreshBooks account using the invited email address.
• If the invitee already has a FreshBooks account under a different email, they cannot use that existing account; they must use the invited address.
• There is no bulk invite or CSV import for team members.

• Can delete users: No
• Delete/deactivate behavior: FreshBooks does not permanently delete team members. Removing a team member deactivates their access. Their historical records (time entries, expenses, invoices they created) remain in the account. The team member can be re-invited later.

1. Log in as the account Owner or a Manager with team management permissions.
2. Navigate to Settings → Team Members.
3. Locate the team member to remove.
4. Click the options menu (three dots or 'Edit') next to their name.
5. Select 'Remove Team Member' or 'Deactivate'.
6. Confirm the action in the dialog prompt.
7. The team member immediately loses access to the account.

Watch out for:

• Removing a team member does not delete their data; all historical records are retained.
• If the removed team member was the only person assigned to active projects, those projects may become unassigned; reassign before removing.
• Billing relief may not be immediate; the seat may be charged through the end of the current billing period.
• There is no 'suspend' or 'pause' state; the only options are active or removed.

• Where to check usage: Settings → Team Members (shows list of all active team members and their roles)
• How to identify unused seats: No built-in last-login or activity report for team members. Owners must manually review the team member list and cross-reference with project activity or contact team members directly to identify inactive seats.
• Billing notes: Team member seats are billed as an add-on at $11/user/month. The Lite plan does not support team members. Annual billing saves approximately 10% on the base plan but the per-seat add-on pricing may vary; confirm current rates at freshbooks.com/pricing. Seats are not prorated for partial months in most standard billing configurations.

Every app that adds or removes team members in FreshBooks requires manual action through Settings → Team Members - there is no bulk invite, no CSV import, and no automated provisioning path outside of an Okta SSO configuration on an Enterprise plan.

Identifying unused seats is entirely manual: FreshBooks provides no last-login data or activity audit, so owners must visually review the team member list and cross-reference project activity themselves. Billing for removed seats does not stop immediately; the seat charge typically runs through the end of the current billing period, meaning delayed offboarding directly increases cost.

The most consistent friction reported by FreshBooks users centers on three areas. First, the absence of granular permissions - there is no way to restrict a Manager to specific clients or projects, which forces a choice between over-provisioning and under-provisioning access.

Second, Contractors are billed at the same $11/user/month add-on rate as Employees despite having significantly more restricted access, which surprises teams that treat contractors as low-cost collaborators.

Third, the Lite plan restriction on team members is frequently discovered after signup rather than before, requiring an unplanned plan upgrade.

Common complaints:

• Users report frustration that there is no granular permission control - for example, no way to give a Manager access to some clients but not others.
• Multiple users have noted that removing a team member does not immediately stop billing; the seat charge continues through the end of the billing period.
• Users on the Lite plan frequently discover that team member functionality requires upgrading to Plus or higher, which is not prominently communicated during signup.
• Some users report confusion that Contractors are billed the same as Employees despite having significantly more restricted access.
• Users have noted the absence of a last-login or activity audit for team members, making it difficult to identify and reclaim unused seats.
• There is no bulk invite or CSV import for team members, which is a pain point for businesses onboarding multiple staff at once.
• Ownership transfer requires contacting support rather than being self-serve, which causes delays when businesses change ownership.

FreshBooks is a practical fit for small teams where the five fixed roles map cleanly to actual job functions and where accounting-focused access control is sufficient.

It is a poor fit for organizations that need role segmentation below the Manager level - for example, restricting a Manager to a subset of clients - or for teams that require auditable, automated provisioning and deprovisioning.

If your IT or HR workflow depends on every app reflecting real-time joiner/mover/leaver changes without manual intervention, FreshBooks' current tooling will not support that without significant process overhead.

Bottom line

FreshBooks delivers straightforward team access management for small accounting-focused teams, but its fixed role model, absence of activity auditing, and lack of bulk provisioning tools create real operational drag as headcount grows.

Every app in a modern SaaS stack is expected to support some form of automated lifecycle management; FreshBooks currently meets that bar only for organizations already running Okta on an Enterprise plan.

Teams outside that configuration should budget for manual seat reviews and accept that offboarding will require deliberate, step-by-step action each time.