Sign in

Invite a user to the company account

The Owner (or an Admin) invites a person by email and chooses the roles they will hold — including roles built from the Omnichannel reference permission sets — so the invitee can set up their own access.

When this happens: Owner opens User Management — Invite User.

Step by step

  1. 1

    Open User Management and clicks Invite User.

    EasyCRM shows the invitation form: email, roles (multi-select, every role of the company), Reports To, message, allowed sign-in methods, expiry.

  2. 2

    Enter the email, selects one or more roles (e.g. A role created from the *Operator* reference set) and, optionally, the Supervisor the invitee reports to.

  3. 3

    Click Send Invitation.

    EasyCRM checks the email (not an active user, no pending invitation) and the role set. EasyCRM creates the invitation with a hashed single-use token and the chosen expiry (default 14 days). Emails the invitee: [Owner] invited you to [Company], with the redemption link and the optional message. EasyCRM records InvitationSent and shows the invitation in the Invitations list as *Pending*.

Other paths

Admin invites a user

Performs steps 1–4. The Admin role is disabled in the role list with the hint Only the account Owner can invite administrators

Owner invites an administrator

At step 3 selects the Admin role. The invitation proceeds normally; the invitee becomes an Admin, not the Owner.

If something goes wrong

Email already active or invited

At step 5 the email belongs to an active user or has a pending invitation. EasyCRM shows the FR-01-027 inline error; nothing is created.

Email delivery fails

At step 7 the email cannot be delivered. The invitation is kept; the Owner sees Invitation saved, but the email could not be delivered. Use 'Copy invitation link' to share it manually

Good to know

  • Only the Owner can invite a user with the Admin role.
  • An invitation may carry several roles; the invitee receives all of them.
  • Omnichannel personas are roles the company created from reference sets; no persona role is seeded.
  • Tokens are single-use and stored hashed; resending rotates the token.