Do not share passwords, paste invitation/reset tokens into support, weaken MFA or switching policy as a shortcut, or assign Owner broadly. Also do not assume the location/register picker itself proves row-level authorization: the current selectors list active records for the chosen tenant, while downstream screens can apply separate user-location and restricted-register scopes.
Step by step
- Start at the branded /login screen and confirm the exact invited email. The current flow uses Email and Password only. If Login failed appears, distinguish a bad credential from Signed in as a different account, which means CentriPOS rejected an authenticated identity that did not match the email requested or an active matching profile.
- If the password is unknown, choose Forgot password?, submit the existing account email once, and use the newest branded recovery message. Password recovery changes an existing credential only; it cannot activate a profile, add a business membership, assign a role, or grant a location/register permission.
- After authentication, examine the business step. A user with one active profile enters that tenant directly. Multiple active profiles produce Choose your business. If the intended business is absent, an authorized administrator must verify that the invited identity is linked to an active profile in that tenant; searching cannot reveal an inactive or nonexistent membership.
- On Choose a location, No locations configured yet means the selector returned no active location rows for the active tenant. A missing location can therefore indicate an inactive/missing record or wrong business. The current selector itself does not filter its location query through user_locations, so seeing a location card is not proof that every downstream report or action will include that location.
- On Choose a register, only active registers belonging to the selected location are listed. Exactly one is auto-selected. The current selector itself does not exclude restricted registers through user_registers; downstream queries can separately exclude restricted registers for unassigned non-owner users. Treat selector visibility and operational authorization as different checks.
- Open User Hub to confirm the effective name, email, and role label, then confirm the active business/location/register separately in the operating-context bar because User Hub does not print the business name. Use Sign out / switch user for the wrong identity, Switch store for another membership, and Switch for another location/register.
- For missing navigation or a disabled action, compare the effective user’s roles and explicit permissions inside the active tenant. Admin requires Owner, Super Admin, or settings.manage (Manage settings). Other screen and action permissions are independent; granting Admin access does not automatically grant every receipt, sale, contact export, financial, or register action.
- For scoped data discrepancies, compare the page’s query rules with user_locations and restricted register assignments. The shared location-scope hook gives Owners/Super Admins all locations; for other users, assigned location IDs are used when present. With no assignments, many callers treat the user as unrestricted unless that screen requests strict assignment. Restricted registers are excluded downstream only when marked restricted and the user lacks a user_registers assignment.
- Review Admin → Security only with an authorized Owner, Super Admin, or Manage settings role. Defaults include Log in access, switching policy, authentication method, and inactivity re-authentication. Role-specific login and authentication overrides supersede defaults; the system Owner role always reports Has access to log in. Changes save immediately to the security settings stored on a tenant location record.
- If a role is set to Only has access to log in through user switching, do not treat failed direct login as a forgotten-password problem. If Password + MFA or inactivity re-authentication is configured, follow that policy rather than disabling it to test. Retain an authorized owner recovery session before changing security settings.
- If the correct identity, active membership, context, role, and page-specific scope are all verified but the screen still fails, capture the safe page name, timestamp with time zone, business/location/register names, exact message, device/browser, and smallest repeatable steps. Never include a password, OTP, invitation token, reset URL, session token, API credential, or customer/payment screenshot.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Authentication | Email-and-password proof of identity on the branded CentriPOS login screen. |
| Signed in as a different account | Protective sign-out when the authenticated identity differs from the requested account and no active matching profile exists. |
| Active profile | Tenant-specific CentriPOS membership row connecting one authenticated user to one business. |
| Single active profile | Enters that business directly without showing the business picker. |
| Choose your business | Multiple-membership selector containing the account’s active tenant options. |
| Choose a location | Active tenant-location selector; card visibility is not proof of every downstream location scope. |
| No locations configured yet | No active tenant locations were returned to the selector. |
| Choose a register | Active registers for the selected location; one active register is auto-selected. |
| Restricted register | Register marked is_restricted; downstream scope can exclude it when the effective user lacks a user_registers assignment. |
| user_locations | Assignments used by scoped page queries for non-owner users, not by the current location selector itself. |
| No location assignments | Many shared-scope callers interpret this as all locations unless they explicitly request strictAssigned behavior. |
| Effective user | Proxy identity when supported proxy mode is active; otherwise the signed-in account identity. |
| Operating-context bar | Separate confirmation of the active business, location, register, and session state. |
| Storefront role | Baseline tenant role used in navigation and permission evaluation. |
| Explicit permission | Named capability such as settings.manage or a page/action-specific sale, receipt, contact, financial, or register permission. |
| Admin access required | Admin is limited to Owner, Super Admin, or a custom role with Manage settings. |
| Security defaults | Login access, switching policy, authentication method, and inactivity re-authentication applied unless a role override exists. |
| Role override | Per-role login-access or authentication-method choice that supersedes the default. |
| User switching only | Role can enter only through the configured in-app switching flow, not normal direct login. |
| Password + MFA | Configured authentication method requiring the business’s supported second-factor flow. |
| Support evidence | Safe screen/context/time/error/device details only; never secrets or private customer/payment data. |
| No public screenshot | Security and user-access screens are sensitive, and the approved Harbor & Hearth manifest explicitly rejected them; this article intentionally has no fabricated replacement. |
Expected result
The user signs in with the invited identity and sees exactly the businesses, locations, registers, and navigation allowed by the current role.
Troubleshooting
- Capture the exact screen, time, expected result, and smallest repeatable steps.
- Remove unnecessary customer and payment information from screenshots.
- Include only safe receipt, order, or record references when contacting support.
CentriPOS API explorer · API Center administration