# Environments

> **Set up with an AI agent:** Connect Chrona MCP for documentation, setup guidance and configuration recipes. Server: https://mcp.chrona365.com/mcp (Streamable HTTP; authentication: None). Your agent needs separately authorized Dataverse tools to apply changes. In Copilot Studio, after importing Chrona, add the Chrona Scheduler connector to your agent alongside Microsoft’s Dataverse tools. [Connection guide](https://chrona365.com/install-with-an-agent).

Connect each Power Apps environment to your Chrona account once, from a Chrona [board](https://chrona365.com/glossary/board). Your organization's first environment connects at once. Each further environment needs an owner or admin's approval.

## Connect your first environment

1. Install Chrona in the environment: [Install Free Scheduler](https://chrona365.com/docs/scheduler/install) or [Install Workforce Scheduler](https://chrona365.com/docs/workforce/install).
2. Open the board and select **[Auto Schedule](https://chrona365.com/glossary/auto-schedule)**, then **Try a free sample run**.

The environment is connected and appears on **Environments** in the portal. A System Administrator, or someone with the **Chrona Scheduler Admin** role, connects it. It connects whether or not someone has signed in to the portal first.

## Connect a further environment

1. On the new environment's board, select **Auto Schedule**, then **Try a free sample run**. Chrona records a request and asks for approval.
2. An owner or admin opens the portal and approves the request under **Needs your attention**.
3. Within 24 hours, select **Try a free sample run** again on that board.

An environment that already has its current connection key reconnects without another approval.

## The Environments page

**Environments** lists every Power Apps environment connected to your account, with the date it connected. **Open in Power Apps** takes you to it.

An owner or admin can select **Disconnect** to take an environment off the account. It stops optimizing until someone connects it again. Past solves and usage stay.

## Every environment counts

Production, test and development all count under the organization's plan. A [worker](https://chrona365.com/glossary/worker) with the same record ID in two environments counts once, so a full production copy adds no duplicate workers. See [Plan and billing](https://chrona365.com/docs/account/billing) for the free five and how workers are counted.

---
Product: Account and billing
Language: English
Canonical: https://chrona365.com/docs/account/environments
