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

# Admin quickstart

Create, fund, and configure a compliant Cortecs project

Use this guide if you are responsible for setting up and governing a Cortecs project. If you were invited to an existing project to connect a tool or application, follow the [Member quickstart](/member-quickstart.md) instead.

### 1. Create and fund the project

Register at [cortecs.ai](https://cortecs.ai), then complete the project billing setup:

1. Add your billing address in [**Console > Billing**](https://cortecs.ai/userArea/console?tab=billing).
2. Add a payment method. Credit card is recommended when funds must be available immediately.
3. Top up the project balance.
4. Configure **Auto top-up** if requests must continue without interruption.

See [Billing](/web-console/billing.md) for payment methods, invoices, and balance management.

{% hint style="warning" %}
Requests fail when the project balance reaches zero. Use Auto top-up or monitor the balance to avoid interruptions.
{% endhint %}

### 2. Invite and organize members

Open [**Console > Project**](https://cortecs.ai/userArea/console?tab=project) to invite the people who will use Cortecs. Organize members into teams when departments, workloads, or internal projects need separate settings, budgets, or usage reporting.

See [Teams](/web-console/teams.md) for member assignment, the Default team, and team-specific controls.

### 3. Configure compliance and inference

As a project administrator, translate your organization's compliance, security, and data-processing requirements into enforced project settings before members begin sending requests.

Open [**Console > Inference**](https://cortecs.ai/userArea/console?tab=inference) and review:

* whether individual requests may override the saved configuration;
* Zero Data Retention and Sovereign Cloud restrictions;
* the providers that may process requests;
* quantization, model fallback, maximum tokens, and the provisioning strategy;
* whether any team needs an override of the global settings.

See [Inference Settings](/web-console/inference-settings.md) for all controls. The [Security & Compliance](/security-and-compliance.md) section explains the available data-governance options in more detail.

{% hint style="info" %}
Disable **Allow overwrite** when the saved inference configuration must be enforced centrally. When it is enabled, applications may supply their own inference settings per request.
{% endhint %}

### 4. Set spending limits

Open [**Console > Budgets**](https://cortecs.ai/userArea/console?tab=budgets) to define project, team, user, or API-key limits. Choose the scopes and periods that match your organization's cost controls.

See [Budgets](/web-console/budgets.md) for available scopes and enforcement behavior.

### 5. Hand off to members

Once funding, team assignments, compliance settings, and budgets are ready, members can create their own team-scoped API keys and connect their tools. Send them the [Member quickstart](/member-quickstart.md).