# Login and email verification

Sign in to INSIDE with your operator account and verify your email address when your website requires it.

*Release 3.3 · admin, operator*

**Settings › Account › Operators** · **Settings › General Settings › Admin**

## What it is

**Login** checks your operator credentials and whether your account can enter INSIDE. Your website may also require email verification, a second authentication factor or single sign-on.

Email verification confirms your registered email address once. It is separate from the email codes used for **2-Factor Authentication**.

## Who uses it and why

Operators sign in to work in INSIDE. Users with the **Settings** or **Manager** role and the required operator permissions maintain accounts and help resolve locked accounts or missing verification emails.

## Where to find it

Open your organisation's INSIDE sign-in page. Users with the **Settings** or **Manager** role and the required operator permissions administer accounts under **Settings › Account › Operators**.

Powerfront manages **Enable Email Verification** under **Settings › General Settings › Admin**. Ask Powerfront to change this requirement for your website.

## How it works

1. Enter your registered **Email** and **Password**, then select **Login**.
2. Complete any authentication-code or single sign-on steps shown.
3. If email verification is required and your account is unverified, INSIDE stops sign-in. It sends a verification email if one has not already been sent.
4. Open the link in that email. After successful verification, return to sign in.

The verification link expires after 24 hours. An authorised account manager can use **Send Verification Email** from the operator's action menu to send another.

Disabled accounts cannot sign in. A missing website, maintenance, password expiry or a network restriction can also prevent entry. App-only accounts have additional app-access checks.

## Configure it

Ask Powerfront to enable email verification if your organisation requires it. It is off by default.

Use **Settings › Account › Operators** to check the account's email address, **Enable Operator** status and website assignments. A manager needs **Allow Unlock Account** to use the account-unlocking control.

### Settings

| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Enable Email Verification | Settings › General Settings › Admin | website | Off | Powerfront, on request | Operators must verify their email address at least once before signing in. |

### Permissions

| Permission | Lets you |
|---|---|
| Settings | Manage operator accounts within your permitted websites, subject to Settings Permissions. |
| Operators | Allow operator administration within Settings Permissions. |
| Manager | Manage permitted operator accounts, subject to Manager Permissions. |
| Allow Unlock Account | Allow a manager to unlock an operator account. |

## Limits and good to know

- Six failed sign-in attempts can lock your account. Incorrect supplied second-factor codes also count towards this limit.
- A successful credential check clears previous failures for an enabled account. Unlocking an account also clears its failed-attempt count.
- Password recovery and account unlocking are separate tasks. A password reset does not enable a disabled account.
- Maintenance can prevent client operators from signing in even with valid credentials.
- Visitor chat access does not create an operator account.

## Depends on and works with

### This feature uses

- **Requires** [Operator accounts](ADM-007.md): You need an enabled operator account to sign in.
- **Configured in** Admin settings and feature switches (managed by Powerfront): Powerfront manages the website email-verification switch.
- **Configured in** [Roles and permissions](ADM-008.md): Roles and delegated permissions control account administration and app access.
- **Configured in** [Website, channel and subsite access](ADM-009.md): Website assignments determine the websites your account can access.
- **Configured in** [Password changes and recovery](SEC-002.md): Password checks, recovery and optional expiry affect password sign-in.
- **Configured in** [Two-factor authentication for operator sign-in](SEC-003.md): An account or website may require a second authentication factor.
- **Configured in** [Operator sign-in network and email restrictions](SEC-028.md): Configured network restrictions can prevent sign-in.
- **Works better with** [Single sign-on with SAML 2.0](SEC-005.md): SAML single sign-on can direct an operator to an identity provider.
- **Works better with** [Single sign-on with OAuth 2.0](SEC-006.md): OAuth single sign-on can direct an operator to an identity provider.
- **Related** [Logout and remembered computers](SEC-004.md): See logout and remembered-computer guidance for what happens to your session after sign-in.
- **Related** [Sign-in and chat request limits](SEC-025.md): Repeated failed password or second-factor checks can lock your operator account.

### Used by

- **Required by** [INSIDE console](CON-001.md): Sign in with an operator account to enter the console.
- **Required by** [Mobile console](CON-033.md): Sign in with an operator account to use the mobile console.
- **Required by** [Two-factor authentication for operator sign-in](SEC-003.md): These factors apply to the operator password sign-in flow.
- **Required by** [Logout and remembered computers](SEC-004.md): A successful operator sign-in creates or resumes a session.
- **Required by** [Single sign-on with SAML 2.0](SEC-005.md): Provider authentication still leads to INSIDE operator-account admission checks.
- **Required by** [Single sign-on with OAuth 2.0](SEC-006.md): Provider identity leads to INSIDE operator-account admission.
- **Required by** [Operator access tokens](SEC-011.md): Password-based token issuance authenticates an operator account.
- **Required by** [INSIDE operator CLI](EXT-023.md): The CLI signs in using an operator account.
- **Related** [Operator accounts](ADM-007.md): Review sign-in and email verification when preparing a new operator account for use.
- **Related** [Password changes and recovery](SEC-002.md): Use password recovery when you cannot complete password sign-in.
- **Related** [Sign-in and chat request limits](SEC-025.md): Repeated failed sign-ins can lock an account and require an authorised account manager to unlock it.
- **Related** [Operator sign-in network and email restrictions](SEC-028.md): Check the operator's default website network policy when ordinary sign-in is denied.

## FAQ and troubleshooting

### Why am I being asked to verify my email address?

Your website requires verification and your operator account has not completed it. Open the verification email before trying to sign in again.

### My verification link has expired. What should I do?

Ask your account manager to use **Send Verification Email** for your operator account. Open the new link within 24 hours.

### Why is my account still locked after resetting my password?

An authorised account manager must also unlock the account. Resetting your password does not remove the disabled-account restriction.

### Why does Login take me to another sign-in page?

Your account uses single sign-on. Complete the sign-in process with your organisation's identity provider.

### Why can I sign in through the app but not the browser?

Your account may be restricted to app use. Ask your account manager to check your account type and app access.