Help and reference · 1 MIN READ
Know what is available in your workspace
Understand why a catalogue, interface and deployed feature can differ.
Guide reviewed 14 September 2026 · Controls depend on your app version and access.
Before you begin
Feature access depends on more than the name of your plan.
01Check entitlement and access
Ask whether the plan includes the feature and whether your role permits the action. Device permissions are a separate requirement.
02Check the actual deployment
A screen, API adapter or draft action is not proof that every service is enabled and configured. Confirm the available workflow in your own environment.
03Treat development products as development
RetailPort and Satchel are described as in development. X-Ray is catalogue-restricted and has no verified end-user implementation in the inspected sources. The delivery preview is not a production fulfilment tutorial.
04Ask about additional capabilities explicitly
Knowledge, AutoSync, integrations, enterprise communications and other plan-listed features need deployment-specific setup and documentation. Do not invent a setup procedure from a marketing name. Ask for the supported entry point, provider, permissions, data handling and a verified example.
Check the result
You can distinguish a plan entitlement, a configured feature and a proposed or preview capability.
If something does not look right
If a guide differs from your screen, keep the app version, organisation and missing control in your support request. Do not bypass a missing feature with unapproved tools.
Look up an error