Check access, workspace and permissions
Diagnostic sequence
- Check the product domain, email address and automatically synchronised system clock.
- Confirm that email verification, password source and selected MFA method belong together.
- Select the intended tenant or insideBase workspace after sign-in.
- Compare the licence, active capability and role separately.
- Check whether the action additionally requires write permission or a particular record state.
| Status | Meaning | Next step |
|---|---|---|
401 | Sign-in is missing or expired | Sign in again; never send a token or cookie to support. |
403 | Identity is known but access is denied | Check product, membership, capability and specific permission. |
404 | Route or visible record is missing | Check host, workspace and record ID; cross-tenant records are intentionally hidden. |
429 | Too many requests | Observe the stated wait time and stop automatic retries. |
When a module or button is missing
An entire module is usually controlled by product, licence or capability. Individual actions additionally depend on role, business permission, selection and record state. An administrator should test the same task with a comparable role instead of granting broad extra permissions.
Recover safely
Use password recovery only for the correct account. If an MFA method is lost, use the designated recovery or administrator path. Do not create another account to bypass an access issue; this creates separate identities and memberships.
Continue with Understanding permissions and Signing in securely.