First staff sign-in
When EDUBase enables first staff sign-in approval for your school, existing staff keep their access. A newly created staff login first proves its normal password or sign-in QR, then waits without receiving an application session. Ask the school owner to open Owner App → Approvals → Staff Access. The card shows the staff identity and a private approval code valid for fifteen minutes. The owner chooses Approve or Reject. After approval, the staff member signs in again normally. Approval never adds privileges, app access or campus access.
Private owner decision
Only a centrally verified school owner can decide; school administrators and the EDUBase Admin app cannot approve. School owners never need approval themselves. No SMS, email, WhatsApp or push is sent. Open Staff Access to refresh the queue. An expired code needs the staff member to try signing in again before approval; rejecting is final for that identity. Repeated sign-in attempts reuse one request. Final decisions are retained.
Gradual rollout
EDUBase controls this action per school. Other approval actions are not enabled. Switching the action off suspends its sign-in requirement and hides decision controls, without erasing decisions. Switching it back on retains the original staff baseline and previous decisions. Staff created while off may need approval when it is re-enabled. Existing status, employment, app, device and campus rules continue to apply.