Skip to content

Invitations

Invitations is where Owners and Admins bring new people into the workspace with the right role and seat from the start. You can send a single email invite, paste a list for bulk invites, or generate a shareable link for lower-friction onboarding.

Every invite path lets you choose the role (Owner, Admin, Member, or Viewer) and seat type (Planner or Viewer) before the person even accepts, so they land with correct access on first login instead of needing a follow-up adjustment.

This page also surfaces pending invites and access requests together, since both represent people waiting to get into the workspace. Approving an access request is functionally the same as sending an invite with a chosen role and seat.

  • Send a single invite by email with a chosen role and seat.
  • Send bulk invites by pasting a list of email addresses.
  • Generate a shareable guest link for lower-friction onboarding.
  • Track pending invites and resend or revoke them.
  • Approve or reject access requests from people trying to join.
  • Onboarding a new hire or teammate into the workspace.
  • Bringing in a batch of people at once, such as a new team.
  • Reviewing pending access requests before they sit unresolved.
  • Owner or Admin role to send invites or approve requests.
  • Members can view limited directory data but cannot invite by default.
  • Sidebar: Organization → Invite
  • Direct route: /org/invite
  1. Open Organization → Invite (/org/invite).
  2. Choose single, bulk, or guest link invite depending on how many people you are adding.
  3. Pick the role and Planner versus Viewer seat for the invite.
  4. Send the invite, or copy the generated guest link to share.
  5. Track pending invites and resend or revoke any that stall.
  6. Open Access requests to approve or reject people who requested to join directly.
  • New teammates land with the correct role and seat on their very first login.
  • No invite sits pending for weeks without follow-up.
  • Access requests are resolved quickly instead of leaving people stuck.
  • Prefer Viewer seats for stakeholders who only need to read, to control seat costs.
  • Use the guest link for fast, informal onboarding when email invites feel too slow.
  • Resend a stalled invite rather than creating a duplicate one for the same person.
  • Sending every invite as a Planner seat when most stakeholders only need Viewer access.
  • Letting access requests sit unreviewed, leaving people stuck on an access-pending screen.
  • Sharing a guest link publicly when it was only meant for a specific small group.