> For the complete documentation index, see [llms.txt](https://docs.chirpwireless.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chirpwireless.io/account/inviting-members.md).

# Inviting Members

Adding someone to your Chirp home takes just a few steps. Once they accept, they can see and interact with the sensors, dashboards, and automations you choose to share with them.

## What You Need

* **Manage Users** permission with Edit access. If the **Add user** button is greyed out, you do not have this permission — ask your home owner or another member who manages access.
* The person you want to invite must already have a Chirp account. The invitation system does not create new accounts. If they have not signed up yet, they need to register first.

## Where to Find It

Click your name or avatar in the bottom-left corner to open the user menu, then select **Users**. The members page shows everyone who belongs to your home, plus any invitations that have not been accepted yet. Click the **Add user** button at the top of the page.

## Sending an Invitation

1. Click **Add user**. The **"Invite user to organization"** dialog opens.
2. **Enter the email address.** Type the email associated with the person's Chirp account. Click **Continue**.
3. **Set permissions.** The **Page access** section appears, listing each section of Chirp. For every section, choose one of three access levels:

   * **Edit** — they can view and make changes
   * **View** — they can see the section but not change anything
   * **No access** — the section is completely hidden from them

   The dialog starts with sensible defaults: Edit on most sections, with **Manage Users** and **Activity Log** set to No access. You can adjust any section before sending.

   Two sections have restricted options:

   * **Activity Log** (under **Reports** > **Audit Trail**) — only View or No access. There is no Edit option because the Activity Log is read-only for everyone.
   * **API Keys** — only Edit or No access. There is no View option — API key management is all-or-nothing.
4. Click **Send invite**. Chirp sends an email with a link to join your home. The invitation is valid for **7 days**.
5. The pending invitation appears in the members list. The row shows the invited email with an **"Awaiting invitation confirmation"** tooltip, and a **Remove** button in case you need to revoke it.

## Constraints

* **Existing accounts only.** If the email does not match an existing Chirp user, the invitation is rejected.
* **No self-invitations.** You cannot invite yourself.
* **No duplicate invitations.** If an active invitation already exists for the same email in your home, a new one cannot be sent.
* **No duplicate members.** If the person is already a member of your home, the invitation is rejected.
* **No Owner invitations.** You cannot invite someone as Owner. Ownership transfer is a separate process in [Home Settings](/account/organization-settings.md).

## What Happens Next

Once the invitation is sent, the person receives an email with a one-click link. See [Accepting Invitations](/account/accepting-invitations.md) for what happens on their end. To revoke a pending invitation or manage members after they join, see [Managing Access](/account/managing-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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.chirpwireless.io/account/inviting-members.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.