Inviting people
Invitations are how new people join your organization on Lurno. You paste a batch of email addresses, pick one role and one scope for the batch, and Lurno emails each person a link. Until someone opens that link and finishes setup, their invitation sits in a pending list you can watch and re-send from. The flow is identical whether you’re adding a colleague who will build content or a learner who will take a course.
What this does
Section titled “What this does”Everything to do with members and invitations lives on one screen: People, in the People section of your navigation. It has two tabs — People (the directory of everyone already in the organization) and Invitations (everyone who has been emailed but hasn’t finished joining). The Invite button in the top right opens a four-step wizard that sends the batch.
There is no separate “invitations” page. If you have an old link to one, it redirects to People with the Invitations tab already open.
Before you start
Section titled “Before you start”- You need permission to create users in the organization. Without it the Invite button is visible but disabled.
- Decide which role the whole batch should start with. Everyone in one batch gets the same role; you can change individuals afterwards. See Roles & permissions.
- Decide the scope that role applies at — the whole organization, or one sub-organization, branch, group, or program. See Sub-organizations & structure.
- Make sure you’re working in the organization you want people to land in. The wizard invites into the organization you’re currently switched to; you cannot invite into a different one from here.
- Have the email addresses ready as text you can paste. The wizard takes up to 100 addresses per batch.
Send invitations
Section titled “Send invitations”- Open People from your navigation and choose Invite.
- Step 1 — Who. Pick Type or paste emails and paste the addresses into the box, separated by commas or new lines. A live counter under the box reports how many are valid, how many are duplicates, and how many are malformed, so you can fix the list before moving on. The second tile, Upload a CSV file, is marked Coming soon and cannot be selected yet.
- Step 2 — Role. Choose one role from the list. Roles show their description where they have one. Every address in this batch gets this role.
- Step 3 — Where. Choose the scope the role applies at. It defaults to the whole organization. If your organization has sub-organizations, branches, groups, or programs you’re allowed to assign at, they appear here grouped by kind, with a search box.
- Step 4 — Review. Check the count, the role, and the scope. Add an optional personal message (up to 500 characters) that goes into the invitation email.
- Choose Send invitations.
Each address gets its own email and its own link, valid for 7 days. The batch immediately appears on the Invitations tab.
Note that step 3 sets where the role applies — it does not put anyone into a group. To place people into a group, add them from the directory after they exist; see Groups.
You can only invite someone with a role whose permissions you already hold yourself. Picking a role that would grant more than you have is refused when you send, so an administrator can’t quietly hand out access above their own level.
Track and re-send
Section titled “Track and re-send”The Invitations tab lists this organization’s invitations, most recently sent first. Each row shows the address, a status badge, who sent it and how long ago, and when it expires.
- Pending — sent, not yet accepted. These rows carry a Resend button, which issues a fresh link.
- Accepted — the person finished setup and is now in the directory.
- Expired — the seven-day window elapsed. Use Resend while the row is still pending, or send a new invitation.
There is no cancel or revoke control on this screen today. An unwanted invitation will lapse on its own when it expires; if the person has already accepted, off-board them from the directory instead — see Offboarding & data requests.
What the invitee sees
Section titled “What the invitee sees”The link opens a short setup page headed You’ve been invited, naming who invited them, which organization, and which role. Below that they see a plain-English preview of what that role will let them do. They enter a display name and, if they’re new to Lurno, a password of at least 12 characters — someone who already has a Lurno account leaves the password blank and keeps their existing one. Choosing Accept and continue finishes the join and sends them to the sign-in page.
Email and password is the only sign-in method available today. Single sign-on, passkeys, and multi-factor authentication are listed as Coming soon under Organization settings → Sign-in methods and cannot be turned on from there.
Seat limits bite at this moment, not when you send. If accepting would push the organization past the member limit on its plan (or past the allocation given to that sub-organization), the invitee — not you — sees the refusal on this screen. Watch your headroom before sending a large batch. See Billing & plans.
Managing members in a sub-organization
Section titled “Managing members in a sub-organization”My organizations shows your organization tree, and each organization in it has a People panel listing that organization’s members, with Invite (the same four-step wizard) and a per-row remove control. Reaching the screen needs the same permission as the directory; the invite and remove controls appear only for the built-in organization-administrator role. See Sub-organizations & structure.
Reference
Section titled “Reference”| Control | What it does |
|---|---|
| Invite | Opens the four-step wizard. Disabled without permission to create users. |
| Emails (step 1) | Comma- or newline-separated addresses. 100 per batch; duplicates and invalid addresses are counted, not sent. |
| Role (step 2) | One role for the whole batch. Changeable per person later. |
| Where (step 3) | The scope the role applies at: organization, sub-organization, branch, group, or program. |
| Message (step 4) | Optional text added to the invitation email, up to 500 characters. |
| Status | Pending, Accepted, or Expired. |
| Resend | Issues a fresh link. Offered on pending rows only. |
| Expiry | 7 days from the moment the invitation is sent. |
| Export | Downloads the directory as CSV. Not related to invitations. |
Troubleshooting
Section titled “Troubleshooting”The Invite button is greyed out. You can see the directory but don’t hold permission to create users. Ask someone who manages roles in your organization.
Sending was refused because of the role I picked. You can’t invite with a role that grants more than you hold yourself. Pick a narrower role, or ask someone with wider access to send that batch.
Sending was refused with a message about the organization. The wizard invites into the organization you’re currently working in. Switch into the target organization first, then send.
The person can’t accept — they see a message about the plan. The organization is at the member limit on its plan, or at the allocation given to that sub-organization. Whoever manages billing needs to upgrade or rebalance, then the person can retry the same link. See Billing & plans.
The invitation email never arrived. Ask the person to check spam, confirm the address on the Invitations tab is spelled correctly, then Resend. If your organization sends from its own domain, confirm that setup completed — see Email from your domain.
The link says it isn’t valid. Invitation links last seven days, and each one can only be used once. Resend from the pending row to issue a new link.
“Above 100 — paste fewer.” That’s the per-batch limit. Split the list and send it as several batches.
Someone is already in the directory. Search for them on the People tab rather than inviting them again — they may be suspended rather than missing.