Admin → Security uses the Shield icon and is a sensitive administrative surface. The current component stores one `security` object inside the settings JSON of only the first location row returned for the tenant; it does not select a location, update every location, or prove that login, switching, MFA, barcode, privilege comparison, or inactivity code consumes these values. Treat the page as policy configuration awaiting end-to-end enforcement verification—not as evidence that controls are active. Every selection saves immediately with no confirmation or visible saving indicator.
Step by step
- Go to Admin → Security, identified by the Shield icon, while signed in to the intended CentriPOS business. Keep a separate verified Owner recovery session and current account-recovery methods available before changing access policy.
- Wait for the loading spinner to disappear. The screen concurrently requests one location settings record and the tenant’s custom roles. It does not display fetch errors. If either request fails, defaults or an empty role table can appear without an error banner; do not save until the loaded values are independently confirmed.
- Understand the storage scope before editing. The component reads the first location row returned with `limit(1)` and no explicit ordering, then stores defaults and role overrides inside that row’s settings.security object. There is no Location selector and no tenant-level security table write. In a multi-location business, the chosen record can be ambiguous and other location rows are not updated.
- Read Default settings as the intended fallback policy represented by four stored fields. The current defaults used when no stored object is returned are Has access to log in, Don’t require a password when switching with a barcode, Username and password, and inactivity re-authentication off. A displayed default can therefore mean either a real stored choice or a fallback after missing/failed data.
- Under Log in access, Has access to log in stores `full`; Only has access to log in through user switching stores `switch_only`. Selecting either immediately submits a save. The page itself does not sign anyone out, disable an identity-provider credential, or demonstrate that the login route enforces this field.
- Under Switching user accounts, choose one intended policy: Never require a password; Don’t require a password when switching with a barcode; Require a password when switching to a user with more privileges; or Always require a password. The selection saves immediately.
- Do not infer implementation details from the switching labels. The page contains no barcode enrollment/scanner controls, privilege-ranking editor, password prompt, switching test, or session-lock behavior. Verify the actual user switcher with controlled accounts for lower, equal, and higher privilege, barcode and non-barcode entry, and failed/cancelled authentication.
- Under Authentication method, Username and password stores `password`; Username and password with multi-factor authentication stores `password_mfa`. Selecting either saves immediately. This page has no MFA factor enrollment, recovery-code, authenticator, SMS/email factor, reset, grace-period, remembered-device, or enforcement-status controls.
- Before selecting Password + MFA, confirm how every affected account enrolls and recovers through the actual Centri Account authentication system. After saving, prove enforcement with a designated non-owner account in a private browser session. A stored `password_mfa` value or success toast alone is not proof of MFA.
- Require logging in after inactivity stores a boolean immediately. The page has no inactivity duration, warning, grace period, pause-screen, exempt-workflow, or resume editor. Verify the actual timeout source and behavior across Sell, customer data, reports, customer display, and interrupted forms; never test during a terminal payment.
- Review Role specific settings only if roles loaded successfully. Each row is a tenant custom-role record sorted with system roles first, then name. The table can be absent because there are no roles or because the role query failed; confirm in Admin → Users/Roles before concluding no overrides exist.
- For a non-Owner role, Log in access can inherit Default setting, explicitly allow Has access to log in, or require User switching only. Authentication method can inherit Default setting, require Password only, or require Password + MFA. Every dropdown selection immediately saves the entire override map.
- For the exact system role whose name is `Owner`, direct Log in access is hard-coded as Has access to log in and has no selector. Owner Authentication method remains editable. This UI safeguard does not prove the owner account’s credential, MFA factor, recovery email, or break-glass process is usable.
- Choosing Default setting stores the literal override value `default` rather than removing that role’s override object. Any enforcement consumer must interpret `default` as inheritance. Verify behavior; do not assume the mere presence of an override row means it differs from the baseline.
- Change only one control at a time. Each action rereads the first location and writes its whole settings JSON with the updated security object, preserving the then-read other settings. Rapid overlapping saves have no queue or version check and can race, while another administrator can also change the row. Wait for Security settings saved, reload, and confirm before the next change.
- If no location row is returned during a save, the function ends without a success or error toast. If the location update errors, the page shows the raw error message but keeps the new local selection visible. In either case, reload and inspect stored state; never treat the selected radio/dropdown alone as persisted.
- Create a written test matrix before rollout: direct login for Owner and representative roles; `switch_only`; each password-switching policy; barcode and ordinary switching; lower/equal/higher privileges; Password only and MFA; enrolled versus unenrolled MFA; inactivity timeout/resume; logout/session revocation; offline/network failure; and recovery.
- Run tests with designated demo users in an isolated browser while the Owner recovery session remains untouched. Verify both permitted and denied paths. Check that user switching changes the effective audit identity and permissions, not just the displayed name, before customer, inventory, or financial work.
- For a multi-location tenant, inspect which location row currently holds settings.security and whether runtime enforcement reads that same row for every register. Do not copy or repair production location JSON merely to make the page look consistent without a scoped engineering/data plan and before/after verification.
- If the intended restriction is not enforced, restore only a known-good tested policy through an authorized path and escalate as a security defect. Preserve tenant, location/register, role IDs/names, stored policy values, test user, route, time, expected/actual result, and audit evidence without including passwords or MFA secrets.
- No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth Security page was both a sensitive administrative surface and remained loading during the safe inspection window, so the capture was rejected rather than shown, fabricated, or replaced.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Shield icon | Exact CentriPOS Admin navigation icon for Security. |
| Loading spinner | One location-settings query and the custom-role query are running; errors are not displayed by this component. |
| First location record | Only settings source/destination selected with limit(1) and no explicit order; no location picker or all-location update. |
| Default settings | Intended fallback values merged with the one returned settings.security object. |
| Has access to log in | Stores login_access `full`; enforcement must be tested separately. |
| Only through user switching | Stores login_access `switch_only`; it does not revoke credentials by itself. |
| Never require a password | Stored switching policy with no in-page enforcement test. |
| Barcode exception | Stored no-password-barcode policy; no barcode setup exists here. |
| Higher privilege | Stored password-higher-privilege policy; no privilege-rank editor exists here. |
| Always require a password | Stored always-password switching policy. |
| Username and password | Stores auth_method `password`. |
| Password + MFA | Stores auth_method `password_mfa`; no factor enrollment/recovery controls exist here. |
| Require logging in after inactivity | Stored boolean without a duration/editor or proven pause implementation. |
| Role specific settings | Tenant custom roles plus saved override map; the section is hidden when no roles are returned. |
| Default setting override | Literal `default` value stored in the role override object and expected to inherit baseline. |
| Owner direct login | Hard-coded non-editable Has access to log in only for a system role named exactly Owner. |
| Owner authentication | Still selectable separately in the Authentication method column. |
| Immediate save | Every radio, checkbox, and dropdown change writes without page-level Save or confirmation. |
| Security settings saved | One location row update returned success; not enforcement proof. |
| Silent no-location outcome | No location row means the save ends without success/error feedback. |
| Visible-state mismatch | A failed update can leave the newly selected local value visible until reload. |
| Race risk | Overlapping full settings-JSON writes have no version check or serialized queue. |
| No public screenshot | The approved Harbor & Hearth inspection rejected the sensitive/loading Security surface. |
Expected result
The intended policy is confirmed in the exact stored location record and then proven end to end for direct login, effective-identity switching, barcode and privilege cases, MFA enrollment/recovery, inactivity, representative roles, denied paths, and Owner recovery; immediate saves are reloaded and no first-location setting is mistaken for verified tenant-wide enforcement.
Troubleshooting
- Confirm you are changing the intended business and location before saving.
- Record the previous setting when a change affects live selling, payments, tax, or integrations.
- Use a controlled test record after saving before rolling the setting out broadly.
CentriPOS API explorer · API Center administration