Sign-in and signup
How sign-in works on AACWorkflow Cloud — email + verification code and Google OAuth — and how invites interact with your account.
AACWorkflow Cloud supports two sign-in methods: email + verification code (default) and Google OAuth (where enabled). Both create your account automatically the first time you sign in — there's no separate signup step.
For token details (JWT cookie, PAT, daemon token), see Authentication and tokens.
Email + verification code sign-in
Enter your email on the sign-in page → AACWorkflow sends a 6-digit code → enter it → the server verifies it and signs you in. This is the default method and needs no setup on your side.
Google OAuth
Where enabled, the sign-in page shows a Sign in with Google button — click it and complete the standard OAuth flow to sign in with your Google account instead of an email code.
The redirect must match exactly what AACWorkflow expects. If Google shows redirect_uri_mismatch, see Troubleshooting.
Joining a workspace via invite
If someone invites you to a workspace and you don't have an AACWorkflow account yet, signing in for the first time (with either method above) creates your account automatically — you don't need to do anything separately before accepting the invite. See Members and roles for how invites work day to day.
Next
- Authentication and tokens — JWT / PAT / daemon token categories and usage
- Members and roles — inviting people and what each role can do
- Troubleshooting — verification code not received, OAuth
redirect_uri_mismatch