Send Planner permissions
The Send Planner has three permissions of its own: View, Edit and Draft. You grant them on a role, under Send Planner. Creating shipment drafts, allocating stock and drafting purchase orders also act on other screens, so they need those screens' permissions too. This page lists what each one allows. Admins have every permission. To change a role, see Create a role.
Send Planner's own permissions
| Permission | Lets a user |
|---|---|
| Send Planner → View | Open Inventory → Send Planner and every tab: working plans, scenarios, send runs, history, network rules, and the drafts made from a plan. Compare scenarios, open Why these numbers, and export a plan. Read-only. Without it, the Send Planner isn't in the menu. |
| Send Planner → Edit | Calculate, recalculate and Plan anyway; create, promote, archive and unarchive plans and scenarios; change send quantities, add reasons, reset, rebalance and use marketplace suggestions; apply tuning; refresh network data; start, recalculate and discard send runs, resolve their exceptions, approve networks and schedule runs; change network rules, lanes, sources, capacity limits, product overrides, transfer destinations and planner settings; and add a shortfall to the production schedule with Plan production (which also needs MRP Planning → Run). Doesn't create drafts or allocate stock. |
| Send Planner → Draft | Create shipment drafts from a plan and retry them, allocate and release source stock, enter manual sends, draft supplier purchase orders, approve the plan in Review AI plan, and turn on automatic drafting for send runs. Each of these also needs the screen's own permission; see below. Nothing is ever submitted to a marketplace. |
Edit and Draft do nothing without View. The role editor warns "These permissions have no effect without View" when you pick one without it.
Permissions the planner's actions also need
The planner hands work to other screens, so a role can't do through the planner what it can't do on those screens directly.
| To… | You also need | Message when it's missing |
|---|---|---|
| Create FBA, AWD, WFS or FBT shipment drafts | Integrations → Edit, the same permission the network's own inbound screens need | Creating marketplace drafts also needs the "Integrations → Edit" permission |
| Create warehouse transfer drafts to your own warehouses or 3PLs | Warehouse Transfers → Create. Transfer drafts don't need Integrations → Edit. | Creating warehouse transfer drafts also needs the "Warehouse Transfers → Create" permission |
| Allocate source stock, from the selection bar or while drafting | Warehouse Transfers → Create, because it sets stock aside in your warehouses | Allocating stock also needs the "Warehouse Transfers → Create" permission |
| Turn a manual send into a warehouse transfer | Warehouse Transfers → Create | You need the "Warehouse Transfers → Create" permission |
| Draft supplier purchase orders | Purchase Orders → Create | Creating purchase orders also needs the "Purchase Orders → Create" permission |
| Add demand to the production schedule from Why these numbers or a send run's shortfall card | Send Planner → Edit and MRP Planning → Run | Adding demand to the production schedule needs the "MRP Planning → Run" permission (or names both, when both are missing) |
When only the allocation permission is missing, the Draft shipments dialog turns its allocate checkbox off and greys it out, and the drafts are created without allocating stock. Allocate stock in the selection bar is greyed out too. In Review AI plan, you can turn supplier orders off to approve the rest without Purchase Orders → Create.
For how allocations work, see Allocate stock for a send.
What a user without a permission sees
The planner greys out an action you can't take, and the tooltip says why. The one exception is Create PO on a short SKU, which isn't shown at all without Purchase Orders → Create. The tooltips name the other screens' permissions the way the role editor does, such as Integrations → Edit, Warehouse Transfers → Create and Purchase Orders → Create.
| Missing | What you see |
|---|---|
| Edit | Calculate plan, Recalculate, Plan anyway, Save as scenario, archive buttons and the send boxes are greyed out with "You need the Send Planner edit permission". Network rules says "These rules are read-only for you. Changing them needs the Send Planner edit permission." Send runs says "You can review send runs, but changing a run's rules, resolving exceptions or scheduling runs needs the Send Planner edit permission." The grid's When stock is short toggle is greyed out. |
| Draft | Draft shipments, Allocate stock, Release allocations, Review AI plan and supplier PO buttons are greyed out with "You need the Send Planner draft permission". Turning on Auto-create drafts for SKUs with no exceptions in a send run's schedule says "Turning on automatic drafting needs the Send Planner draft permission." While that setting is saved on, the buttons that start or recalculate a send run are greyed out too, because the run drafts as soon as it finishes. |
Default grants
When the Send Planner was added, existing roles were granted its permissions once, based on what they could already do with warehouse transfers:
| Roles that could… | Were granted |
|---|---|
| View warehouse transfers (Warehouse Transfers → List) | Send Planner → View |
| Create warehouse transfers (Warehouse Transfers → Create) | Send Planner → Edit and Send Planner → Draft |
After that, you manage them like any other permission.
API scopes
Personal access tokens and connected apps reach the Send Planner through two scopes, listed under Send Planner when you create a token:
| Scope | Description on screen |
|---|---|
send-plans:read | View send plans, scenarios, network rules and draft results |
send-plans:write | Calculate plans and scenarios, override lines, change network rules, allocate stock, create inbound drafts in each network and draft supplier purchase orders shipped direct to a network |
A token's scope limits what it can reach, and the user's own role still applies on every call: a token with send-plans:write can only draft if its user has Send Planner → Draft plus the extra permissions listed earlier. A read-only token can't edit or draft. Drafting through the API goes through the planner itself, so a token doesn't need the scopes of each network's inbound screens.
The Send runs tab has a For developers and AI agents panel with the calls behind a send run. For endpoint details, see the developer documentation. See also Create a personal access token, the API scopes reference, and Connect an AI assistant.
Rebalance through the API
An AI agent or an integration with the send-plans:write scope can rebalance many SKUs around their edits in one request. Up to 200 SKUs rebalance straight away. A larger request runs in the background and shows in the job tray as Send Plan Rebalance; the Plan tab reloads its totals and rows when it finishes. A single request can't cover more than 50,000 SKUs. On screen, the rebalance icon works one SKU at a time; see Change a send quantity.