> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Inviting Users
> Invite new users to your Rootly organization through the web UI and assign Incident Response or On-Call roles, team memberships, and permissions.
Use invitations to add new users to your Rootly organization. You can invite one or more users at a time, assign roles during invitation, and let users join using the sign-in method configured for your organization.
Invitation emails are sent automatically after you create an invitation.
You can invite multiple users at once by entering more than one email address in the invite flow.
## Invite Users
In the top-left corner, click the drop-down next to your organization name and select **Organization Settings**.
Select **[Members](https://rootly.com/account/memberships)**, then click **+ Invite Member**.
Enter one or more email addresses for the users you want to invite.
You can separate multiple email addresses using:
**Commas**
[maria@candly.org](mailto:maria@candly.org),[tim@candly.org](mailto:tim@candly.org),[kirija@candly.org](mailto:kirija@candly.org)
**New lines**
[maria@candly.org](mailto:maria@candly.org)
[tim@candly.org](mailto:tim@candly.org)
[kirija@candly.org](mailto:kirija@candly.org)
**Spaces**
[maria@candly.org](mailto:maria@candly.org) [tim@candly.org](mailto:tim@candly.org) [kirija@candly.org](mailto:kirija@candly.org)
You can optionally assign:
* **Incident Response role**
* **On-Call role**
When inviting multiple users at once, the selected roles apply to all invited users in that batch.
If no role is selected, the team’s default role is applied.
Click **Invite** to send the invitation email.
## What You Can Do
From the invite flow, you can:
Add a single user or invite multiple users at the same time.
Set Incident Response and On-Call roles during invitation.
Allow Rootly to apply your team’s default roles when no role is selected.
Send users directly into the account creation or sign-in flow.
## Role Assignment
You can assign roles during invitation to control what access a user receives after joining.
* **Incident Response roles** control access to incidents, workflows, retrospectives, and related configuration
* **On-Call roles** control access to schedules, escalation policies, alerting, and responder workflows
If a role is not selected, Rootly assigns the team’s default role for that product.
Configure default roles in **Organization Settings** to standardize access for new users.
Ensure you have available seats for the roles you’re assigning. If seats are limited, some roles may be unavailable.
## Email Requirements
Invitations require valid email addresses that meet your organization’s requirements.
* **Valid format**
* **Not already a member**
* **Allowed email domain**, if your organization restricts invitations by domain
Rootly validates email addresses during invitation creation. Invalid addresses will return an error.
## User Acceptance and Sign-Up
After an invitation is sent, the user receives an email with a link to join your organization.
When they open the invitation, they can complete sign-up using one of the methods available in your environment, such as:
* **Google**
* **Slack**
* **SSO**
* **Email and password**
If the user signs up with email and password, the password must include:
* At least **10 characters**
* One **lowercase** letter
* One **uppercase** letter
* One **number**
* One **special character**
Once sign-up is complete, the user is added to your organization with the assigned roles.
## Bulk Invitations
When you invite multiple users at once, Rootly processes invitations in batches.
* Invitations may take longer to appear for larger batches
* Individual errors do not prevent valid invitations from being created
* You can review progress from the **Invitations** page
Large invitation batches may take a few minutes to complete.
## Who Can Send Invitations?
Invitation access depends on the user’s assigned permissions.
* **Owners** can send invitations
* **Admins** can send invitations
* **On-Call Admins** may be able to assign On-Call access, depending on configuration
Contact your team administrator if you do not have permission to invite users.
## Best Practices
* Configure default roles before inviting users with standard access needs
* Double-check email addresses before sending invitations
* Assign roles during invitation to reduce manual updates later
* Use bulk invitations when onboarding multiple users at once
* Review pending invitations and resend or remove them as needed
## Troubleshooting
Confirm the email address is correct, ask the user to check spam or junk folders, and resend the invitation if needed.
Invitations cannot be edited after they are sent. Delete the pending invitation and create a new one with the correct details.
Make sure the user is signing in with the same email address that received the invitation. If the invitation is no longer valid, send a new one.
This usually means your plan has reached its seat limit for that role type, or you do not have permission to assign that role.
At the limit, the invitation fails with an error that names the plan that ran out:
> You have reached the seat limit for your On-Call plan. Please email our team at [sales@rootly.com](mailto:sales@rootly.com) to upgrade your plan.
To check current usage, go to **Organization Settings → [Members](/managing-users/managing-users)** and hover over the information icon beside the **Incident Response** or **On-Call** column header.
The email may be invalid, already belong to an existing member, or fail your organization’s domain restrictions.
Large invitation batches may take time to process. Check the Invitations page to review progress.
## Related Documentation
View, resend, or delete pending invitations.
Manage existing users in your organization.
Learn more about Incident Response and On-Call roles.
Understand how permissions are controlled across teams and products.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.