> For the complete documentation index, see [llms.txt](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces/how-to/invite-members.md).

# Invite members

Bring teammates into your organization. You choose their organization role and, for members, which workspaces they can see.

## Prerequisites

* You're an **Admin** in the organization.
* The recipients' email addresses.

## Steps

{% stepper %}
{% step %}
Sign in and switch to the organization you want to add to.
{% endstep %}

{% step %}
Go to **Settings → Organization** and scroll to the **Organization members** card.
{% endstep %}

{% step %}
Select **Invite member** in the top-right of the card.
{% endstep %}

{% step %}
**Email addresses**: Enter a comma seperated list of email addresses, or enter each address and press Enter. You can add up to 100 at once. Invalid or duplicate addresses are flagged in the list.
{% endstep %}

{% step %}
**Role**: pick:

* **Admin** for full access, including organization settings and member management. Automatically gets every workspace.
* **Member** for access only to the workspaces you grant.
  {% endstep %}

{% step %}
**Workspace access** (Members only): tick each workspace they should see. For each ticked workspace, set their workspace role: **Admin**, **Editor**, or **Viewer**.
{% endstep %}

{% step %}
Select **Send invites**. DevAlly emails each recipient a link.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
Each invite appears in the **Invites** tab as **pending** until the recipient accepts.
{% endhint %}

## What happens next

* The recipient selects the link in their email and follows [Accept an invite](/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces/how-to/accept-an-invite.md).
* If they don't act before the invite expires, you can [revoke and re-invite](/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces/how-to/revoke-an-invite.md).

## If something goes wrong

{% hint style="warning" %}
**"You've reached your member limit"**: your plan caps the number of seats. Remove an inactive member, or upgrade.
{% endhint %}

* **Some emails skipped**: DevAlly skips emails that already belong to the organization or already have a pending invite. The toast lists which were skipped and why; the rest still send.
* **Member needs more workspaces**: invite first, then adjust later via [Manage workspace access](/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces/how-to/manage-workspace-access.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces/how-to/invite-members.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
