Skip to main content

​
How the app is organized

The left sidebar groups the product into sections:
  • Apps — Tasks, AI Agent, Analytics (master-data cards & dashboards), Signals (alerts), Activity.
  • Inventory plans — restock, rebalance, markdown, pre-season, supplier return/exchange, and the approvals queue.
  • Orchestration — Workflows.
  • Intelligence layer — business rules & rulesets, budgets, size curves, markdown calendars, supplier constraints, approval/return policies, and more.
  • Data platform — data sources, ingestion specs, datasets explorer, tags, taxonomy.
  • Settings — users, teams, roles, organization, API tokens, navigation templates, preferences.

​
Configurable navigation (per organization)

The sidebar is template-driven. Rather than a fixed menu, each organization uses a navigation template that decides which items appear — and in what order — for each role. Administrators can:
  • Show, hide, and reorder menu items per role (admin vs user).
  • Rename sections and submenus.
  • Create multiple templates (e.g. Buyer, Merchandiser, Operations).
On login, the sidebar renders from your organization’s template for your role, so two users in the same org can see different menus.
Navigation templates are managed under Settings → Navigation templates (admin).

​
Roles & permissions

Access is governed by permissions grouped into roles. A user’s role determines which sections they can open and which actions they can take.

​
Roles

RoleFocus
Org adminFull access to everything in the organization.
User managerManage users, teams, and roles.
Data platform adminConfigure data sources, ingestion, sandbox; view analytics.
Intelligence layer adminConfigure rules, budgets, policies; view analytics & signals.
Inventory managerManage all inventory plans; view analytics & signals.
Shop managerView plans for assigned shops; view analytics & signals.
Shop viewerRead-only on assigned shops + analytics.
AnalystAnalytics & signals across all shops.
Plan approverDecide on plan approval requests.

​
Permission domains

Permissions are fine-grained and grouped by domain — for example inventoryPlans.view, inventoryPlans.manage, inventoryPlans.approvalsDecide, dataPlatform.configure, intelligenceLayer.configure, signals.manage, analytics.view, org.settings.edit, users.view. Shop visibility is controlled by shops.viewAll vs shops.viewAssigned.
The same permission model governs the API: a service-account token carries a set of these permissions and can only do what they allow.