What your invited person receives

When you send an invitation, you should know what the other person sees on the other side. This page is the recipient's view, in order, for any of the three roles.

The email

When an email service is configured for your workspace, the recipient receives a branded bilingual invitation email. Subject: You've been invited to join the workspace on Jadiroon. The body has three parts:

• A short opening line naming the inviter and the workspace.
• A button labelled Accept invitation linking to /invite/{token}.
• A plain-text fallback URL underneath, in case the button does not render.

If no email service is configured, the invitation modal shows a copy-link button and a WhatsApp share button — paste the link into any message. The invitation modal also offers these fallback share options regardless of whether email fired, so you always have a way to hand the link to the invitee.

The token is a long random string. It is single-use and expires in seven days.

The accept page

/invite/{token} opens with the editorial split-panel that the rest of authentication uses — the brand statement on one side, the form on the other.

The form is short:

• Full name — pre-filled if the inviter typed one when sending the invitation; editable.
• Password — minimum eight characters; no maximum.

There is no email field — the email is implied by the token.

A submit button labelled Create account completes the flow.

What happens after submit

For an HR administrator or a line manager invitation, the recipient is logged in and lands on /{slug}/app — the administrative workspace.

For an employee invitation, the recipient is logged in and lands on /{slug}/me — the employee portal. A welcome notification is already in their bell.

In both cases, the person's User record is created with the role you assigned, and a corresponding Person record is linked to it (or created if none existed yet).

What can go wrong

• Expired token — the page shows a polite message that the link is no longer valid and instructs the recipient to ask the inviter to resend.
• Already-accepted token — same message; the same token cannot be used twice. If the recipient has lost their password, they should use the Forgot password flow on /login instead.
• Mistyped password (under eight characters) — the form shows an inline validation note; submit is blocked until corrected.

What the recipient cannot do at this stage

The accept form does not let them choose a workspace, a role, or settings of any kind. Their workspace and role are decided by the inviter. There is no profile setup, photo upload, or preference selection at this point — those are all available later, on their own time, in their profile page.

Next

The previous pages covered all three invitation flows from the inviter's side. The next page picks up the first login moment from the employee's perspective — useful both as orientation for employees themselves and for HR teams writing welcome materials.