Invite teammates
Team invitations are managed in company settings, not on a separate standalone page.
When to use this
Team invitations are managed in company settings, not on a separate standalone page. The route https://lengrowth.com/companies/[id]/team/invitations is a compatibility route that redirects into the Team Hub inside company settings. In practice, the invite experience lives at https://lengrowth.com/settings/company with the Team tab selected and the Invites subtab open.
That Team Hub is where LenGrowth keeps the member roster, invite form, pending invitation list, role definitions, and access notes together. It is also where the app checks whether your role is allowed to invite people. If your role does not have permission, the invite controls are hidden and the page shows that restriction in plain language.
The invitation flow supports single invites and bulk CSV uploads. Pending invites are tracked in a table that shows status, delivery state, expiry timing, and actions such as copy link, resend, or cancel.
Use the invite flow when you need to:
Add a teammate to a company workspace.
Send more than one invite at a time from a CSV file.
Check whether an invite is still pending, accepted, expired, or revoked.
Resend an invite after the first email was missed.
Cancel an invite before the person accepts it.
Copy a direct invite link for sharing outside the email flow.
If you are looking for personal account settings or billing, use https://lengrowth.com/settings or https://lengrowth.com/subscription instead.
Step-by-step
Select the Team tab.
Open the Invites subtab.
If the Invite team member button is visible, click it.
Choose Single Invite if you want to invite one person.
Choose Bulk Upload if you want to upload a CSV file with many invites.
For a single invite:
Enter the email address.
Choose a role from the role list.
Add a custom message if you want to include one.
Click Send Invite.
For bulk upload:
Upload a CSV file.
Use the format email, role, message.
Keep the email column populated for every row.
Fix any row-level errors before sending.
Click Send X Invites once the preview is valid.
The single-invite form validates the email address, requires a role, and shows a success message when the invite is sent. The bulk uploader validates email format, role names, file size, and batch size. The current UI accepts up to 100 invites per batch.
The pending invitation list can be filtered by status. On desktop it appears in a table; on smaller screens it renders as stacked cards. Each invite shows the email, role, sent date, status badge, delivery status, and the time remaining before expiry.
After a successful invite, the pending invite list refreshes and the new invitation appears with its delivery state. If the invite email was sent successfully, the delivery column shows that status. If the email failed or is still queued, the list shows that as well.
Each invite can be copied as a direct link. The copied link uses the public invitation route pattern /invites/[token]. That route is where the invited person signs in and accepts the invite.
If the invite has not expired, you can resend it or cancel it from the actions menu. Canceling an invite makes the current invitation invalid, but the history remains visible in the workspace.
Common problems
If you do not see the invite button, your role does not have permission to invite members. The Team Hub shows a clear message in that case.
If the invite form rejects the email, check the address for spelling and formatting mistakes. The form requires a valid email address before it can submit.
If a CSV upload fails, check these items first:
The file must be a .csv file.
The file must be under 1 MB.
The CSV should include email, role, and message columns in that order.
Each role must be one of the roles accepted by the current workspace.
The batch must stay within the 100-invite limit.
If an invite does not arrive, open the pending invitation list and check whether the delivery state says queued or failed. If needed, resend the invite from the actions menu.
If the invite is older than 14 days, it is expired. The Team Hub notes that pending invites expire after 14 days, so you will need to send a new invite.
If someone opens an invite link and sees the wrong email address, they may be signed in with a different account. The invite acceptance page checks that the signed-in email matches the invited email before it lets the person accept the invitation.
Related articles
Invitation links use the route pattern /invites/[token]