OpenSana Docs

Auth and Clerk

Configure Clerk as the authentication layer for OpenSana deployments.

OpenSana uses Clerk for user authentication in the web app.

What Clerk Handles

  • sign-in and sign-out
  • user identity
  • tokens passed into the Convex-backed application flow

Deployment Requirements

At minimum you need:

  • NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY
  • CLERK_SECRET_KEY

Operational Notes

  • keep production and non-production Clerk apps separate
  • make sure your allowed origins and redirect URLs match the deployed app URL
  • verify that authenticated users are syncing correctly into the OpenSana user model

What This Does Not Replace

Clerk handles authentication, but authorization still depends on OpenSana’s organization and project permission system.

Environment Variables

Reference for all environment variables, where each one belongs, and what it does.

Email and Resend

Configure transactional email delivery for invitations and onboarding flows.

On this page

What Clerk HandlesDeployment RequirementsOperational NotesWhat This Does Not Replace