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

# Why was I refused?

> Each refusal a new Ankra organisation can meet - payment method, free allowance, trial limit, pipeline approval, two-step sign-in and role - and how to clear it.

Ankra refuses a few first actions on purpose: connecting a cluster without a payment method, a token for an account without two-step sign-in, a pipeline's protected settings nobody approved. Each refusal says what it needs. This page lists them by the words you see, with why each one exists and what clears it.

## Find your message

| You see | Where | Section |
| - | - | - |
| **Add a payment method before you connect a cluster** | Connecting a cluster | [Payment method](#a-payment-method-for-clusters) |
| **A payment method is required to create this cluster.** | Creating a cluster | [Payment method](#a-payment-method-for-clusters) |
| **Run did not start: add a payment method** | A pipeline run | [Free allowance](#the-free-allowance-without-a-payment-method) |
| **The 30-vCPU trial limit would be exceeded. ...** | Creating a cluster or adding capacity to one Ankra builds | [Trial limit](#the-30-vcpu-trial-limit) |
| **Your organisation has used its AI allowance for this month. ...** | Ask Ankra | [Ankra AI](#ankra-ai-stops-answering) |
| **Awaiting authority approval** | The `Ankra pipeline` check | [Pipeline approval](#a-pipeline-waits-for-approval) |
| **Add a second step to sign in first** | Making an API token | [Two-step sign-in](#two-step-sign-in) |
| **Set up two-step sign-in to continue** | Right after you sign in | [Two-step sign-in](#two-step-sign-in) |
| **You can’t open this page with this account.** | Any page | [Your role](#your-role) |

## A payment method for clusters

**What you see.** On **Infrastructure → Clusters → Connect a cluster**, the warning **Add a payment method before you connect a cluster**: "Ankra connects a cluster only for an organisation with a payment method on file. Free credit does not replace it: without one, adding the cluster is refused." Creating a cluster stops on its review step with **A payment method is required to create this cluster.**

**Why.** A pay-as-you-go organisation with no usable payment method is on the free tier. It may not create clusters, connect clusters or order paid playgrounds, whatever credit it holds. The free trial [playground](https://docs.ankra.ai/guides/cluster-sandbox.md) is the one cluster it can start.

**How to clear it.** An organisation owner opens **Settings → Plan and billing** (`/next/organisation/billing#unlock`) and, under **Unlock paid usage**, clicks **Add payment method**. The card is added with Stripe, and the browser comes back to the page. Then try again. Someone who cannot add it reads "Ask someone who manages billing for your organisation to add one." on the connect page.

## The free allowance without a payment method

**What you see.** A pipeline run that did not start is marked **Did not start: add a payment method**. Its notice, **Run did not start: add a payment method**, has an **Open billing** button.

**Why.** A Pay as you go organisation without a payment method gets a small free allowance each calendar month (UTC):

| Allowance | Each month | What counts |
| - | - | - |
| Pipeline minutes | 100 minutes | Wall-clock minutes of steps Ankra builds for you on its own build cluster. A step on your own cluster never counts |
| Ankra AI | USD 1 | The cost of every AI request, on Ankra's model key and on your own key alike |

Both are checked when a run or a request starts, so the one that crosses the line finishes and the next is refused. Once the pipeline minutes are spent, every new run is refused, wherever its steps would have run, because Ankra decides where a step runs after the run is queued.

**How to clear it.** Add a payment method under **Settings → Plan and billing**. Saving it lifts the free tier and its allowance together. Then run the pipeline again.

## The 30-vCPU trial limit

**What you see.** "The 30-vCPU trial limit would be exceeded. An organisation owner must approve paid usage in Plan and billing before adding capacity." Or, when Ankra cannot count: "Capacity could not be verified against the 30-vCPU trial limit. Refresh the provider catalogue and cluster observations, or ask an organisation owner to unlock paid usage."

**Why.** On the Free or Homebuilder plan, until an owner approves paid usage, Ankra refuses to create or grow a cluster it builds for you when the organisation's clusters would then run more than 30 vCPUs. The limit is checked whenever such a cluster grows, from the portal, the API, GitOps or the autoscaler. Connecting a cluster is not refused by it, but a connected cluster's vCPUs count toward the 30. A payment method alone does not lift it. An organisation on Pay as you go, Startup or Enterprise never meets this limit: your plan shows under **Settings → Plan and billing**.

**How to clear it.** An organisation owner opens **Settings → Plan and billing** and goes to **Unlock paid usage**. The section shows the prices. Add a payment method if there is none, tick the box that approves the prices and authorises paid usage and removal of the 30-vCPU trial limit, and click **Confirm charges and unlock**. Anyone else reads **Only an organisation owner can approve charges and unlock the account.** [Billing](https://docs.ankra.ai/platform/billing.md) explains the prices and what they cover.

## Ankra AI stops answering

**What you see**, in **Ask Ankra**:

| Message | Why | How to clear it |
| - | - | - |
| **Your organisation has used its AI allowance for this month.** | The plan's monthly AI allowance is spent and no model key pays instead. In an organisation admitted to the DevOps AI model by Ankra, that model's own allowance is spent too. On Pay as you go, credit pays for Ankra AI past the allowance, so this shows only once there is no credit left | An administrator clicks **Add a model key** and adds the organisation's own model key under **Ankra AI → Models and provider** |
| **An admin has paused Ankra AI for this organisation.** | Someone turned Ankra AI off | An administrator clicks **Turn Ankra AI back on** (**Ankra AI → Autonomy and approvals**) |
| **Ankra AI is unavailable until the overdue invoice is settled.** | An invoice is past its due date | Settle it under **Settings → Plan and billing** (**Open billing**) |
| **Your role cannot use Ankra AI.** | Your role has no access to Ankra AI | Ask an organisation owner for a role that has |

## A pipeline waits for approval

**What you see.** The `Ankra pipeline` check on a pull request reads **Awaiting authority approval**, and the organisation gets a notification **Pipeline authority approval needed: my-org/my-repo (...)**.

**Why.** A pull request may change what a pipeline *does*, but not what it may *touch*: secrets, credentials, caches, CPU and memory, timeouts, services, network access and where a step runs. Those protected settings take effect only once an administrator approves the definition on the default branch. Until then the run is skipped, if a stage depends on them, or runs with the last approved settings.

**How to clear it.** An administrator approves the settings on **Build & delivery → Builds and clusters**, under **Pipeline settings waiting for approval**. The steps are in [Get started with Ankra CI](https://docs.ankra.ai/get-started/ankra-ci.md#7-approve-the-pipeline-once). Approving needs a person: a service-account token, or Ankra AI acting through one, is refused with "A pipeline definition's authority can only be approved by a human administrator".

## Two-step sign-in

**Tokens.** On **API access** in your account, the row **Add a second step to sign in first** takes the place of the **Create token** button until your account has two-step sign-in. The portal asks for it because a token acts as you. Click **Set up two-step sign-in**, which opens **Sign-in and security** in your account, add a passkey or an authenticator app, and come back. [Service tokens](https://docs.ankra.ai/guides/service-tokens.md) covers tokens for automation.

**Organisations that require it.** When an organisation requires a second step, signing in stops at **Set up two-step sign-in to continue**: "Your organisation requires a second step after you sign in, on top of your password or sign-in provider." Choose **Passkey** or **Authenticator app**. You get recovery codes in case you lose your device. While the organisation requires it, you cannot remove your last authenticator: "Your organisation requires MFA, so you cannot remove your last authenticator". [Account security](https://docs.ankra.ai/platform/account-security.md) has the details.

## Your role

| You see | Why | How to clear it |
| - | - | - |
| **You can’t open this page with this account.** | Your role may not open this page | "Ask an administrator of your organisation for access, or sign out and sign in with another account." |
| **This page is not turned on for your organisation.** | The feature is not turned on for the organisation | "Contact Ankra support to have it turned on." |
| **Your role does not allow adding clusters.** | Your role cannot create or connect clusters | Ask an organisation owner for a role that can |
| **Your role cannot show the install command** | The agent install command carries the agent's token, so it needs the `agents.manage` permission | Ask an organisation owner to show it, or to grant you the permission |
| **Your role in my-org can look at these settings but not change them. Owners and admins can.** | Organisation settings such as **Builds and clusters** are read-only for your role | Ask an owner or admin to make the change |

[Roles and access](https://docs.ankra.ai/guides/roles-and-access.md) lists what each role may do.

## Where to go next

* [Billing](https://docs.ankra.ai/platform/billing.md): plans, prices and the payment method.
* [Find your way around Ankra](https://docs.ankra.ai/platform/find-your-way-around.md): where each page in this guide lives.


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