Start here
Use the workspace address supplied during setup and the email on your invitation. A public website demo, purchase preview or local app preview does not create a production account.
Hosted owners should use their provisioned workspace. Self-hosted owners should use their installation’s address; their operator manages its authentication and mail configuration.
Check and recover
- Open the latest invitation or your workspace’s sign-in page. Confirm the email address before continuing.
- Use the sign-in method shown on that page. If you already have a password, use it; otherwise use an email sign-in link when offered. Google sign-in depends on deployment configuration.
- For a forgotten password, use the password reset option. Open the newest reset email and finish setting a password before trying again.
- If the link is invalid or expired, request a new one. Do not keep reopening an older email. Check spam and any organization mail quarantine.
- If you see a wait message after repeated requests, wait for its retry period. Repeatedly submitting the form can extend the interruption.
- After signing in, check the organization switcher. One account can belong to multiple workspaces, and choosing the wrong one can make the expected records appear missing.
If it still does not work
Ask the workspace owner to confirm that your membership is active and the invitation uses the same email. A self-hosted operator should also check the configured app URL, allowed authentication redirects and mail delivery.
When to contact the team
Escalate if the newest valid link still fails, or the owner confirms access but the workspace cannot open. Include the workspace address, sign-in method, approximate time and exact error. Keep passwords and sign-in links out of the request.
Related: Invite your team and fix access problems.