> 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/accepting-invitations.md).

# Accepting Invitations

Accept a Kilo IoT invitation — membership invites valid 7 days, ownership-transfer invites with their own acceptance.

When someone invites you to join their organization — or transfers ownership to you — you receive an email with a one-click link. There are two types of invitations, each with its own acceptance flow and expiration window.

## Membership Invitations

A membership invitation adds you to an organization as a new member with the permissions the inviter assigned.

1. You receive an email containing a link with a `?acceptInvitation=` parameter.
2. Click the link. You must be logged in to your Kilo IoT account for the acceptance to succeed.
3. On success, the token parameter is removed from the URL and you are now a member of the organization. The permissions assigned by the inviter take effect immediately.

Membership invitations are valid for **7 days**. After that, the link expires and the inviter would need to send a new invitation.

{% hint style="info" %}
If the acceptance fails — for example because the token has expired, was already used, or was revoked — an error is shown and the token parameter remains in the URL. Ask the person who invited you to send a new invitation.
{% endhint %}

## Ownership Transfer Invitations

An ownership transfer invitation makes you the new owner of an organization. Only the current owner can initiate this, and you must already be a member of the organization before the transfer can happen.

1. You receive an email containing a link with a `?acceptOwnerInvitation=` parameter.
2. Click the link. You must be logged in to your Kilo IoT account.
3. On success, the token parameter is removed from the URL. You are now the organization owner.

After a successful ownership transfer:

* **You** (the new owner) get automatic access across the entire organization. The audit trail remains read-only.
* **The previous owner** retains write access on all product surfaces except the audit trail, which becomes read-only for them. They remain a member of the organization — they are not removed.

Ownership transfer invitations are valid for **24 hours**. This shorter window reflects the sensitivity of an ownership change.

## What Happens on Acceptance

For both invitation types, the system creates access policies based on the permissions granted. One rule always applies: even if the invitation assigned write access to the audit trail, it is automatically downgraded to read. The audit trail is read-only for everyone, including the owner.

An **"Invite accepted"** event is recorded in the [Audit Trail](/reports/audit-trail.md), capturing who accepted and when.


---

# 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/accepting-invitations.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.