Overview

Invite teammates from Settings → Administration → Members when the workspace is ready for them to enter. The invite flow gives each person a starting role and access level, so it is worth reviewing access before sending a large batch of invitations.

Use this article when you are inviting internal employees, admins, finance users, contractors, or implementation leads during onboarding.

Least-access rule: Give people the access they need for their current work, then expand access later when their responsibilities change.

Who can do this

  • Owners and admins only: This is controlled by the workspace role (Owner or Admin), not by an access level, so it cannot be granted to other members.
  • Personal accounts: Only the space owner and admins can do this.

Owners and admins review and change access levels in Settings → Administration → Members → Access levels.

Before you start

  • Confirm organization settings and starter records are ready enough for new users to orient themselves.
  • Collect the email addresses for the people you want to invite.
  • Decide which role and access level each person should receive.
  • Review who should have finance, billing, integration, organization settings, or permission management access.

Invite a teammate

  1. Open Settings → Administration → Members.
  2. Click Invite members.
  3. Enter one or more Email addresses.
  4. Choose the Access level they should have when they join.
  5. Click Send invites.
  6. Ask the teammate to accept the invite and sign in before the invite expires.

Choose the right access

User typeTypical starting accessReview carefully
Daily team memberClients, projects, tasks, time, notes, and documents needed for assigned work.Whether they need create, edit, or only read access.
Project or operations leadProject settings, task workflows, assignments, reporting, and team coordination tools.Whether they can change templates or workspace-wide settings.
Finance userBudgets, rates, contracts, invoices, approvals, and billing records.Access to sensitive revenue, cost, and payment information.
AdminMembers, permissions, integrations, subscription, and organization settings.Whether they should manage other admins or billing.

Review pending invites

After sending invites, return to Settings → Administration → Members to review pending invitations. Pending invites are useful during rollout because they show who has not joined yet.

  • Resend an invite when the recipient cannot find the original email and the action is available.
  • Cancel an invite when it was sent to the wrong address or the person no longer needs access.
  • Update access by cancelling and re-inviting, or by changing the member's role after they join, depending on the available action.

Verify access after acceptance

  1. Ask the teammate to open the workspace and visit the module they will use first.
  2. Have them open one sample record, such as a project or task.
  3. Confirm they can perform their expected actions, such as viewing, editing, assigning, commenting, or logging time.
  4. If they cannot see what they need, review their role and access level in Settings → Administration → Members → Access levels.

Security note: Do not use a broad admin role as a shortcut for onboarding. Broad access is harder to audit later and can expose finance, member, integration, or subscription settings unnecessarily.


Common mistakes

  • Inviting everyone before setup is complete: New teammates may see test records, incomplete modules, or missing workflows.
  • Using one role for everyone: This can hide important tools from leads or expose sensitive areas to people who do not need them.
  • Forgetting pending invites: A launch can stall when key teammates never accepted their invitations.

Next steps

  • Review the permissions overview before creating specialized roles.
  • Ask each new teammate to complete a simple task in the sample project.
  • Revisit member access after the first week, after role changes, and before inviting external collaborators.