dodil/erp-brick-product

tests/scenarios/roles.yaml

# The scenarios' role catalogue: the brick's default roles (src/brick_product/roles.yaml — tests/test_scenarios.py keeps
# them equal) plus the one role the neighbour needs: whoever keeps the partner register, so a scenario can make the customer
# a price list is assigned to (a customer that is not in the register cannot be assigned), and a selling brick's service client
# (quote, orders, invoices, stock) which alone holds the machine permission that records a unit as used.
roles:
  catalogue_manager:
  - product:product:read
  - product:product:write
  - product:product:archive
  - product:category:write
  - product:class:write
  - product:settings:write
  planner:
  - product:product:read
  - product:site:write
  pricing_manager:
  - product:product:read
  - product:price_list:read
  - product:price_list:write
  - product:price_list:publish
  - product:customer_price_list:write
  - product:settings:write
  owner:
  - product:product:read
  - product:price_list:read
  - product:settings:controls
  sales_rep:
  - product:product:read
  - product:price_list:read
  system:
  - product:product:read
  - product:price_list:read
  - product:catalogue:import
  - product:product:suggest
  - product:price_list:check
  - product:migration:read
  - product:unit:mark_used
  partner_steward:
  - bp:partner:write
  selling_service:
  - product:product:read
  - product:price_list:read
  - product:unit:mark_used
  - product:migration:read
service_clients:
- system
- selling_service