The user authenticates through the shared Supabase sign-in flow.
UtopiaSystem uses one shared sign-in foundation so users can move between supported Utopia apps with the same identity.
Supabase handles authentication, session management, and the platform hooks used to enforce access rules before a user enters the system.
Authentication starts before application access is checked.
The user authenticates through the shared Supabase sign-in flow.
The system validates whether the user account is active and allowed to sign in.
A valid user receives a shared session for supported Utopia apps.
Apps and features are shown based on permissions and scopes.
Users with inactive or resigned status are blocked from signing in through the Supabase custom access token hook.
This means access is stopped at sign-in instead of only hiding features after the user has already entered an app.
The same identity can be used across supported Utopia subdomains.
Users sign in once using the shared Utopia account foundation.
Apps that support shared authentication can read the same active session.
Permissions and scopes decide which apps, features, and data the user can access.
Authentication proves who the user is. Access control decides what the user can open.
The launcher shows apps the user can access and hides apps without access.
Work Space appears only when the user has at least one Work-related permission.
Developer tools are visible only to users with developer.workspace.view.
Recent documentation and system notes.
Adopted Parent Identity v2, enhancing the core identity system and resolving previous identity gaps. This update also includes refreshed branding elements across applications.
The sign-in experience has been revamped for improved usability and security.