Authentication
Understand how authentication works in Mimasa AI and configure secure access for your team. The same mechanisms govern access whether users sign in through the browser or systems connect through the API.
Authentication Methods
Human users typically sign in with email and password or through single sign-on, while programmatic integrations authenticate with an API key or an OAuth 2.0 access token. Regardless of method, every authenticated session or credential is scoped to a specific workspace and carries a role that determines which resources it can read or modify. Administrators can require stronger authentication, such as SSO, for all members of sensitive workspaces.
SSO Configuration
Single sign-on lets your team authenticate to Mimasa AI using your existing identity provider rather than a separate password, and it is configured by a workspace administrator from the security settings. Once enabled, user roles can be mapped from identity provider groups, so access changes made in your directory are reflected in Mimasa AI automatically. SSO also centralizes session and credential lifecycle management under your existing identity governance.
API Keys
API keys are the credential of choice for server-to-server integrations that act as the workspace itself rather than as an individual person. A key is generated from workspace settings, shown once, and should be stored in a secrets manager rather than in source code. Keys inherit role-based permissions like any other credential, so scope each key narrowly and rotate it periodically or immediately after any suspected exposure.