01
Find the apps the leaver authorized
List third-party apps connected through the employee’s Google account so that access outside the normal provisioning record is visible during offboarding.
If someone left tomorrow, would you catch everything they had access to? Standard offboarding closes the account, transfers data, and releases the licence. We’ll show how to find the access that sits outside that checklist — connected apps, delegated Gmail and Calendar access, API tokens, and privileged admin access — and bring it into a controlled review before it is left behind.
Join the session to see how to uncover connected access that can survive a standard Google Workspace offboarding.
Most offboarding processes are built around access IT knows it provisioned: the Google account, Groups, shared drives, licences, and core systems. The harder part is access the employee created, delegated, or authorized themselves.
A Google sign-in can leave a third-party app connected to mail, files, or Calendar. Delegated Gmail and Calendar access can remain buried in account settings. API tokens can exist in tools Google cannot see. And an IT or admin departure can carry a completely different set of privileged-access risks.
We’ll show how to make this hidden access visible, capture the right evidence, and put the findings in front of the right reviewer before access is revoked or the account is closed.
The demo focuses on the practical controls that close the gap: discovering access that sits outside the standard checklist, keeping API-token ownership visible, reviewing activity before revocation, and applying additional checks when privileged users leave.
List third-party apps connected through the employee’s Google account so that access outside the normal provisioning record is visible during offboarding.
Bring delegated mailbox and Calendar access into the same review instead of relying on someone to remember that those relationships exist.
Use activity context to help distinguish an abandoned connection from access that may still support a live business process.
Automatically create, populate, and perform checks against a registry so token ownership does not depend on a spreadsheet someone has to remember to update.
Send connected-app and delegation findings for review before tokens are revoked, so the business can identify dependencies that should be transferred rather than simply broken.
Branch privileged departures into a stricter review so admin roles, delegation grants, and other elevated access are not treated like a standard employee offboarding.
You’ll leave with a clearer model for finding hidden access, deciding what needs human review before revocation, and treating privileged departures differently from standard employee offboarding.
Understand the categories of access most likely to survive a standard Google Workspace offboarding.
Give managers a chance to identify dependencies before connected access is removed and a business process breaks.
See how a maintained registry can make otherwise invisible token ownership part of the offboarding conversation.
Apply the right level of scrutiny when the person leaving held administrative or other elevated access.
Everyone who registers can claim a free connected-app audit. The audit uses Zenphi to report third-party app access still tied to your inactive accounts, so you can see what remains connected.
IT Directors and Heads of IT, CISOs and security leads, Google Workspace administrators, and IT operations teams responsible for employee departures and access governance.
No. The session is open to anyone responsible for offboarding or access governance in Google Workspace. The demo uses Zenphi, but you do not need to be a Zenphi customer to attend.
After you register, you can book the audit directly from the Thank You page. The audit uses Zenphi to report third-party app access still tied to your inactive accounts, so you can see what remains connected.
Yes. Bring your own offboarding edge cases, access gaps, and process questions for the live Q&A.
See how to surface connected apps, delegated access, API-token ownership, and privileged-access risks before they are left behind after an employee departure.
Thursday, November 19 · 2 pm ET · 40 minutes