> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blockgence.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Accounts and organizations

> How access works, what an organization is, the roles and how work is shared.

## Access by invitation

Blockgence has no open sign-up. To get in:

**1. Request an invitation**

From the public website, with **Request an invitation**. If you investigate on your own, the organization is
optional.

**2. Wait for approval**

Once the request is approved, you get a single-use link to join an organization or, if you are an independent
investigator, to open an individual account.

**3. Create your user**

You choose your password with the link. Then you sign in at [app.blockgence.com](https://app.blockgence.com) with
your email and password, or with **Continuar con Google** (continue with Google) if it is enabled.

> [!NOTE]
>
> If the server has it enabled, you can turn on a second factor (TOTP codes from an authenticator app) from your name's
> menu. Your organization can require it. API and MCP keys do not ask for a second factor: protect them like a password.

## Organizations

Every person belongs to an organization. The organization sets:

* **The plan**, which determines the rate limit and the monthly credit quota (see
  [Credits and limits](https://docs.blockgence.com/en/get-started/credits-and-limits.md)). On the `enterprise` plan, the quota belongs to the whole
  organization: the web app and the keys of all its members share it.
* **What is shared:** a case belongs to whoever created it, who can share it with one person in the organization or with
  all of it, to view or to edit.
* **What is isolated:** no one outside your organization sees your cases, your private labels, your Guard watches or
  your audits.

An **independent investigator** has an individual organization with a single member.

## Roles

| Role | What they can do |
| - | - |
| `admin` | Everything an analyst can, plus managing the organization: inviting people, changing roles, deactivating accounts, creating organization keys and downloading the change log. |
| `analyst` | Investigate, create and share cases, add labels, watch addresses with Guard and use the copilot. |
| `viewer` | Read-only: sees the cases the organization shares and runs queries that save nothing. Cannot create, edit or share cases. |

Anything a `viewer` cannot do returns `403` with `error: "read_only"`. A key belonging to a person with the `viewer`
role is read-only too. See [Errors](https://docs.blockgence.com/en/api/errors.md).

## What you see is your account's, whatever you use

An API key acts as its owner. With it you see and create the same cases and labels as in the web app. If the account is
deactivated, its keys stop working (`401`).

> [!TIP]
>
> For an integration that does not depend on a person (a system at your company), an admin can create an
> **organization key**. See [API keys](https://docs.blockgence.com/en/get-started/api-keys.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.