Production rights before day one? Bind recruit-to-preboard permission switches to the hire effective date

Two days before the start date, the account had already been added to the production system.

During a spot check on information security, an account was found: its permission package was for a production line team leader, and the last login was two days before the employment effective date. HR explained, 'It's for early system training.' IT retorted, 'The person hasn't signed the contract yet, how can they view work orders?' Most of these incidents are not hackers but process habits—permissions are granted as soon as someone is hired, and when the employment is canceled, they are sometimes forgotten to be revoked. The convenience comes at the cost of 'permission debt' during audits, which becomes increasingly difficult to clean up all at once the longer it is delayed.

Manufacturing enterprise business systems are many (ERP, MES, WMS, quality), and the cost of "opening them for convenience first" is compliance and data exposure. Pre-employment is not "almost employed," but a bounded transition: moving information and tasks forward while keeping permissions back. Candidate experience and security are not contradictory—the contradiction is "using formal permissions to lazily complete training".

There is also symmetric risk on the exit side: the account remains even after someone leaves. If a disciplinary start date can be established at the time of joining, recovery at the end date will naturally be symmetrical; if both ends rely on human memory, both ends will have omissions.

From Hiring to the First Day: What Should Happen

Align each department using a timeline; it's shorter than writing another set of rules:

The establishment and the roster should be kept separate: pre-employment can be counted as 'pending entry,' but it should not directly occupy the in-service establishment, otherwise the establishment analysis will be inflated, and the recruitment and employing departments will argue over the two tables. On the payroll side: before the effective date, it is not advisable to enter the regular payroll; employees who have joined but have no attendance records will cause discrepancies in exceptions and piecework later on—this is an upstream issue affecting payroll reliability, not a problem with the payroll formula.

Concurrent positions, secondments, and temporary deputations all have time limits—the pre-employment permission package should also have a time limit. A 'temporary permission' with no expiration date becomes a ghost account after six months.

Minimum privilege package: Training needs to be conducted, but it should be conducted correctly

"Should the system be opened in advance for training?" — Yes, but what is opened is the pre-onboarding or training permission package: only to view training materials, fill in the portal, and access necessary read-only demo environments; the automatic expiration date is fixed. Official production reporting, pricing, master data maintenance, and payroll inquiries follow the official onboarding effective date.

Position/production line templates are very important. When a factory has a large number of new employees on the same day, permissions should be assigned according to positions, rather than giving everyone a 'temporary admin'. The minimum sets needed for production line operations, quality inspection, warehouse management, and clerical work are different; a universal package would inevitably be too large. Temporary permissions must be automatically revoked when onboarding is canceled — key checks often focus here: the person hasn't arrived, but the account still exists.

Outsourcing and internships use different permission packages and are revoked upon the end date, with logic symmetrical to formal employees, to avoid 'external accounts living permanently.' On-site mentors, if they need to view work orders, should also stay within the mentoring/readonly scope, rather than giving the team leader's package to the candidate in advance.

Task board replaces WeChat for requesting materials

Repeatedly urging for materials is often not because the candidate is deliberately delaying, but because tasks are scattered across emails and group chats. Pre-onboarding should be standardized: ID card, medical examination, contract, bank card, equipment collection... each item has a completion time and a reviewer. HR monitors the task board to urge completion, and candidates check the to-do list, so both parties are aligned on the same progress.

For batch onboarding days, there should be an overall completion rate dashboard: who is stuck at the medical checkup, who has not signed the contract, who has not received their equipment. This way, the site will not turn into people standing around filling forms and later having to scan and submit them. SSC and the hiring departments can also divide tasks according to the blocking items, rather than @ing each other in the group chat.

Resume and interview results should enter the pre-onboarding process from the cloud recruitment system to avoid entering once in the recruitment system and again in the EHR—long-term dual entry will inevitably lead to discrepancies. If the interface fails, manual pre-onboarding is allowed, but failures must go into the to-do list and be corrected and backfilled; it cannot turn into two sets of HR being maintained in parallel for a long time.

