> ## Documentation Index
> Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Cloud environment access

> Verify protected environments and make an environment public.

Veryfront Cloud creates `preview`, `staging`, and `production` environments.
Each environment is protected by default. Use this guide when a browser, CI
check, or API client must reach a deployed environment.

## Check a protected environment

Open the environment URL in a browser signed in as a project member. A protected
environment serves the request when it carries that member's session in the
`authToken` cookie.

To inspect an unauthenticated response, probe a route the project serves:

```bash theme={null}
curl -s -o /dev/null -w '%{http_code} %{redirect_url}\n' \
  <environment-url>/<route>
```

An unauthenticated request receives a `302` sign-in redirect. The sign-in apex
depends on the host serving the environment:

* `*.veryfront.com` redirects to `https://veryfront.com/sign-in`.
* `*.preview.veryfront.org` redirects to `https://veryfront.org/sign-in`.

Sign in on the apex in `redirect_url`. The session cookie is scoped to that
domain.

## Authenticate a non-browser client

A non-browser client can still authenticate by sending the `authToken` cookie
with a project member's session token. Store that token as a secret and account
for its expiration.

`VERYFRONT_API_TOKEN` does not open a protected environment. It authenticates
the CLI against the Cloud API, not requests to the deployed app. A signed-in
user who is not a member of the project gets a `403`.

## Make an environment public

In Veryfront Studio:

1. Open **Environments**.
2. Select the environment.
3. Enable **Public Environment**.
4. Confirm **Make Public**.

Keep protection enabled for internal or unreleased environments.

## Verify it worked

Repeat the route probe:

```bash theme={null}
curl -s -o /dev/null -w '%{http_code} %{redirect_url}\n' \
  <environment-url>/<route>
```

Validate the status that route normally returns. Do not require a `200` from
the environment root when the project has no static page at `/`.

See [Deployment behavior](/docs/code/guides/deploying) for readiness and URL semantics.