User Permission Setup

What a customer should see inside the portal

For a B2B portal, the customer view should feel clean and limited to their own business. Corporate buyers often want to reorder branded stationery, update branch details or approve a proof without seeing internal pricing rules for other accounts. They should not see another client’s artwork, team notes or stock movement.

A Durban corporate office may have one approver, two requesters and a finance contact. Each person needs different access. One user can submit a request, another can approve artwork and a third can check order history. That split keeps the account organised and avoids messages being forwarded around with outdated notes or old proofs attached.

• Hide price margins where the customer does not need them
• Allow reordering from approved product templates
• Keep proofs tied to the correct job number
• Show delivery status and collection details only for that account
• Limit account edits to named approvers or admins

Staff permissions that protect pricing and proofing

Inside the shop, user roles should follow the workflow. A pricing assistant may need to build matrices for size, stock and quantity bands, but not change payment rules. A proofing coordinator may send artwork back for correction, yet not alter the product template or discount structure. This split matters when a shop handles business cards, labels, folders and short-run packaging from the same storefront.

One practical rule is to separate commercial control from production control. If the same login can edit prices, approve artwork and close a job, there is no clear trail when something goes wrong. It becomes harder to see who changed what, and harder still to correct it without upsetting the rest of the workflow.

For teams in Johannesburg, Pretoria or Bloemfontein, where branches may share one system, permissions also help with accountability. A branch user can work in their own lane while head office keeps oversight over product setup and financial settings. That keeps each branch useful without turning the platform into a free-for-all.

Artwork rules and preflight checks need their own gates

Artwork handling is one of the places where user permission setup earns its keep. Preflight checks can flag missing bleed, low-resolution images, incorrect colour spaces or oversized files before a job lands in production. Staff need enough access to see those warnings and fix them, but not enough to bypass the rules when a deadline feels urgent.

A useful setup lets the system separate upload, review and approval. The customer uploads a file, a proofing user checks it, and an approver signs off only when the artwork is ready. If a production operator also needs to view the file, they should see the approved version and the notes that matter to print, not the full chain of customer comments.

• Upload rights can be limited to named users or all account holders
• Proofing rights can sit with an internal team member or customer approver
• Approval rights can be restricted to senior staff or finance sign-off users
• Preflight warnings should remain visible to the people fixing the file
• Rejection notes should stay attached to the job for traceability

Payments, delivery and order tracking also need limits

Permissions do not stop at artwork. Payment and delivery settings need proper control too. Some accounts should be able to place an order on account, others must pay before production starts. Courier choices, collection points and delivery addresses may also differ from one customer to the next, especially for chain stores with several branches across South Africa.

Order tracking should show enough to be useful without exposing more than needed. A buyer can see that a job is in proofing, print, finishing or dispatch. An internal user can add notes, reroute a job or update the delivery method. A customer should not be able to change a production step once it has already been approved. That saves a lot of friction when a job is on press and everyone is watching the clock.

A Durbanville setup example for a multi-branch print shop

Picture a print shop in Durbanville serving clients in Cape Town, Stellenbosch and Paarl, plus a few corporate accounts in Gauteng. The owner wants the sales team to quote, the artwork team to proof files and the admin team to handle payments. The branches must share templates, but each branch also needs its own order queue and delivery rules.

In that setup, the cleanest approach is to assign roles by task and account type. Head office users manage templates, matrices and top-level settings. Branch staff handle local orders and customer follow-up. Corporate clients log into a restricted portal with their own approved products, their own user list and their own purchase rules. It sounds tidy because it is tidy, and tidy systems are easier to run when the phones are busy and the order list keeps growing.

Setting permissions without making the system awkward

Good permission setup should feel almost invisible to the people using it. Staff should not need to ask for a manager every time they open a file or check a status. At the same time, no one should have broad access just because it is easier to switch it on. The right balance comes from listing the real tasks first, then assigning access around those tasks.

For most print shops, the best starting point is a small number of clear roles, followed by specific exceptions for senior staff. That keeps training easier, reduces confusion and gives the business room to grow as more products and branch users are added. In practice, the strongest setup is the one people can understand on a busy Monday without needing a long explanation.