The organizational engine remains the only entry point for employee master data: EHR consumes the master data to handle transfers, onboarding, and pre-onboarding, without creating a separate shadow directory. The effective date of the transfer/order/onboarding drives the switching of permissions and process handlers—onboarding and transfers are two ends of the same time discipline. Formal access is granted on the onboarding date, and the approver is switched on the transfer date; the logic is consistent for audit purposes.

The position of JEDP-EHR on the link

JEDP-EHR Recruitment and Pre-Onboarding Emphasis: From resume to pre-onboarding task list; pre-onboarding has only minimal permissions, switching to formal permission package on the official start date; online form submission, data review, and onboarding processing are interconnected. On the organization side, positions are maintained by the organizational engine, while EHR carries out pre-onboarding and the roster, avoiding the situation where a person has formal system permissions before officially joining.

Integration with organizational permissions, attendance, and payroll: The effective date should align with appointment, formal permissions, and attendance records; payroll reliability depends on the correct entry status, to avoid issuing salaries before entry or having no attendance records after entry. Phase one focuses on integrating one type of position (including permission engine debugging and expiration recovery), phase two will handle batch onboarding and recruitment integration, and phase three will address residual accounts and spot checks for early activation.

When the team is very small and there is almost no access to business systems, the benefits of this topic are limited; but once there are ERP/MES accounts, the permission process becomes a must-answer question. Extended modules such as benefits, dormitories, and certificate processing should be added only after the main workflow (information—permissions—positions—attendance) is reliable, to avoid the joining date turning into 'ten windows issuing cards at the same time.'

Factory Mass Onboarding Day: From Filling Forms at the Team to Clearing the Queue

Common at manufacturing bases: 'Dozens of people join on the same day': dormitories, uniforms, medical checkups, contracts, and system accounts are all handled in the same morning. When there is no pre-onboarding task board, the on-site process inevitably regresses to lining up and using paper checklists; when there is a task board but permissions are still granted for official packages in advance, both safety risks and processing efficiency deteriorate simultaneously.

It is recommended to fix three rhythm points in batch scenes:

• T-7: Mass generate pre-onboarding tasks and training permission packages; blocking items (medical check, background, key documents) must be visible.
• T-2The hiring department and SSC will divide the responsibilities to clear the blockage list; items that are still incomplete should be marked as 'temporarily deferred', and do not formally grant authority early just to fill heads.
• T0: Switch official permissions and attendance records according to the effective roster; those not on the roster shall not be mixed into the activation batch.

If a training classroom needs to demonstrate the production system, using a separate training tenant or a desensitized environment is much safer than 'temporarily giving formal permissions and taking them back after the class'—the latter is the easiest to forget to revoke. Equipment pickup, work badges, and access control can also be listed on the same task board, but access control and business system permissions should be modeled separately: being able to enter the factory does not mean being able to modify work orders.

In terms of candidate experience, having a transparent process itself can reduce follow-up inquiries; regarding security, automatically closing accounts upon contract expiration or onboarding cancellation is more effective than adding a couple more pages of instructions. Both can coexist, provided you are willing to remove 'convenience' from formal permissions. During spot checks by the information security committee, including the three columns 'Account Activator / Approver / Reclamation Time' can expose process gaps more than just looking at the account list.

Three Questions about Recent Monthly Entry Spot Checks

No need to release a new module this week, just do a sample first:

1. Among those who joined in recent months, how many had official business access before the effective date? List the system names and the persons who enabled them.
2. During the pre-employment period, are the permissions limited to the minimum/training package, and do they have an expiration date? Have the permissions been closed for those who canceled their onboarding?
3. On the effective date of joining, are the organizational appointment, official permissions, and attendance records all completed on the same day? If one is missing, it is recorded as a break.

If any of the three checks fails at scale, fix effective-date switching and permission-pack templates before talking about a 'digital recruiting experience.' In mass onboarding weeks, add one more: can the task board expose blockers two days before the hire date? Answer clearly and the floor shifts from chasing people to clearing a queue; if not, welcome kits will not hide day-one permission and document chaos. Put spot-check results straight into joint HR–InfoSec minutes: who granted access, who approved, when it was revoked—if that cannot be written, stop 'hire equals production rights' first.

• EHR HR solution
• Organizational Permission Inheritance
• Attendance anomaly
• Compensation data is reliable