Remote Manual · Access

Getting started and account security

Remote manual Sign in Recovery Account Sessions Password workflow Troubleshooting

Enter through the account boundary

Human users authenticate with email and password. The resulting session determines the tenant, role and resources visible to the browser and mobile client.

Login screen

Responsibility

The login page introduces the control-plane boundary and accepts the account email and password.

Empty or malformed input is rejected before authentication.
Rejected credentials use a generic notice so the response does not disclose whether an account exists.
Access tokens are short-lived and refresh tokens anchor the longer session.
The browser is intended for administration and oversight. Day-to-day PLC operation remains available through the PlcConsole client.

Validation state

Required fields and email format are checked before submission.

Rejected credentials

The framed notice remains clear without exposing account details.

Active Context

Confirm tenant, user and role before making changes

The header identifies the signed-in user and effective role. A platform administrator sees an additional Acting on behalf of line only after entering a tenant context. Tenant-scoped screens then operate against that tenant’s sites, PLCs, people and policies.

If the displayed context is unexpected, return to the tenant directory before creating, editing or archiving records.

Password Recovery

Recover access without revealing account existence

Use this public flow when the current password is unavailable.

Request a reset link

Workflow

Enter a syntactically valid email address.
The application returns the same generic confirmation whether or not the account exists.
Rate limits apply by account and source address.
The emailed token is short-lived and single-use.

Set the replacement password

Workflow

Enter the new password twice and resolve any mismatch notice.
A successful reset revokes active sessions and returns the user to sign-in.
A used, expired or invalid link is rejected and cannot be replayed.

Email validation

Malformed addresses are rejected locally.

Generic confirmation

The response does not reveal account existence.

Password mismatch

Both password values must agree.

Successful reset

Existing sessions are revoked.

Invalid link

Used or unavailable tokens cannot be reused.

Account Settings

Change a known password from the active session

Account settings dialog

Responsibility

The header theme control changes the persisted appearance preference.
Password change requires the current password, new password and confirmation.
Authentication and validation failures use a framed dismissible notice that returns after each failed submission.
Application rate limits slow repeated attempts.
A successful change revokes active sessions and redirects directly to sign-in.

Session Guide

Know what the session carries and when it ends

A successful sign-in creates an independently revocable human session. The browser uses short-lived access tokens while refresh-token rotation maintains the longer session.

Situation	Expected behavior	User action
Normal access-token expiry	The browser refreshes the authenticated session while its refresh token remains valid.	Continue working. Sign in again only if the session can no longer be renewed.
Log out	The current browser session is revoked.	Sign in again to create a new session.
Password changed	All active sessions are revoked, including the one used to change the password.	Return to sign-in and use the new password.
Password reset completed	The single-use reset token is consumed and existing sessions are revoked.	Sign in with the replacement password. Do not reuse the reset link.
User or tenant disabled	Access stops until the responsible administrator restores an allowed lifecycle state.	Contact the tenant or platform administrator rather than repeatedly retrying credentials.

Tenant context matters: the identity line states who is signed in. Acting on behalf of appears only when a platform administrator has entered a different tenant context. Confirm both before changing tenant-scoped data.

Password Decisions

Choose change or recovery based on what you know

Use Account when the current password is known

Open Account from the application header.
Enter the current password.
Enter and confirm a new password between 10 and 64 characters.
Resolve any framed validation or authentication notice.
Submit once and expect to be returned to sign-in.

Use Forgot password when access is lost

Open Forgot password? from the sign-in screen.
Enter a syntactically valid email address.
Read the generic confirmation; it intentionally does not reveal whether the account exists.
Open the newest reset link and set the replacement password.
Sign in again after the successful reset.

If an error repeats: read the notice rather than submitting continuously. Wrong-password and reset attempts are application-rate-limited. An expired, used or malformed link cannot be repaired and requires a new recovery request.

Troubleshooting

Separate identity, session and authorization problems

Sign-in rejected

Verify the complete email address and password once. The generic response does not identify which value is wrong. If the password is unknown, use recovery instead of repeated guessing.

Signed in, screen missing

This is usually authorization or tenant context, not authentication. Confirm the displayed role and tenant, then ask an administrator to inspect the relevant permission assignments.

Unexpected tenant data

Stop before making changes. A platform administrator should return to the tenant directory and switch to the intended tenant context.

Theme did not follow the account

The header theme control persists the preference for the signed-in account. Allow the application to load the profile before deciding that the preference was lost.