Written by DROPS.ST.
Separate the information needed for employment administration from the information needed to operate a shop account. Do not copy an employee’s document bundle into sales software merely because the account is being created at the same time.
DROPS gives staff a shared operating context for products, Customer Accounts and orders, with defined order-action controls. Use that context to describe the work the employee will do. Keep employment records with the responsible process rather than treating the shop account as a general file for the person’s private information.
Name the purpose before choosing the destination
An account administrator needs to establish the authorized user and approved work. Payroll, employment agreements and other personnel processes serve different purposes and may have different responsible people.
List the exact information requested by each process. Check the supported account setup rather than assuming a document is required because it appears in an onboarding checklist.
The OPC’s workplace guidance recommends mapping employee information and considering whether each collection has a legitimate purpose. It also notes that obligations can vary between provinces and workplaces. Determine the applicable requirements for your business; this is not a universal employment-document list. OPC workplace privacy guidance.
Use a record-destination worksheet
The destinations below are review decisions, not claims that DROPS supplies an HR or payroll module.
| Purpose | Information to establish | Responsible destination |
|---|---|---|
| Operational identity | Required account identity and approved contact route | Supported staff-account process |
| Work authority | Tasks and actual permission scope | Account administrator’s access decision |
| Training readiness | Demonstrated responsibility and reviewer | Approved training record |
| Employment administration | Documents required for the actual employment purpose | Responsible personnel process |
| Payroll administration | Required payroll information | Authorized payroll process |
| Exceptions | Reason a proposed extra item is needed | Named owner who reviews the request |
For each row, record who may handle it and which copy is authoritative. Avoid placing sensitive documents in a general note merely because uploading is convenient.
Pass a confirmation when a document is unnecessary
Sometimes one process needs to know another check has been completed without receiving the underlying document. Ask whether an appropriate confirmation and responsible contact will meet the task.
Do not use this approach to omit evidence that the actual process must retain. The owner must decide which information is required, where it belongs and what approved confirmation is sufficient elsewhere.
Explain the request to the employee. Staff should understand what is being collected for shop access and what belongs to a separate employment process. A convenient combined form should not hide those different purposes.
Hypothetical example: one onboarding bundle, two owners
A new employee submits a bundle requested for personnel administration. The shop administrator receives a task to create the operational account.
Instead of copying the whole bundle into the shop, the administrator confirms the information the account process needs and records the approved work responsibilities. The personnel owner retains the documents under the separate approved process. A missing confirmation goes back to that owner rather than becoming a general request for more personal details.
This hypothetical example does not define legally required documents or verify a native DROPS HR workflow.
Review access and copies separately
DROPS product-edit access includes customer-account edits and wallet adjustments. An operational title does not restrict that broader grant. Review the intended work with the staff permissions guide, and use the training sign-off guide for demonstrated readiness.
Those shop controls do not establish restrictions on a separate personnel folder or copied attachment. Review each destination on its own: approved recipients, working copies, retention and supported disposal.
A staff departure also needs both processes. Removing shop access does not determine the treatment of retained employment records. Coordinate with the responsible owner using the offboarding checklist, without assuming global deletion or revocation.
Keep the shop account focused on shop work
DROPS brings daily product, customer and order work together. Give that operational account the information and authority its actual purpose needs, while keeping employment administration accountable to its own owner.
Explore DROPS.ST and the shop demos. Review a fictional onboarding task with the worksheet and identify which information the shop needs, which process holds the rest and who resolves an exception.