Docs
The full permission reference
126 permissions across 32 modules. This page is a reference to keep open while configuring a role.
What is this page?
A reference of every permission in Pashkateb — 126 permissions across 32 modules. Keep it open while configuring a new role.
The shape of a permission
module : action
The common actions:
| Action | What it means |
|---|---|
view | Can see the screen — without it the screen does not appear at all |
add | Can create a record |
edit | Can change a record |
delete | Can remove a record |
submit | Can submit an invoice |
return | Can create a return invoice |
manage | Full management (on shop modules) |
Master data
| Module | Permissions |
|---|---|
items | add · delete · edit · view |
item_group | add · delete · edit · view |
brand | add · delete · edit · view |
warehouses | add · delete · edit · view |
warehouse_transfers | add · view |
stock_adjustment | add · delete · edit · view |
customers | add · delete · edit · view |
suppliers | add · delete · edit · view |
shipping_companies | add · delete · edit · view |
lead | add · delete · edit · view |
Transactions
| Module | Permissions |
|---|---|
sales_invoices | add · delete_draft · edit · return · submit · view |
purchase_invoices | add · delete · delete_draft · edit · return · submit · view |
delete_draft applies to drafts only. A submitted invoice cannot be deleted by any permission.
Finance
| Module | Permissions |
|---|---|
accounts | add · delete · edit · view |
journal_entries | add · edit · view |
general_ledger | add · view |
payment_entry | add · delete · edit · view |
Commerce
| Module | Permissions |
|---|---|
shop | manage · view |
shop_catalog | manage |
shop_theme | manage |
shop_domain | manage |
shop_orders | manage · view |
shop_reviews | manage · view |
shop_promotions | manage · view |
shop_analytics | view |
shop:view is the master key for reaching the commerce screens. Grant that first, then the manage permissions needed.
Reports
reports:view for general access, then one permission per report:
Inventory: stock_evaluation · stock_ledger · stock_by_warehouse · warehouse_transfer_history · low_stock_warehouse · stock_adjustment · items_need_reorder · items_prepare_production
Sales: best_selling_items · monthly_sales_summary · top_customers · most_returned_items · item_sales_period · leads_list · lead_conversion
Purchasing: monthly_purchase_summary · top_suppliers · most_purchased_items · most_purchase_returns · item_purchases_period
Financial: general_ledger · trial_balance · profit_and_loss · balance_sheet · customer_payment_ledger · supplier_payment_ledger
Logistics: orders_for_shipping
Administration
| Module | Permissions |
|---|---|
users | add · delete · edit · view |
roles | add · delete · edit · view |
companies | add · delete · edit · register · view |
integrations | add · delete · edit · view |
subscriptions | edit · view |
settings | users_view · view |
ai | use |
Practical tips
viewis always the starting point. Without it the screen does not exist for that user.submitis separate fromaddon purpose. Staff prepare drafts and someone senior submits — a common and useful arrangement.- Report permissions are individual so you can give each department only its own reports.
- Start narrow and widen. Adding a permission is easier than dealing with something done wrongly.
A technical note
Some permissions — mostly the report permissions and the warehouse ones — are checked by the interface when building the menus but are not present in the permission list seeded into the database. The consequence is that they may not appear as checkboxes in the role matrix.
If a custom role needs a permission you cannot find in the matrix, contact support — that is a platform-level configuration rather than something to fix on the Roles screen.
Frequently Asked Questions
Which permission matters most in any module?
The view permission. Without it the screen does not appear in the sidebar at all, and the other permissions are pointless. Always start with view.
Why do reports have so many permissions?
Because each report has its own. That is deliberate, so you can give your accountant the financial reports without the stock reports, or a storekeeper only the stock ones.
What does delete_draft mean?
Permission to delete draft invoices only. Submitted invoices cannot be deleted by any permission — they have already affected stock and your accounts. The only way to reverse one is a return invoice.
Why do the shop permissions not all have view?
Some shop modules have manage without a separate view, because access to the screen is controlled by the general shop:view. Grant the role shop:view first, then the manage permissions it needs.
Related Links
Use Pashkateb with Your Real Workflow
Start the free trial or move to the most relevant landing page for your workflow, then apply what you read using your own invoices, stock, and reports.