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

# Account, organization and billing

> Sign up, secure your account, create an organization, add an approver, and choose, change or cancel a plan.

This page covers everything around the product itself: your account, your organization, the people who can approve, and your plan. When it is done, continue with [Create an API key](https://docs.atlasent.io/quickstart/api-key.md).

## 1. Create your account

**1. Sign up**

Open [console.atlasent.io/auth/sign-up](https://console.atlasent.io/auth/sign-up?utm_source=docs\&utm_medium=quickstart). Sign up with Google, or with an email address and password.

**2. Confirm your email**

Email sign-ups get a confirmation email with a 6–8 digit code and a link. Type the code on the "Check your email" page, or open the link. Both expire shortly and work once. If they have expired, sign in with the same address: the sign-in page offers to resend the confirmation email when an address is not yet confirmed.

**3. Turn on an authenticator app**

Owners and admins must use an authenticator app (TOTP) before the Console opens administrative pages, such as members, keys and billing. You are asked to enrol the first time you open one. Save the recovery codes it shows you: they are how you get back in if you lose the device.

> [!NOTE]
>
> **Forgot your password?** Use **Forgot password** on the sign-in page. The reset link works once and expires. After you set a new password, sign in again with it. An expired or already-used link shows "Invalid or Expired Link". Request a new one.

## 2. Create your organization

After your first sign-in, the Console opens onboarding (`/onboarding`) and creates your organization. That organization is your tenant: policies, keys, decisions and evidence all belong to it, and nothing is shared with other organizations. To add more later, use **Create New Organization** in the organization switcher.

You start on the **Free** plan. Nothing is charged, and no payment details are requested.

> [!TIP]
>
> Check the organization name in the header before you create keys or policies. Every key, policy and permit is bound to the organization it was created in. A key from one organization cannot act in another.

## 3. Approvals, and adding a second person

A held request is approved from the **Approval Queue** (`/approval-queue`). Who may approve depends on the policy:

* **No independent approver required** (the hold the quick start creates, for example): an owner or admin of the organization can approve it.
* **Independent approver required:** someone other than the person who started the change must approve. **You can never approve a change you started, on any plan.** A one-person workspace keeps such a request on hold, by design, until a second person approves it.

To add that second person:

**1. Invite them**

Go to **Team** (`/team`) and choose **Invite a Person**. They accept the emailed invitation and sign in to your organization.

**2. Give them an approver grant**

On **Team → Members** (`/team/members`, owners and admins), use **Issue approver grant** for that person. A grant decides which consequential actions they may approve. It is separate from their role.

**3. They approve from My Approvals**

A held request appears in the approver's **My Approvals** (`/my-approvals`). A link to a single request opens it there after sign-in.

## 4. Plans

| Plan | Price | For |
| - | - | - |
| **Free** | \$0 | A hosted workspace to learn the authorization loop in advisory mode. 1,000 hosted evaluations per month. |
| **Team** | $299/month or $2,990/year | Shared policy, approval workflows and **hosted fail-closed enforcement** of protected actions. |
| **Enterprise** | Custom annual contract | Organization-wide authority, identity integration, audit export and contract terms. |

Developer Cloud (\$49/month) is planned and not yet on sale. Local blocking with the public MCP gate and SDKs is free for everyone, with or without an account. The [pricing page](https://atlasent.io/pricing?utm_source=docs\&utm_medium=quickstart) is the current source for what each plan includes.

### Upgrade

**1. Open billing**

Go to **Settings → Billing** and choose **Upgrade plan**. Only owners and admins can change the plan.

**2. Pay on the Stripe page**

Choose the plan. You are sent to a Stripe-hosted Checkout page; AtlaSent never sees your card. If you leave Checkout, nothing is charged and you can start again.

**3. Wait for the plan to apply**

Payment, plan and enforcement are three separate steps. Once Stripe confirms the payment, your organization's plan updates. That normally takes seconds; refresh Billing if it has not. Enforcement does not switch on by itself: you turn it on for each protected action when you are ready.

### Change payment method, invoices, cancel

**Settings → Billing → Manage Billing** opens the Stripe customer portal. There you can change your payment method, download invoices and cancel. When a paid subscription ends, your organization returns to Free.

### A payment fails

If a renewal payment fails, Billing shows **"Your last payment failed — update your payment method"** with a button to the portal. Update the card there and Stripe retries it. If the subscription ends unpaid, your organization returns to Free.

> [!NOTE]
>
> **Billing never turns protection off.** Whatever your billing state, AtlaSent keeps evaluating, verifying, denying, holding, auditing and serving evidence. A billing problem can stop you *adding* paid capability, such as upgrading, new keys or activating enforcement. It never weakens a protection that is already running.

## 5. Troubleshooting

| You see | Meaning | What to do |
| - | - | - |
| "Billing details could not be loaded" | The Console could not reach billing. | Use **Retry billing options**. If it persists, contact support. |
| Activation refused, trial cannot activate | A trial can install and test a pack, but cannot switch on enforcement. | Upgrade to Team, then activate. |
| Upgrade or new key refused, entitlement unknown | AtlaSent could not confirm your plan, so it refuses anything that would expand it. Existing protection is unaffected. | Contact support with your organization name. This is not fixed by retrying. |
| Making someone an admin is refused: admin limit reached | An owner has capped the number of admins (**Team → Lock down admin rights**). Pending admin invitations count toward the cap. | Ask an owner to raise the cap or remove an admin first. |
| HTTP 403 `insufficient_scope` | The API key lacks a scope the call needs. | See [key scopes](https://docs.atlasent.io/quickstart/api-key.md). `production.deploy` also needs `idp_broker:mint`. |
| HTTP 429 `QUOTA_EXCEEDED` on evaluate | The monthly evaluation allowance is used up. | Upgrade, or wait for the next month. |
| HTTP 429 `RATE_LIMITED` | Too many requests in a short time. | Retry with backoff. This is not a plan limit. |
| A request stays on hold | It is waiting for an approval. If its policy requires an independent approver, that must be someone other than the person who started it. | Open the **Approval Queue**. For an independent approval, add a second person (step 3 above). |
| "Request Not Found" on an approval link | The request expired or was resolved, or you cannot see it: the wrong organization is selected, or you have no approver grant covering it. AtlaSent gives the same answer in each case, so it does not reveal which requests exist. | If the page offers **Switch to** another organization you belong to, use it. Otherwise select the right organization, check your grant on **Team → Members**, then open **My Approvals**. If it is still missing, ask for a fresh request. |

For deny codes on evaluate and verify, see [Deny codes](https://docs.atlasent.io/concepts/deny-codes.md).

## Get help

Email **[support@atlasent.io](mailto:support@atlasent.io)** for sign-in and billing help. Include your organization name and what you were doing; never send an API key, password or authentication code. See [Get help](https://docs.atlasent.io/trust/get-help) for what to include, and [Contact](https://docs.atlasent.io/trust/contact.md) for security reports.


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