1How to use it #
- Pick a User to see everything currently allocated to them. Refresh (F2) re-reads the list.
- Allocate Items (F3) opens the picker: tick items on the left (search first, then Select all covers every match), choose one or more users, and apply — the same set goes to every chosen user.
- To take items away, tick their rows here and press Remove Selected (F5) . Removing an allocation never touches the item itself.
- Allocating an item a user already has is harmless — it is skipped rather than duplicated.
2Step by step #
Restricts product visibility per user — a counter operator can be limited to the lines they sell.
- Pick the User * to restrict.
- Allocate the products (or ranges) they may see and save with F5 .
- From their next load, product pickers show that user only the allocated products. Remove all rows to lift the restriction.
3When does it actually restrict? #
- Only when the company preference User can use shared products only is switched on. Until then allocations are recorded but nothing is hidden.
- With it on, every item pick-list the user meets — voucher entry, scheme item lists, item pickers — is narrowed to their allocated items, on top of the usual branch-visibility rules.
- A user with no allocations at all will see an empty item list once the preference is on, so allocate before switching it on.
- This page itself always lists every branch-shared item when allocating, so an administrator can hand out items they don't personally hold.
4Rules & integrity #
- One row per item-and-user pair — the database enforces it, so double allocation is impossible.
- Deleting an item or a user clears its allocations automatically (cascade).
- The page needs the UserProductAllocation tools permission; without it the page opens read-only with a notice and loads nothing.
- The database also checks permission on every insert and delete, so a denied user cannot get through by another route.
5Why is a pick-list empty? #
- User — the list holds the users of this company (template users excluded). If it is empty, add the user to this company first.
- Items — the allocate picker shows active items shared with your branch; an item hidden from your branch will not appear.
6If something does not work #
"Requested action denied due to security restrictions (Tools->UserProductAllocation). Contact Administrator !"
- Why
- Deciding who may see which products is a tools permission of its own.
- What to do
- An administrator grants it.
"Pick the user whose allocations are being removed." / "Pick a customer group first."
- Why
- An allocation is always for somebody, or for a group.
- What to do
- Pick one, then apply.
"The same customer is both added and removed in one save. Nothing was changed." / "The same product is both published and unpublished in one save. Nothing was changed."
- Why
- The save contradicted itself, so it was refused whole rather than guessed at.
- What to do
- Decide which you meant and save again.
"Published every item matching the filters (...)." / "Removed every item matching the filters (...)."
- Why
- Not errors - the count says how many the filters actually touched.
- What to do
- Check the count matches what you intended.
A user still sees a product you removed
- Why
- Allocation is read when their screen loads.
- What to do
- Ask them to press F5, or to sign in again.
This is the help InvoiceNET® ERP shows beside the Product Allocation to Users screen. Whether you have the screen depends on the modules of your licence and the rights your administrator has given you.
See this screen for yourself
The demo is the real product, with a company of your own.