Inviting your team: starting roles for sales, operations, and admin

It is a new hire's second day. She opens a quote at the back-office desk, and the screen shows more commercial detail than her job requires. That is the moment to ask what access the role should have. On OrderPilot's POS register, vendor costs are never sent to the screen; at the Admin desk, cost visibility is a deliberate permission decision.

Start with OrderPilot's Salesperson, Operations, and Store administrator roles, then review the actual permissions against your store's jobs. The starter names are useful starting points, not a finished policy. Before the first real quote, have each person try the work they should be able to do and a representative action that should be restricted.

Read the starter permissions before assigning people

The starter roles are broad working arrangements. In particular, “Salesperson” does not automatically mean a tightly restricted trainee account.

Use a restricted non-administrator role for someone who needs narrower access. Store administrator is intended for full authority, so giving it a gentler name is not a way to make it a limited role. Keep that distinction clear when a trusted employee takes on an occasional administrative task.

This review belongs early in the first-week setup plan. It is easier to explain access as part of the job from the beginning than to remove an unexplained privilege after staff have built a habit around it.

Decide separately who sees cost and who changes price

Cost visibility and selling authority answer different questions. Someone can know a vendor cost without being authorized to reduce a customer's price, or be allowed a defined selling action without needing access to purchasing figures.

In the role editor, review cost visibility, price overrides, discounts, and payment terms as distinct responsibilities. The store's cost-visibility policy should explain why a person needs the information, while the discount authority matrix explains who can make the commercial decision. For an illustrative arrangement, a sales associate prepares quotes and requests customer payments, while a manager approves a discretionary discount and handles refunds. That is a policy example to implement and test, not a description of the starter Salesperson role. Remove or adjust broad starter rights where the store wants that separation.

Permissions are not a substitute for an agreed discount rule. If the store allows a specific exception, staff still need to know when it applies and what reason to record. Otherwise, a perfectly configured permission merely makes an unclear decision easier to execute.

Give cover staff the records they need

Covering a colleague's day off should not require giving someone every record in the business. Review the role's viewing and changing scope alongside the locations assigned to the person.

Start with a concrete handoff. A customer calls about a quote owned by an absent associate at the downtown showroom. Decide whether the covering person should see it, edit it, send a message, or only pass the question to a manager. Those are separate parts of the job, not a single vague “cover” permission. Use the available record and location scope to give the covering person the intended reach, then test the actual colleague's sample record. Also try a record from a location they should not access. If the chosen scope is too broad for the intended arrangement, use a narrower assignment or a designated covering manager rather than opening the whole store by default.

Keep record assignment separate from sales credit. The person answering today's question may not be the person credited for the sale. Changing who handles the next action should not quietly settle a commission discussion.

Name the people who can make exceptions

Exception permissions deserve their own review because they let staff act when the normal requirements are not met. Include placing an order despite a requirement, converting without the expected signature, warranty exceptions, and changes to sales attribution. Give each exception a named responsible person and a backup. The backup matters when a customer is ready to proceed and the usual manager is visiting a vendor. An escalation path that ends at an unavailable phone is not much of a process.

Ask what evidence the approver needs. A missing signature may be a genuinely unsigned agreement or a signed paper copy waiting to be recorded. Those situations deserve different actions. The exception holder should resolve the real condition and leave a traceable explanation, rather than simply clearing whatever stops the screen.

Treat changes to sales attribution with the same care. The store should be able to explain why credit changed, especially when several associates contributed to the sale. A shared iPad is not the ideal venue for an improvised commission summit.

Choose commission visibility by responsibility

Salespeople should receive the commission information the store intends them to review, while wider commission and profit access belongs with the people responsible for those decisions. Review the available own-commission and wider reporting permissions explicitly.

Do not infer commission access from a job title or assume every starter role has the setting you want. Open the role and inspect it. Where someone checks only their own credit, test that view. Where a manager reconciles the whole team, test the broader report and any related cost visibility.

Explain the policy to staff in the same conversation as the earning rules. Seeing a number is useful only if the person understands what event makes it earned and how refunds or corrections appear. This day-one setup needs a clear owner even if detailed commission configuration follows later.

Keep Shopify access and OrderPilot roles in step

Shopify controls access to the store, apps, and POS environment; OrderPilot controls permissions within its own work. Both layers matter. Granting an OrderPilot role does not create a Shopify login or replace the Shopify permissions needed to reach the app.

Shopify's POS staff-management documentation distinguishes staff access, location access, PINs, and login requirements. Its POS comparison places advanced staff roles and permissions within POS Pro. Review those settings for the way each person accesses the register, alongside their OrderPilot role.

For Admin staff, establish the person's Shopify account and app access, then assign or preassign the appropriate OrderPilot role. OrderPilot records staff when they visit the app and can match a preassigned role to that visit. For POS-only staff, the app supports adding a staff identity reported by POS so the owner can give that person a role.

Use the staff identity and POS PIN arrangement on shared devices. Verify the acting person before a payment or exception. The showroom iPad setup guide covers the device rehearsal, including switching people and checking the actions available to each one.

Test permitted work and blocked actions

A role is ready when the intended person can complete their job and the restricted actions are actually restricted. Test as that person, not from the owner's account with a mental picture of what ought to be hidden.

Open a sample quote and inspect the visible information. Try a permitted edit, find a record in scope, and attempt an action outside the role's authority. A restricted control may be unavailable or the action refused with an explanation; the useful result is that the unauthorized change does not happen and staff know the next step. OrderPilot keeps access changes and blocked actions traceable. Use that information to resolve an unexpected refusal: was the wrong staff identity active, was the record outside scope, or does the role genuinely need a different permission? Grant the missing job responsibility deliberately instead of escalating the whole person to administrator.

Repeat the relevant check when someone's role changes or they move locations. A role review is most valuable at a real change in responsibility, while the expected work is still clear to everyone.

Fill in the store's access table

Use this table to record decisions before changing settings. “Decide” means the store must choose; it is not an app default or a suggested blanket grant.

Assign the people, run the sample checks, and keep the completed table with your training material. For the deeper policy decisions, continue with roles and permissions for a furniture store.

Sources

1. Point of Sale staff management — Shopify Help Center.
2. Plans for selling in person — Shopify.