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

# Projects

A **project** is the unit of configuration in IDlayr. Each project holds:

* A **mode** — `sandbox` or `production`.
* A set of **credentials** (`client_id` / `client_secret`).
* A list of **allowed networks** representing the MNOs the project can route traffic to.

You'll typically have multiple projects per organisation — one per environment (sandbox / production), one per use case, one per major integration. Keeping them separate makes analytics, approvals, and credential hygiene cleaner.

## Create a project

1. From the left-hand navigation menu, click **Projects**.
2. Click **New Project** in the top right.
3. In the **Create a new project** panel:
   * **Project name** *(required)*. Use a name that's meaningful to your team — for example `signup-sandbox`, `risk-prod`, `mobile-onboarding`.
   * **Description** *(optional)*. Free text — helpful for teammates.
   * **Mode** — choose **Sandbox** for testing, **Production** for live usage.
4. Click **Create Project**.

The project appears in the Projects list immediately, and you can open it to generate credentials and review configuration. See [Credentials](/enterprise-portal/credentials.md).

## Project modes

<table><thead><tr><th width="112.203125">Mode</th><th width="305.5625">What it does</th><th width="201.1328125">Billing</th><th>MNO traffic</th></tr></thead><tbody><tr><td><strong>Sandbox</strong></td><td>Verification calls are intercepted by IDlayr and return simulated results based on the MSISDN suffix or test IP. Full response shape, no real carrier traffic. See <a href="/pages/NJ632gJ5pAEFPuxEy2hJ">Sandbox testing</a> for the full per-product sandbox map (MSISDN suffix tables, what's simulated and what isn't).</td><td>None — sandbox checks don't consume billed balance.</td><td>None — no calls reach MNOs.</td></tr><tr><td><strong>Production</strong></td><td>Live integration. Real verifications against real numbers and devices.</td><td>Billed per check.</td><td>Yes — traffic reaches the approved MNOs.</td></tr></tbody></table>

## Going live

A project created in **Production** mode does not automatically have live traffic enabled. Production enablement is **manually approved** by IDlayr against a specific use case and the carriers it depends on. To start the approval flow:

1. Create the production project in the Portal.
2. Contact your IDlayr account team to request enablement. Provide the project name, the use case, and the markets / MNOs you need.
3. Once approved, your project's allowed networks are updated to include the carriers in scope.
4. Generate production credentials, store them as build/runtime secrets, and cut over from your sandbox project.

This step is intentional: production traffic touches mobile network operators under our commercial agreements with them, so each new live use case needs a deliberate enablement step. The Portal lets you create the project; live traffic stays gated until the approval is recorded.

## Project lifecycle

* **Renaming** is safe and has no impact on credentials or running integrations.
* **Revoking credentials** affects the project immediately — see [Credentials](/enterprise-portal/credentials.md).
* **Deleting** a project is irreversible and is not possible through the portal.

## What's next

* [**Credentials**](/enterprise-portal/credentials.md) — issue the OAuth2 keys your backend will use.
* [**Allowed networks**](/enterprise-portal/allowed-networks.md) — review which MNOs your project is approved to route to.
* [**Verification logs**](/enterprise-portal/verification-logs.md) — inspect activity once your integration is making calls.
* [**Analytics**](https://docs.idlayr.com/enterprise-portal/analytics) — monitor usage and performance across your projects


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.idlayr.com/enterprise-portal/projects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.