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

# Inviting Users

Invite a person with an existing Kilo IoT account to your organization and set their access per product area.

You can invite someone to join your organization — as long as they already have a Kilo IoT platform account. The invitation system does not create new accounts. If the person you want to invite has not signed up yet, they need to create an account first, and then you can send the invitation.

Sending invitations requires **Manage users** permission with Edit access.

## Where to Find It

Open the user menu and click **Users**. The organization page opens at `/superIot/organizations/users`, showing the members and pending invitations for your current organization. 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. **Step 1 — Enter the email address.** Type the email address of the person you want to invite. This must be the email associated with their existing Kilo IoT account. Click **Continue**.

   <figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-74e0b2ccf71bca686bad2e14442d0dc25e6a0497%2Finvite-user-email.jpg?alt=media" alt="Step one of the Invite user to organization dialog with the email field and the Continue button"><figcaption></figcaption></figure>
3. **Step 2 — Assign permissions.** The **Page access** section appears, listing each configurable product surface. For every surface, choose one of three access levels:

   * **Edit** — the user can view and make changes
   * **View** — the user can see the surface but not make changes
   * **No access** — the surface is hidden from the user

   The dialog pre-fills defaults for new invitations: Edit on most features, with **Manage users** and **Audit Trail** set to No access. You can adjust any feature before sending.

   Two surfaces have restricted options:

   * **Audit Trail** — only View or No access (no Edit option, because the audit trail is read-only for everyone)
   * **API Keys** — only Edit or No access (no View option, because API key management is self-service)

   <figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-e88cfaa0a25ad026c3dfdfc272590639e1e93de0%2Finvite-user-page-access.jpg?alt=media" alt="Step two of the invite dialog listing each product surface with Edit, View and No access options"><figcaption></figcaption></figure>
4. Click **Send invite**. The system sends an email to the invited user with a link to accept. The invitation is valid for **7 days**.
5. The pending invitation appears in the users table. The row shows the invited email with an **"Awaiting invitation confirmation"** tooltip, and a **Remove** button to revoke the invitation if needed.

## What the Dialog Shows

The invitation dialog shows a subset of the platform's access features. The underlying permission model includes additional features not shown in the current dialog. For the full permission reference, see [Roles and Page Access](/account/roles-and-page-access.md).

## Constraints

* **Existing accounts only.** If the email does not match an existing platform 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 this organization, a new one cannot be sent.
* **No duplicate members.** If the user is already a member of this organization, the invitation is rejected.
* **No Owner invitations.** You cannot invite someone as Owner. Ownership transfer is a separate process handled in [Organization Settings](/account/organization-settings.md).

## What Happens Next

Once the invite is sent, the recipient receives an email with a one-click acceptance link. For what happens on their end, see [Accepting Invitations](/account/accepting-invitations.md). 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 by asking a question.

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

```
GET https://docs.kiloiot.io/account/inviting-users.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.