Invite Members

Lora workspaces are built around shared shortcuts. Once you have a few to work with, the natural next step is bringing in the rest of your team.

Who can invite

Every active member can invite by default, including Members and Moderators. The Workspace Owner can enable Restrict invitations to Admins, which limits sending to Admins and the Owner.

You can invite someone at your own role or below, so nobody has to invite a person as a Member first just to promote them afterwards:

Your role	You can invite as
Member	Member only — the invite form shows no role choice
Moderator	Member or Moderator
Admin	Member, Moderator or Admin
Workspace Owner	Member, Moderator, Admin or Workspace Owner

On the Paste emails tab a Role field appears as soon as you have more than one role to choose from; it starts on Member. The same rule applies to a Role column on the Upload CSV tab.

On the Free plan roles are locked and everyone is an Admin, so everyone you invite joins as an Admin and the Role field is greyed out, with a note that roles unlock on Basic. A Workspace Owner can still choose Admin or Workspace Owner. An Admin or Owner can change someone’s role after they join on Basic and above.

Enterprise organizations can disable invitations completely. While this option is active, nobody can send a new invitation.

How to invite

Go to Administration → Members.
Click Invite.
On the Paste emails tab, enter the email addresses you want to invite. You can paste a list separated by commas, spaces, or new lines.
If the Role field is there, choose the role these people should have. Everyone on this tab gets the same role.
Click Send invites.

Each invitee gets an email with a link to join the workspace. Once they accept, they show up with the role you chose. A pending invitation keeps its role even if the workspace changes plan before the person accepts. If their email already belongs to a workspace member, Lora tells you which addresses it skipped instead of creating a duplicate.

Invite a list from a CSV file

Use this when you’re onboarding a whole team at once, or when the roles differ per person.

Go to Administration → Members and click Invite.
Switch to the Upload CSV tab and drop your file in, or click Choose file.
Check the mapping. Lora matches your column headers automatically — a column called Email, Email Address, or Work Email becomes Email, Role, Permission, or Access Level becomes Role, and the name and job-title columns an HR export ships are matched the same way. If it picked the wrong column for a property, change it with the dropdown beside that property.
Read the notices under the mapping. They name every row Lora is leaving out, by line number.
Click Send invites.

Your file needs one column of email addresses. Everything else is optional:

Column	Required	What it does
Email	Yes	One address per row
Role	No	`Member`, `Moderator`, `Admin`, or (Workspace Owners only) `Owner`. A blank Role cell joins as Member — or as Admin on Free
Full name	No	Fills in the person’s name so they don’t have to type it
First name	No	Use together with Last name when your export splits the two
Last name	No	Joined with First name into one name
Job title	No	Also matches `Position` or `Designation`

You can keep an export from Personio, BambooHR, Workday, or Google Workspace exactly as it comes — name, email, and job title in one file, nothing to strip out first.

Note: Up to 200 rows per upload. If your file is longer, Lora uses the first 200 and tells you so. Read Invitation limits before you plan the rest — pending invitations have a separate cap that a second upload can run into.

A few things Lora does with your file, and tells you about:

Rows it can’t invite are listed by line number — a missing address, an address that isn’t valid, or an address that already appeared earlier in the file. The rest of the file still goes out.
A repeated address is invited once, using the role, name, and job title from the first row it appeared in.
A role you can’t assign becomes your default role. You can only assign your own role or below, so a Member’s admin row, or an Admin’s owner row, is changed — to Member, or to Admin on Free. Only a Workspace Owner can assign Owner. On Free every row becomes Admin, because roles are locked there.
A role Lora doesn’t recognize becomes your default role too — viewer and editor aren’t Lora roles.
A name or job title it can’t use is simply left blank. Unlike a Role column, these never cost anyone their invitation: the person just fills the field in themselves.

What the invitee sees

The name and job title you supply are filled in for them, not decided for them. When they accept, their name already shows in the members list — no more waiting for everyone to introduce themselves — and they still land on the welcome screen with whatever you supplied already filled in, where they can correct the spelling, add a profile picture, and continue. One click instead of a form.

Invitation limits apply to CSV uploads too. A file that would push the workspace past its member limit is refused as a whole rather than partway through, so you never end up half-invited.

Invite from Google Workspace

If your organization uses Google Workspace, you can pick teammates straight out of your company directory instead of typing or pasting addresses.

Go to Administration → Members and click Invite.
On the Paste emails tab, click Add from Google Workspace.
The first time, Google asks you to approve read-only access to your organization’s directory. After that, the picker opens straight away.
Search or scroll to find people, check the ones you want, and click Add. They’re added to the Paste emails tab alongside anything you’ve already typed.
Click Send invites.

This is a faster way to fill in the invite list, not a different kind of invitation — everyone you add still receives the same invitation email and joins the same way as any other invite. Lora only reads names and email addresses from the directory while the dialog is open; nothing about the directory itself is stored. If your Google account isn’t a Workspace account, or your admin has turned off directory sharing for Lora, you’ll see a note explaining that and a shortcut back to pasting emails.

Invitation limits

Limit	Value
Email addresses per CSV upload	200
Pending invitations per workspace	200
Members per workspace	20 on Free, counting active members and pending invitations together. No member limit on paid plans
CSV file size	10 MB

Those two 200s are different limits, and the second is the one you’ll meet when onboarding a large team. Pending invitations are a standing total, not a per-upload allowance. Once a workspace has 200 invitations outstanding, the next one is refused until some of them are accepted, revoked, or expire. Invitations expire 30 days after they’re sent.

So inviting 600 people isn’t three uploads back to back. Invite the first 200, let people accept, then invite the next group. Revoking invitations you no longer expect anyone to accept frees up room straight away.

Managing pending invitations

Pending invitations live in Administration → Members until they’re accepted, revoked, or they expire. From there you can resend or revoke any pending invite.

Suspending and removing members

When someone is on parental leave, taking a sabbatical, or otherwise away for an extended period, Admins and Owners can suspend them without deleting their account. A suspended person cannot sign in to or open that workspace. Their Lora account and Private shortcuts remain in place. Restoring the membership gives them access again.

To remove someone permanently, use the Remove action on their row. Their Workspace and Unlisted shortcuts stay in the workspace. If they own any Private shortcuts, Lora prompts you about those before the removal completes, so the workspace doesn’t quietly lose access to them.

An Owner can’t be suspended or removed directly. Another Owner must be assigned first.

Best practices

Use the address the person will use to sign in. An email domain does not place someone into a workspace automatically; the invitation grants access.
Lean toward inviting at Member, not Admin, once your plan lets you choose — including in a CSV Role column. Admins can change billing on Basic and Business, suspend other people, and edit any shortcut that isn’t Private — invite at Admin when there’s a reason to. On Free everyone is an Admin; review roles when you upgrade (see Members and roles).
Start with a small pilot. Five or ten people creating shortcuts give you a useful sample of what slugs and folders your workspace actually needs before you open the doors to everyone.

FAQ

Lora says the invitation limit has been reached The workspace already has 200 pending invitations, which is the maximum. Revoke the ones you no longer expect anyone to accept, or wait for people to accept the ones already sent, then invite the rest. See Invitation limits.

Only some of my CSV rows were invited Lora lists every row it left out, by line number, before you send — a missing address, an address that isn’t valid, or an address that already appeared earlier in the file. If the count you sent was lower than you expected, that list is the reason.