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

# Access and entry to the team

> Public and private mode of the page, independent access keys and employee login through the panel.

The status page can be used by two different audiences: customers who have enough of the state of services and their team who need a little more. The **Access** tab separates these two cases.

> [!NOTE]
>
> For whom: panel administrator. Required rights: `statuspage.edit` for mode, `statuspage.deploy` for keys.

## Page mode

**Public.** Statuses and published incidents are open without authorization The usual choice if you have customers outside.

**Private.** A visitor needs an access key, and this is done when a page is intended for a corporate customer or internal team, rather than the open Internet.

## Access keys

The key opens a private page and does not depend on the panel: it is checked on the page server, so it continues to work when the panel is not available.

The key has a name and an expiration date that you don't have to specify. The secret is shown once when it's released. Forgot to copy, release a new one, take the old one out of nowhere.

Revocation of the key is effective immediately: the page stops accepting it.

> [!WARNING]
>
> The key is access to the entire page. Give each recipient a separate key, otherwise you won't be able to revoke one without breaking the rest.

## Entrance to the team

Employees come to the page through a bar, they don't have separate passwords for the page.

**1. From the status page**

An employee presses the input in the "Command Entry" block. The page sends it to the panel.

**2. In the panel.**

The confirmation screen opens: which page asks which account you're logging in to and what the page will receive. Until you click Confirm Log in, nothing is transmitted.

**3. Back to the page.**

The panel signs a statement about who you are and what rights you have now, and returns you to the page. The confirmation is valid for one minute and only for this page.

The page gets two things: your name in the panel and the permission slice at that point. The password, the second factor, and the panel session are never transmitted.

> [!NOTE]
>
> The confirmation screen appears each time intentionally. The status page is on a separate server, and silently giving the signed code to anyone who opened the link would mean that someone else's site is taking away the employee's session with one redirect.

If the link is incomplete and the panel doesn't understand which page is asking for entry, the screen will say so. Open the entry again from the status page.

## What the employee sees

The rights to the page are projected from the dashboard: the one who leads the incidents in the dashboard also leads them on the page. The page does not have a separate list of users, and you do not need to start it - accounts and rights live in the same place.

## Verification

> [!TIP]
>
> Private page without a key requests authorization, with the key opens, the input for the command goes through the confirmation screen and returns to the domain of the page.

## Typical errors

> [accordion] Employee receives 'entry unavailable'
>
> Most likely, the page doesn't know the address of the panel: it goes to it with the settings. Open the section and make sure that the sync state is "Synced."

> [accordion] The key stopped working.
>
> Check the expiration date and if it is revoked, the revoked key can not be restored, a new one is released.

> [accordion] After confirmation, it returns to the panel, not to the page.
>
> This is what an out-of-confirmation looks like: it lives for one minute. Start logging in again from the status page.

Related Pages: [Status Page: Overview Z](https://docs.axottle.com/en/statuspage/overview.md), [Registration](https://docs.axottle.com/en/statuspage/appearance.md), [Access and Sessions](https://docs.axottle.com/en/panel/access-and-sessions.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.