ZenotiHelp

Granular AI Inventory Permissions with Price Visibility Control

ZTZenoti Docs Team Updated October 17, 2026 10 min readGuide

AI Inventory Manager uses four distinct permission actions to control which staff members can access the module and what information they see. This article explains how to configure those permissions and what each one controls, including a price-masking setting that prevents certain staff from viewing monetary values anywhere in AI Inventory.

Note: For conceptual background on AI Inventory Manager, see AI Inventory Manager Overview.


On this page


Before you begin

  • You must have access to your organization's security role configuration in Zenoti.

  • Identify which staff roles need access to AI Inventory and which roles should have prices hidden.

  • Confirm that AI Inventory Manager has been activated for your organization. See Licensing & activation.

  • You need the following permissions to configure security roles:

    Permission: Access to the Security Role configuration screen β€” required to assign or remove AI Inventory permission actions for any role.


Steps

Understand the four permission actions

AI Inventory Manager resolves access using four permission actions. Each controls a distinct capability. Assign only the actions that match each role's responsibilities.

The following table describes each permission action and what it gates.

Permission action Security object What it controls
View Dashboard AI_Inventory Grants access to the AI Inventory dashboard, including the Inventory Dashboard and all tabs within it. Without this action, the user sees an access-denied state instead of the dashboard.
Onboarding AI_Inventory Allows the user to run or re-run the four-step setup wizard. Without this action, the onboarding wizard is inaccessible.
Settings Edit AI_Inventory Allows the user to view and modify organization defaults, center overrides, and product overrides in the settings screens. Without this action, settings are read-only or hidden.
Raise Order Inventory Allows the user to create and send bulk purchase orders from the action grid. Without this action, the order creation flow is unavailable.

Important: All four permission actions are fail-closed. If Zenoti cannot resolve a user's permissions β€” due to a network error, service timeout, or any other failure β€” every action defaults to denied. The user sees an access-denied state rather than an indefinitely loading screen. No access is granted until permissions are confirmed.

Note: Permission state is resolved once at session start and cached for the duration of the session. Once a user signs in, Zenoti does not re-check permissions on every page load β€” the resolved access flags are read from the session cache. Changes to a role's permissions take effect the next time the affected user signs in.


Configure access permissions for a role

  1. In Zenoti, navigate to the security role configuration screen for your organization.
  2. Select the role you want to configure.
  3. Locate the AI_Inventory security object.
  4. Grant or remove the following actions based on what members of this role should be able to do:
    • View Dashboard β€” grant to any role that needs to view the AI Inventory dashboard.
    • Onboarding β€” grant only to administrators or senior managers who will run the initial setup wizard.
    • Settings Edit β€” grant only to roles authorized to change reorder coverage defaults, lead time settings, or center and product overrides.
  5. Locate the Inventory security object.
  6. Grant or remove the following action:
    • Raise Order β€” grant to roles authorized to create and send purchase orders from AI Inventory.
  7. Save the role configuration.

Important: Changes to security roles take effect the next time affected users sign in. Ask users to sign out and sign back in after you update their role.


Configure price visibility using the Hide Price permission

The Hide Price permission controls whether a user sees monetary values in AI Inventory. When this permission is granted to a role, all prices and monetary totals are masked for every user in that role. Masking applies across the entire module.

The following locations all display masked values when Hide Price is active for a user:

  • Line-item prices in the action grid (Vendor price, Value to order, Line total)
  • KPI tile values on the Inventory Dashboard tab (including Net inventory value, Retail profitability, and Turnover ratio)
  • Vendor pricing shown in the vendor scorecard

Masked values are replaced with a placeholder indicator rather than a number.

Important: Price masking is fail-safe. If Zenoti cannot determine whether a user has the Hide Price permission β€” due to a timeout, error, or absence of an explicit grant β€” the system defaults to masking prices rather than displaying them. Prices are never shown to a user whose permission state is ambiguous or unresolvable.

To configure price visibility:

  1. Navigate to the security role configuration screen.
  2. Select the role whose price visibility you want to control.
  3. Locate the Inventory security object.
  4. To hide prices from this role, grant the Hide Price action.
  5. To allow this role to see prices, ensure the Hide Price action is not granted.
  6. Save the role configuration.

Tip: Use Hide Price for roles such as front-desk staff or junior employees who need to view stock status and suggested quantities but should not see vendor costs or inventory value totals.


Understand the training-progress display during Analyzing

When a center first registers with AI Inventory Manager, the module enters an Analyzing state while the initial model training cycle runs. During this period, the dashboard displays a progress indicator to communicate status to users.

The progress indicator shows:

  • Elapsed time and estimated time remaining β€” displayed as a human-readable label such as "~2h 30m remaining"
  • A "started at" timestamp β€” displayed as a human-readable date and time such as "Jul 14, 2026, 9:00 AM"
  • A current stage indicator β€” advances through four sequential stages based on elapsed time

The four stages and their approximate timing are:

Stage Elapsed time from registration
Stage 1 0 – 90 minutes
Stage 2 90 minutes – 3 hours
Stage 3 3 – 4.5 hours
Stage 4 4.5 hours and beyond

Important: The stage indicator is cosmetic. Stage advancement is based on elapsed time and does not reflect the actual completion state of the underlying model-training pipeline. The training cycle may complete earlier or later than the cosmetic window suggests.

