A person appears in your personnel directory but has no platform login. Another person has a login and unfinished compliance work. Those are different states, and they need different actions.
In the Sythe platform, start with Personnel in the correct organization. Use an organization admin account for this walkthrough. Directory details and private compliance information have different permission checks, and access actions depend on your role.
Check the person's record before changing access
Use the Active or Separated filter when it helps locate the right person, then open their record. Review the source, manager, and GRC-role information. A No platform login label identifies the login state; it does not mean the person is absent from your workforce records.
Confirm identity before acting. Similar names, an external contact, and an employee using a second email address can lead to the wrong invitation or access change if you rely on a name alone.
The right outcome may be a corrected record, an invitation, or no change at all. Decide that from the person's actual relationship to the organization.
Inspect the applicable compliance work
As an authorized organization admin, open Compliance and read the checklist states and remediation guidance. The person, organization admins and owners, assigned operators, and system admins can view this information. Other members do not receive another person’s compliance checklist. Use the listed work to identify what remains outstanding instead of sending a general request to “finish compliance.”
When outstanding applicable items exist, Send compliance reminder provides a direct follow-up action. Verify the person and the unfinished work before using it. For a demonstration, use a designated test person so the walkthrough does not notify a customer employee.
Applicability matters. Separated, external, and non-human records are exempt from workforce checks and acknowledgments. Do not describe an exemption as evidence that the person completed every employee requirement.
Use the action that matches the current login state
The directory offers actions based on the record's state and your permissions. These can include Upgrade to login, Send invitation, Resend invitation, Copy invite link, Revoke access, and Restore access.
For a person who should join the platform, establish whether an invitation already exists before resending it. For an access removal, confirm the intended account and review the resulting state after the action. Do not mark work finished merely because a confirmation dialog closed.
An invitation link is an access artifact. Share it only through the approved route for the intended recipient.
Keep external offboarding separate
Revoke access in this walkthrough concerns access to the Sythe platform. It does not prove that Google Workspace, GitHub, an SSH key, or a vendor account was revoked.
When someone leaves, use the personnel record as one part of the broader departure process. Identify the other systems that own access and retain their actual completion records. If a deploy key or shared credential needs review, assign that work explicitly instead of treating a platform login change as the end of offboarding.