> For the complete documentation index, see [llms.txt](https://kb.mago.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.mago.io/mago-stage/mago-stage-client-apps/select-the-mago-stage-environment.md).

# Select the Mago Stage environment

Mago Stage can connect to Mago Cloud or to a customer-managed corporate server.  Controllers and receivers must use the same environment before they can connect and work together.

### Mago Cloud

Mago Cloud is the default environment for standard Mago-hosted deployments.

No server configuration is normally required when using Mago Cloud. Open the application and continue to sign-in or receiver activation.

Mago Cloud requires access to the endpoints listed under **Cloud connectivity**.

### Corporate server

Select a corporate server when the organization hosts its own Mago Stage environment.

Obtain the exact server address from the organization administrator before continuing.

The address may resemble:

`https://api.magosrv.com`

or:

`https://api.magosrv.com/api`

Use the address supplied by the administrator. Do not guess the hostname, protocol, port, or path.

### Set a corporate server

You can select a corporate server from the sign-in screen or receiver activation screen.

1. Open Mago Stage.
2. Go to the sign-in or receiver activation screen.
3. Open the **Settings** control.
4. Select **Set corporate server**.
5. Enter the address supplied by the administrator in **Corporate Server URL**.
6. Include `https://` when required.
7. Select **Save**.
8. Wait while Mago Stage retrieves the server configuration.
9. Sign in or activate the receiver in the selected environment.

On the receiver activation screen, the Settings control appears near the lower-right corner.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F0wcjnJHcIS5x8mlM1xVh%2Fselect-environment-menu.png?alt=media&amp;token=0112664e-aacb-4b5b-bf82-eee895814d59" alt=""><figcaption></figcaption></figure>

### Confirm the environment

Before signing in or activating a receiver, confirm that:

* The address was copied correctly.
* The protocol is correct.
* The hostname resolves through DNS.
* The device trusts the server certificate.
* The server is reachable from the device’s network.
* The controller and receiver use the same environment.
* The organization account and licenses exist in that environment.

If the corporate server cannot be reached, Mago Stage may be unable to retrieve its configuration.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Fr1yMHISLnS1Aukc26zRO%2Fcorporate-server-address.png?alt=media&amp;token=b8d7407f-bf22-4ce7-9d7b-a2871e8a573e" alt=""><figcaption></figcaption></figure>

### Return to Mago Cloud

To remove the corporate-server setting and return to Mago Cloud:

1. Open the sign-in or receiver activation screen.
2. Open **Settings**.
3. Select **Use cloud server**.
4. Complete device authentication when requested.
5. Wait while the corporate-server configuration is cleared.
6. Sign in or activate the receiver using Mago Cloud.

Depending on the device, authentication may use:

* Device password
* PIN
* Fingerprint
* Face recognition
* Another supported device-authentication method

Device authentication protects the server setting from unauthorized changes.

### What happens when the environment changes

Changing the Mago Stage environment:

* Signs the current user out
* Clears the active server configuration
* Disconnects the device from the previous environment
* Requires the user to sign in again
* Requires receivers to be activated in the new environment
* Changes which organizations, users, receivers, Stages, policies, and licenses are available

Changing environments does not transfer data between Mago Cloud and a corporate server.

A Stage, user account, receiver activation, or license created in one environment is not automatically available in another environment.

### Controllers and receivers

A controller and receiver can connect only when both use the same Mago Stage environment.

If a receiver is missing from the controller:

1. Confirm the environment selected on the controller.
2. Confirm the environment selected on the receiver.
3. Confirm that the receiver is activated in that environment.
4. Confirm that both devices can reach the environment.
5. Confirm that the receiver is online.
6. Confirm that the organization permits access to the receiver.

### Troubleshooting

#### The corporate server does not load

Confirm that:

* The server address is correct.
* The address includes the required protocol.
* DNS resolves the server hostname.
* The device is connected to the required network or VPN.
* The server certificate is trusted.
* Required firewall and proxy rules are in place.
* The Mago Stage server is running.

#### Sign-in fails after changing servers

User accounts belong to a specific Mago Stage environment.

Confirm that:

* The account exists on the selected server.
* The correct sign-in method is being used.
* The organization has enabled the expected identity provider.
* The user has received an invitation or account from that environment.

#### A receiver requires activation again

Receiver activation belongs to the selected environment.

When a receiver changes from Mago Cloud to a corporate server, or from one corporate server to another, it must be activated in the new environment and may require an available display license.

#### The expected organization or Stage is missing

Organizations and Stages are not transferred between environments.

Return to the environment where the organization or Stage was created, or contact the organization administrator.