The cosmetic progress window spans approximately 6 hours from the center's registration date. If the 6-hour window expires and the model has not yet finished, the Analyzing state and progress indicator continue to display β€” the dashboard does not automatically advance to a ready state. The system transitions out of Analyzing only when the server-side readiness probe returns a Ready status. No elapsed-time threshold alone determines readiness.

This means a user may see Stage 4 with "~0m remaining" displayed, and the dashboard will still show Analyzing until the server confirms that predictions are available. In that situation, no action is required from the user β€” the system will update automatically once the model is ready.

Note: During the Analyzing state, the prediction panes beneath the status banner are visually muted and non-interactive. This is expected behavior. Once the server returns a Ready status, the dashboard updates and predictions become available without requiring a manual refresh.


Verify the configuration

After saving role changes, ask a test user in the affected role to sign in and confirm the following:

  1. If View Dashboard was granted β€” the user can open the Inventory Dashboard tab without seeing an access-denied message.
  2. If Onboarding was granted β€” the setup wizard is accessible.
  3. If Settings Edit was granted β€” the user can view and modify the Organization defaults, Center overrides, and Product overrides sections in settings.
  4. If Raise Order was granted β€” the user can initiate a purchase order from the action grid.
  5. If Hide Price was granted β€” the user sees masked placeholders in place of monetary values throughout AI Inventory, including Vendor price, Value to order, Line total, and KPI tile values.
  6. If Hide Price was not granted β€” the user sees actual monetary values in those locations.

Note: If a permission change does not appear to take effect, confirm that the user has signed out and signed back in after the role was saved.


Worked example

Scenario: A regional manager at a medspa organization needs full access to AI Inventory but without price visibility, while a procurement specialist needs to raise orders and see prices but should not be able to change settings.

Regional manager role configuration:

Permission action Security object Grant?
View Dashboard AI_Inventory Yes
Onboarding AI_Inventory No
Settings Edit AI_Inventory No
Raise Order Inventory No
Hide Price Inventory Yes

Result: The regional manager sees the dashboard and all stock status, confidence tiers, and suggested quantities β€” but every monetary value (vendor prices, Net inventory value tile, Retail profitability tile) appears masked.

Procurement specialist role configuration:

Permission action Security object Grant?
View Dashboard AI_Inventory Yes
Onboarding AI_Inventory No
Settings Edit AI_Inventory No
Raise Order Inventory Yes
Hide Price Inventory No

Result: The procurement specialist can view the dashboard, see all monetary values, and create bulk purchase orders β€” but cannot access settings or the onboarding wizard.


Tips

  • Assign Onboarding and Settings Edit only to owners or senior managers. Changes to reorder coverage, lead time, and safety days affect the suggested quantities the entire team acts on, and those changes do not take effect until the next nightly refresh.
  • When you create a new role for AI Inventory, start with View Dashboard only, verify the experience, and then add further actions incrementally. This prevents accidentally over-permissioning a role.
  • Use Hide Price proactively for any role where price information is not operationally necessary. Because price masking defaults to hidden on any permission-resolution failure, granting this permission explicitly produces the same result as an ambiguous state β€” but making it explicit keeps your role configuration intentional and auditable.
  • Review role configurations any time you onboard a new center or change organizational structure. The Raise Order action on the Inventory security object is shared with the broader inventory module, so verify that granting it for AI Inventory purposes does not unintentionally expand access to other inventory screens.
  • Remember that permission state is cached per session. Always ask users to sign out and sign back in after a role change, especially during initial setup or troubleshooting.
  • During the initial Analyzing period after center registration, inform staff that the progress stages shown are approximate and that the dashboard will update automatically once the model is ready β€” no manual action or page refresh is needed.

Troubleshooting

A user has been granted View Dashboard but still sees an access-denied screen.

Ask the user to sign out and sign back in. Permission state is resolved and cached at sign-in; changes do not apply to an active session. If the issue persists after a fresh sign-in, verify that the role configuration was saved correctly and that the user is assigned to the correct role.

A user with Hide Price granted can still see prices.

Confirm that the role was saved after the Hide Price action was granted, and that the user has signed in after the save. If the role shows Hide Price as granted and the user has signed in fresh but prices are still visible, escalate to your Zenoti administrator to verify that the permission resolved correctly at the session level.

A user cannot access the settings screens even though Settings Edit appears granted.

Verify that View Dashboard is also granted for that role. Settings access within AI Inventory requires dashboard access as a prerequisite. Grant View Dashboard and ask the user to sign in again.

A user's prices are masked even though Hide Price is not granted on their role.

This is the expected fail-safe behavior when permission resolution encounters an error or timeout at sign-in. The system defaults to masking prices in the absence of a confirmed, explicit permission state. If the user's session consistently masks prices despite Hide Price not being granted, there may be a connectivity issue affecting permission resolution. Ask the user to sign out, confirm network connectivity, and sign back in.

The Raise Order action appears granted but the user cannot create a purchase order.

The Raise Order action sits on the Inventory security object, not the AI_Inventory object. Verify that the action was granted on the correct security object. Also confirm that View Dashboard is granted β€” without dashboard access, the action grid where orders are created is not reachable.

The dashboard shows Analyzing with "~0m remaining" but never advances to Ready.

This is expected. The stage indicator and time-remaining label are cosmetic and based on elapsed time from registration. The dashboard transitions to Ready only when the server-side readiness probe confirms that predictions are available. No user action can accelerate this. If the Analyzing state persists significantly beyond 6 hours, contact your Zenoti administrator to verify that the center's registration completed successfully.


Was this article helpful?
Your feedback helps us improve our documentation.