Permissions & Scopes

One scope per capability

Every capability c in Panoptes has a scope cap:c — for example cap:create_sale, cap:manage_inventory_items, cap:view_reports. A key calls a console action when it holds a cap: scope for a capability that action's gate accepts.

Module	Example capabilities
pos	create_sale, update_order_status, cancel_order, void_line, refund_order, manage_tables
catalog	edit_price, edit_recipe, manage_promotion, manage_brands
inventory	manage_inventory_items, enter_count, approve_variance, manage_transfers
production	create_batch, close_batch, record_waste
purchasing	manage_suppliers, create_purchase_order, receive_purchase, register_supplier_payment
delivery	settle_delivery_account, manage_delivery_policy
cash	enter_reconciliation, manage_vault
accounting	view_gl, manage_accounting, manage_periods
reports	view_reports, view_profit, view_hq
audit	view_audit, resolve_fraud
hr	view_hr, manage_employees, manage_attendance, manage_payroll
admin	manage_users, manage_settings, manage_org

Each endpoint in the API Reference lists the credentials it accepts.

Presets

Presets make a large grant easy to pick. They are expanded at mint time and never stored, so a preset that grows later cannot widen an existing key.

• preset:full — every capability the owner holds. As powerful as the owner; use sparingly.
• preset:read_only — the read capabilities.
• preset:<module> — one per module: preset:pos, preset:inventory, preset:hr, …

Legacy scopes

The original seven scopes stay valid as aliases, each mapping to one capability: read:reports, write:sales, write:inventory, write:suppliers, write:purchases, write:catalog, manage:webhooks.

Refusals

Status	Meaning
401	Missing, malformed or revoked credential
403	The key's scopes or the owner's role do not permit the action, or the plan does not include the module