> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/plan-and-foundations/environments-and-access.md).

# Environments & Access

Environments, tenants, admin users and API keys — what to set up before the integration work starts.

## Environments

You get a **staging** and a **production** environment. Build and test on staging; production is for live members only.

|                     | Staging                                           | Production                                      |
| ------------------- | ------------------------------------------------- | ----------------------------------------------- |
| Purpose             | Integration build, functional testing, UAT        | Live programme                                  |
| SLA                 | None                                              | 99.9% uptime                                    |
| Throughput          | Lower soft limit                                  | Higher soft limit                               |
| Personal data       | Don't store real members' data — use test members | Real members                                    |
| Performance testing | Not suitable                                      | Request it from Open Loyalty support in advance |

The exact throughput, timeout (60 seconds) and pagination limits are in [Environments capabilities](https://help.openloyalty.io/technical-guide/api-fundamentals/environments-capabilities) and [Limits](https://help.openloyalty.io/technical-guide/api-fundamentals/limits). If you expect more traffic than the soft limit — a launch campaign, a migration — request a limits increase from Open Loyalty support in advance.

## Tenants

A **tenant** is a separate programme with its own members, wallets, campaigns and rewards. Every API path starts with its code: `/api/{storeCode}/…`.

* Use **one tenant per programme**. Separate countries, currencies or legal entities usually mean separate tenants.
* Several brands in one programme can share a tenant — see [Multi-brand programmes and wallets](https://help.openloyalty.io/implementation-guide/plan-and-foundations/multi-brand-and-wallets.md).
* Members, balances and history are not shared between tenants.

Tenants are created in [Global settings › Tenants](https://help.openloyalty.io/administration/settings/tenants). To give an admin access to a new tenant, see [Adding a tenant and giving an admin access to it](https://help.openloyalty.io/faq/adding-a-tenant-and-giving-an-admin-access-to-it).

## Admin users and roles

* Give each person their own admin account — no shared logins.
* Use [roles](https://help.openloyalty.io/administration/settings/roles) to limit what each team can change: for example, marketing can edit campaigns and rewards, support can view members and adjust points, and only a few administrators can change settings.
* Restrict each role to the tenants that team works on.

## API keys

The integration authenticates with an [API key](https://help.openloyalty.io/technical-guide/authentication/access-token-api-key) in the `X-AUTH-TOKEN` header.

* An API key belongs to an admin and acts with that admin's permissions. Create a **dedicated admin for each integration** (e.g. "Integration – e-commerce", "Integration – CRM") with a role that allows only what it needs, and generate its key there.
* One key per integration means you can rotate or revoke one without affecting the others, and the System logs show which integration made a change.
* Keys don't expire unless you set an expiry date. Store them in a secrets manager, never in source code, a browser or an app.
* Keep separate keys for staging and production.

## Configuration across environments

Build the programme's configuration on staging and move it to production when it's accepted:

* **Between environments** (staging → production), use [configuration exports](https://help.openloyalty.io/integrations-and-data-exchange/imports-exports/exports/configuration-exports) and import them module by module, in the order given in [Configuration migration](https://help.openloyalty.io/implementation-guide/data-and-go-live/configuration-migration.md). Webhook subscriptions aren't exported — set them up again in each environment.
* **Between tenants in the same environment**, use [Config duplication](https://help.openloyalty.io/global-management/config-duplication).

## Checklist

* [ ] Staging and production tenants exist, with the same tenant codes where possible.
* [ ] Every person has their own admin account with a role limited to their tasks.
* [ ] Each integration has its own admin, role and API key, per environment.
* [ ] API keys are stored in a secrets manager.
* [ ] No real personal data is loaded into staging.
* [ ] Expected peak traffic is compared with the production limits, and a limits increase is requested if needed.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/implementation-guide/plan-and-foundations/environments-and-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
