AACSearch / guide
Console authentication
Sign in to the console, recover access, choose the right credential for the job and manage your sessions.
AACSearch uses three kinds of credentials. They are not interchangeable:
| You are… | Credential | Guide |
|---|---|---|
| A person working in the dashboard | Console session + organization role | this page |
| An application calling the tenant API | An API key with the right scope | API keys |
| An identity provider syncing members | A SCIM token | SCIM |
Never share credentials across layers
A console session must never be used as an API key, and an API key must never be pasted into a browser, a ticket or a chat. If a credential leaked, revoke it — see sessions and token rotation.
Register and recover access
Register in Console, verify your email and select an organization. Use Forgot password to request a reset link. Open the most recent link and choose a new password. If an email does not arrive, check spam and ask the deployment operator to verify delivery; do not assume that a successful form submission proves delivery.
Only configured social/OIDC providers are shown on the sign-in screen. An organization requiring SSO refuses password sign-in for its members.
Manage sessions
Open Profile → Security to inspect active sessions, revoke another session or change your password. Keep the current session identifiable before revoking access on other devices. Organization owners manage member permissions separately under Team/Roles.
Two-factor authentication
Profile → Security also manages TOTP two-factor authentication. Enabling it asks for your password, shows a QR code to scan into an authenticator app, and then shows backup codes once — store them somewhere safe before closing the dialog, because they are the only way back in if you lose the authenticator.
Only authenticator apps are supported. There is no email or SMS code, so a lost device is recovered with a backup code or by an administrator.
Verify: sign out and back in — you are asked for a code from the app.
Do not share session cookies, reset links, API keys or provider secrets. If access remains unavailable, contact support with the time, operation and a redacted error. For payment-related access, see billing.
Plans, usage and credits
What each plan grants, how requests are counted, what an AI credit buys and costs, how RUB payments and renewals work, and what happens when a limit is reached.
Single sign-on
OIDC sign-in for the console, the callback URL to register with your identity provider, requiring SSO for an organization, and where SSO ends — provisioning and authorization live elsewhere.