Technical access levels and business scope
The Business App's current client access check allows technical access levels 0 and 2. These values are technical identifiers, not a complete list of commercial roles, job titles, plans, or entitlements. Project, business, configuration, and server authorization still determine what an account can see and change.
Before you start
- Confirm the intended project before signing in when Project Name and Set project are shown.
- Ask your Ordering administrator which businesses should be associated with the account.
- Do not infer permission from a visible tab or button. Check the result of each server-backed action.
Technical access levels
| Technical access level | Business App entry | Source-intended data scope | What it does not prove |
|---|---|---|---|
| 0 | Allowed by the current app check. | The workspace can receive project-level order and message updates, subject to server authorization and configuration. | It does not prove permission for every order, business, account, message, or device action. |
| 2 | Allowed by the current app check. | The app retrieves the account's available businesses and uses those business identifiers to narrow incoming order updates. | It does not prove a universal “manager” role, ownership of every business, or a commercial entitlement. |
| Any other value | Not allowed by the current app check. | The current sign-in flow attempts to close the newly created session rather than entering the workspace. | It does not explain whether the account can use another Ordering product. |
How project and business scope work together
| Scope | When it is selected or resolved | What it changes | Safe operator check |
|---|---|---|---|
| Project | Before sign-in when project selection is enabled, or from fixed app configuration. | The API and configuration context used by the app. | Confirm that the expected project leads to the expected workspace. |
| Signed-in account | At authentication. | The technical level, session, and account context used for later requests. | Confirm that the profile belongs to the intended operator. |
| Available businesses | After sign-in from the server-backed business list. | Which businesses a level 2 account uses to narrow incoming order updates in the current source-intended flow. | Compare the Businesses list with the assignment expected by your administrator. |
| Task-specific authorization | When the app reads or changes an order, business, message, or account. | Whether the requested read or action is accepted, rejected, or limited. | Verify the visible result instead of assuming that workspace entry grants the action. |
What business scope changes
Business scope can affect the businesses listed in Businesses, the orders and updates relevant to the account, and whether a business-specific action is accepted. Scope is evaluated alongside the selected project and task-specific API rules.
For technical access level 2, the current source-intended flow requests the account's dashboard-mode business list. The corresponding API source limits that list to businesses linked to that account. The app then ignores incoming order updates for businesses outside the returned list when the list is available.
This is an availability boundary, not a role promise. The relationship between the pinned API source and a deployed API environment has not been established, so use the visible business list and action result as the operational check.
Variations and limits
- Project selection appears only when enabled for the app build.
- Available sign-in methods depend on project configuration.
- The Business App's 0 and 2 check occurs in the client after authentication; API routes can apply their own level, ownership, validation, and configuration checks.
- Realtime room metadata is a transport detail and does not define a public role or entitlement.
- Business assignments can change outside the app. Refresh before concluding that scope is stale.
- No source evidence in this article establishes global owner, manager, staff, kitchen, or fulfillment roles for the Business App.
Troubleshooting
| What you observe | Interpretation | Next action |
|---|---|---|
| The app closes the session after authentication. | The returned account may not have technical access level 0 or 2. | Ask the project administrator to verify the account's technical level. Do not repeatedly submit credentials. |
| The project picker is absent. | The app may use a fixed project configuration. | Confirm the expected project with the administrator before working with live orders. |
| The Businesses list is empty or incomplete. | Account-linked scope, project choice, connectivity, or server authorization may limit the result. | Confirm the project, refresh once, and ask the administrator to review business associations. |
| An order update does not appear for a level 2 account. | The order's business may be outside the business list returned for the account, or realtime data may be unavailable. | Check the business list and order queue, then escalate with the visible order and business context. |
| A visible action is rejected. | Workspace entry and action authorization are separate. | Keep the current record unchanged and follow the relevant action guide's recovery path. |
Related articles
:::note Visual status Visual guidance is deferred pending an authorized synthetic capture program with an exact asset allowlist and independent visual QA. This reference remains complete without images. :::