Skip to content
Prego Prego Docs

Authentication

This guide explains how people and apps authenticate to Prego at a high level.

Overview

  • Admin console — Users sign in through the login or sign-up flow your tenant uses. After success, the app holds a session (often a token such as a JWT) for later requests.
  • Platform APIs — Backend services validate that session or token and enforce tenant and user context so data stays scoped to your organization.
  • My AI — Knowledge, Autopilot, and Chat use the same identity model as the rest of the tenant. Requests go to paths under /{companyId}/api/my-ai/* through Prego’s API gateway. Details: My AI API.
  • Configuration — Base URLs and auth endpoints are set per environment (production vs. sandbox). Your administrator or integration guide lists the values you should use.

Login and sign-up

  1. Open your admin console sign-in page (URL from your onboarding materials).
  2. Complete login or self-service sign-up if your tenant allows it.
  3. The browser or app stores the session; keep devices and browsers patched and logged out on shared machines.

Single sign-on (SSO)

Many enterprises connect an identity provider (IdP) so users sign in with corporate credentials. Enablement is done with Prego support or your customer success contact according to your contract.

Password reset and lockouts

Use the Forgot password flow on the admin console sign-in page, or your SSO portal if your tenant uses it. If you are stuck, ask an organization admin or Prego support. Short answers: FAQ — I forgot my password or cannot sign in.

For developers

Use the API overview for how to pass tokens on server-side integrations. Do not embed long-lived secrets in public web pages.

Next steps