# Logout and remembered computers

Understand how INSIDE keeps you signed in, remembers factor verification and ends an operator session.

*Release 3.3 · operator, supervisor*

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

## What it is

An operator session keeps your identity available while you work in INSIDE and reconnect after a connection interruption. Signing in elsewhere with the same account can end your earlier session.

A remembered computer separately stores proof of a successful second-factor check. Remembering verification does not remove the password requirement for a new password sign-in.

## Who uses it and why

Operators sign out when they finish work and respond to connection or inactivity messages. Supervisors with the **Settings** or **Manager** role and the required operator-administration permissions can use **Force Logout** where INSIDE offers it for an online operator.

## Where to find it

Use **Logout** in the desktop console or **Log Out** in the mobile console to leave INSIDE. In **Settings › Account › Operators**, open an eligible online operator's action menu to find **Force Logout**.

Personal inactivity preferences are under **Settings › Account › My Account › Auto Logout**. Powerfront manages the website-wide inactivity sign-out switch under **Settings › General Settings › Admin**.

## How it works

After sign-in, your browser retains session information so the console can identify you on subsequent requests and reconnects. If the session can no longer be resumed, you need to sign in again.

When INSIDE detects another loaded session for the same operator, it signs out the earlier session. Use a separate account for each person.

At the factor prompt, **Don't ask again for this computer** remembers verification in that browser. Its default lifetime is 30 days. Powerfront can change this period. Clearing browser cookies or using another browser means the remembered proof is unavailable there.

**Force Logout** ends the selected operator's session and shows them a message identifying who signed them out. The action is offered only for eligible online accounts.

## Configure it

Ask Powerfront to turn on **Auto logout operators after a period of inactivity** if you require inactivity sign-out. With this enabled, the console's inactivity prompt gives you 60 seconds to respond. Select **Yes I'm here** to continue working.

The available **Auto Logout** preferences depend on your role and website policy. See the inactivity and end-of-shift guidance for those choices.

For single sign-on, ask Powerfront to configure the appropriate **Remote Logout URL** if your organisation needs a provider logout destination.

### Settings

| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Auto logout operators after a period of inactivity | Settings › General Settings › Admin | website | Off | Powerfront, on request | Use the inactivity prompt to sign operators out when they do not respond, rather than only changing availability. |

### Permissions

| Permission | Lets you |
|---|---|
| Settings | Open permitted operator administration screens, subject to Settings Permissions. |
| Operators | Allow operator administration within Settings Permissions. |
| Manager | Open permitted operator administration screens, subject to Manager Permissions. |

## Limits and good to know

- Closing a tab is not the same action as explicitly signing out. Use the sign-out control when leaving the console.
- Session cookies and remembered-factor verification have separate lifetimes. Remembering a factor does not guarantee that a session stays open for 30 days.
- A connection interruption may allow session recovery. Explicit sign-out normally ends the session so it cannot be resumed.
- Provider logout behaviour depends on your organisation's single sign-on configuration.
- **Force Logout** is unavailable for some accounts, including targets with the **Manager** or **Developer** role.

## Depends on and works with

### This feature uses

- **Requires** [Login and email verification](SEC-001.md): A successful operator sign-in creates or resumes a session.
- **Configured in** Admin settings and feature switches (managed by Powerfront): Powerfront manages the website inactivity sign-out switch.
- **Configured in** [Roles and permissions](ADM-008.md): Roles and delegated permissions control access to operator administration.
- **Configured in** [Automatic logout after inactivity](CON-004.md): Inactivity prompts and exit behaviour affect when an operator leaves the console.
- **Configured in** [Single sign-on with SAML 2.0](SEC-005.md): SAML settings supply the remote logout destination when one is configured.
- **Configured in** [Single sign-on with OAuth 2.0](SEC-006.md): OAuth settings supply the remote logout destination when one is configured.
- **Works better with** [Two-factor authentication for operator sign-in](SEC-003.md): Remembered-computer verification can avoid a later second-factor prompt.
- **Works better with** [Operator access tokens](SEC-011.md): The optional remembered-computer function uses an expiring operator access token.
- **Related** [Operator accounts](ADM-007.md): Authorised account managers can use Force Logout for eligible online operators.
- **Related** [Console connection and recovery](CON-005.md): Connection recovery explains when an interrupted console session can resume or needs a new sign-in.

### Used by

- **Required by** [INSIDE console](CON-001.md): The console needs a valid signed-in session.
- **Required by** [Console connection and recovery](CON-005.md): A valid operator session is needed to reconnect to the console.
- **Required by** [API request testing and diagnostics](EXT-019.md): The console uses your signed-in operator session.
- **Required by** [INSIDE operator CLI](EXT-023.md): Saved CLI authentication uses a native operator session and remains subject to session validity.
- **Required by** [Operator CLI requests and browser login](EXT-024.md): Browser login reuses the current operator session rather than creating a separate credential.
- **Configures** [Automatic logout after inactivity](CON-004.md): Website session policy determines automatic logout behaviour.
- **Configures** [INSIDE Store App for mobile](CON-034.md): Operator session rules apply, and the app can receive a duplicate-session disconnect notice.
- **Enhances** [Two-factor authentication for operator sign-in](SEC-003.md): A remembered computer can skip the code prompt on later password sign-ins.
- **Enhances** [INSIDE API](EXT-018.md): Operator requests can use an active operator session.
- **Enhances** [Browser API requests](EXT-020.md): Operator requests can carry the current session identity and react to session disconnection.
- **Related** [Login and email verification](SEC-001.md): See logout and remembered-computer guidance for what happens to your session after sign-in.
- **Related** [Single sign-on with SAML 2.0](SEC-005.md): Provider sign-in opens an operator session, and logout follows the configured provider destination.
- **Related** [Single sign-on with OAuth 2.0](SEC-006.md): Provider sign-in opens an operator session, and logout follows the configured provider destination.
- **Related** [Operator access tokens](SEC-011.md): Logout and remembered-computer guidance explains how remembered verification differs from a console session.
- **Related** [Certificates and protected browser data](SEC-026.md): Remembered-computer verification needs readable protected browser data and a valid remembered token.

## FAQ and troubleshooting

### Why was I signed out when I signed in on another computer?

INSIDE can detect a duplicate loaded operator session and sign out the earlier one. Avoid sharing an operator account.

### Why do I need my password on a remembered computer?

The option remembers factor verification. A new password sign-in still requires your password.

### Why did I return to Login after a connection problem?

INSIDE could not resume your session. Sign in again and complete any verification requested.

### Why is Force Logout missing?

The operator must be online and eligible for that action, and you need access to operator administration. INSIDE does not offer it for every account.

### Does signing out also sign me out of my identity provider?

A configured **Remote Logout URL** can send you to the provider's logout process. Ask Powerfront to check your website's single sign-on configuration if you return directly to INSIDE instead.
