Skip to content

Invite Members

Adding a teammate usually has two steps:

  1. add them to the organization
  2. give them access to the workspace they should operate

Step 1: Add them at the organization level

Open Settings and go to Organization → Users, then click Invite User.

Invite User flow from the organization users page

This is where you decide:

  • who is joining the organization
  • which workspace they should enter first

Add one email at a time, then preview and confirm the batch. The preview shows whether an existing Codeer account will be added immediately or an invitation email will be sent. It also shows the remaining member capacity for the current plan; you cannot confirm a batch that would exceed the limit.

Track invitations that have not been accepted

Organization → Users lists pending invitations with the email, workspace, inviter, status, and expiration time.

  • Use Resend to issue a fresh email when the recipient did not receive it or the earlier link is no longer valid. The new email replaces the previous link.
  • Use Revoke to invalidate a pending invitation that should no longer grant access.
  • Do not treat a pending invitation as an active member. Confirm acceptance before assigning work that depends on access.

Step 2: Confirm workspace access

After the teammate exists at organization scope, open the target workspace, open the workspace menu, and click Members.

Workspace members modal for adding and managing workspace access

This is the place to:

  • confirm they can enter the workspace
  • set or adjust the workspace role
  • remove access later if responsibilities change

If the person does not appear in the workspace list

Usually one of these is true:

  • they have not been added at the organization level yet
  • their invitation is still pending or expired
  • they were added, but not assigned to the intended workspace

Start from Organization → Users, then return to workspace Members.

A simple rollout habit

Invite only the people who need to act on the current phase:

  • early pilot: owner, operator, and one or two expert reviewers
  • wider rollout: add support, operations, or product stakeholders as needed