Account security and sessions#

Manage sign-in methods, recovery information and active sessions without copying application credentials.

Use the Account site#

Open Altifigence Account from the signed-in account menu. Confirm the account before changing security settings. Profile, authentication, sessions, organization access and billing are different settings; use the matching screen for the problem.

Sign-in methods and recovery#

Use the passkey, authenticator or supported provider flow offered by your account. Complete the on-screen verification before treating a new method as active. Keep recovery codes privately when the setup flow provides them; they are credentials and do not belong in chat, a repository or a diagnostic report.

If a passkey dialog is canceled or unavailable, return to the sign-in page and use an offered alternative or recovery route. Do not copy a desktop credential store, browser cookies or machine-licence files to restore account access.

Review sessions and history#

Open the account’s security/session view and identify the current session.
Review listed devices, times and sign-in events. A location or device label can be approximate.
Revoke an unfamiliar or no-longer-needed session using the provided control.
After revocation, expect the affected product or MCP connection to request sign-in again; verify access from the intended account.

Separate access problems#

Problem	Where to check
Cannot sign in	Account sign-in method, verification and recovery.
Signed in, project missing	Selected organization and project membership.
Desktop local tool unavailable	Machine entitlement and local/WSL runtime.
MCP tool denied	Current tool policy, granted scope and fresh consent.
Usage or payment question	Account billing/usage and the Legal Center.

If access remains blocked, report the time, product, sanitized error and recovery step attempted. Never send a password, passkey material, one-time code, recovery code or token to support.