Sign-up in Context Fabric means creating aDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/exegia/corpora-py/llms.txt
Use this file to discover all available pages before exploring further.
public.users record for a user who has already authenticated. The exegia.auth.signup module provides helpers for all registration paths: converting a freshly authenticated user into a full application profile, starting an anonymous guest session, or linking an OAuth identity to upgrade an existing account.
Register an Already-Authenticated User
If a user has just signed in via email OTP or an OIDC ID token andresult.needs_signup is True, pass their session’s access token to sign_up() to create the public.users record.
Anonymous Sign-Up
Passanonymous=True to start a fresh anonymous session and immediately create a public.users record for that guest user in a single call.
Start an Anonymous Session Only
Usestart_anonymous_session when you need a guest session without creating a public.users profile yet. This is the same underlying call as sign_up(anonymous=True), but isolated so you can defer profile creation.
Create a Profile Directly
create_user_profile inserts a row into public.users (table name from USERS_TABLE = "users", keyed by USERS_ID_COLUMN = "id" from exegia.auth.current_user) using the service-role client. It bypasses RLS and is used internally by sign_up(), but you can also call it directly if you need fine-grained control.
Link an OAuth Identity
link_identity_to_current_user returns a provider authorization URL. Redirect the user to that URL to complete the link. This works for both upgrading an anonymous user (adding a permanent identity) and adding a second provider to an already-permanent user.
Identity linking requires Enable Manual Linking to be turned on in your Supabase project’s Auth settings. The user must have an active session, and the candidate identity must not already be linked to another user.
SignUpResult Fields
True if a new public.users record was created for the user. False when already_registered is set or an error occurred.The combined auth identity and application profile. Set on success and also on the
already_registered path (reflecting the existing record).The Supabase session. Populated when
sign_up() started an anonymous session via anonymous=True.A user-facing message. Set on all non-
ok paths.True when the user already has a public.users record. Defaults to False. No new record is created and current_user reflects the existing profile.sign_up Parameters
JWT of an already-authenticated user. Use this when the user has just signed in via email OTP or an OIDC ID token. Optional — mutually exclusive with
anonymous=True.Extra columns to set on the
public.users row at creation time. Keys must match your schema (e.g. {"display_name": "Alice"}). Optional.When
True, start a fresh anonymous session first, then register that guest user. Defaults to False. Optional — mutually exclusive with access_token.user_metadata to attach to the anonymous user at creation. Only used when anonymous=True. Optional.CAPTCHA verification token for the anonymous sign-in step. Only used when
anonymous=True. Optional.