CredVault
Dashboard

Pragma Sign In & Account

Pragma uses the CredVault account system. A user should not need a separate Pragma-only account. Their CredVault identity controls whether they can download, open, and use paid or free Pragma features.

Supported Sign-In Methods

Pragma can use the same account methods as the CredVault platform:

  • Email and password.
  • Google sign-in.
  • GitHub sign-in.
  • Account sessions created from the dashboard or billing flow.

The frontend sign-in page is:

Example
/ide-auth

The user-facing download and app pages connect to the same auth flow:

Example
/pragma
/download
/pragma/workspace

What Happens During Sign In

When a user signs in:

  1. CredVault verifies the user.
  2. The backend creates or confirms the user's session.
  3. The user's plan and access are checked.
  4. Pragma receives a valid app session.
  5. The desktop app can load the user's settings, plan, Drive access, and backend-connected features.

Free users should be able to install and open Pragma with the limits assigned to the free plan. Paid users should be routed through billing when they choose a paid plan.

The important behavior is:

  • Free plan: let the user continue after sign-in.
  • Paid plan: route the user to payment first, then return them to download or app access.
  • Enterprise plan: require organization or seat provisioning.

Account Data Users Should See

Inside the app and dashboard, a user should be able to see:

  • Name.
  • Email.
  • Role or plan.
  • Account ID.
  • Current operating system.
  • Days active or clocked in.
  • Pragma access state.
  • Settings and personalization options.

Security Notes

Pragma should never expose raw passwords, payment secrets, OAuth secrets, or backend service tokens in the app. The desktop app should only receive the user session and the minimum tokens needed for app features.

Users should be able to sign out from the desktop app and invalidate the local session.