Approval-gated account disabling across Google, GitHub, and Okta

Starting promptUse this prompt as a starting point to build your workflow.

Build a workflow triggered by a deactivation request containing the target user's email. Create a Jira ticket and request approval via Jira or email. On approval, suspend the account in Google Workspace, disable/remove from org in GitHub, and deactivate in Okta with sessions revoked, updating the Jira ticket after each step. If not approved within a window, escalate or close. Handle missing accounts gracefully and retry failures. Output the per-system results recorded on the ticket.

New to Tines?Sign up free for Tines 3B Explore Edition

What this prompt builds

Suspend a user in Google Workspace, GitHub, and Okta only after approval, with every step tracked in Jira.

The problem

Disabling accounts ad hoc risks both leaving access open and accidentally locking out the wrong person, with no record of who approved what. Auditors want proof that deprovisioning was authorized.

Solution and impact

This workflow secures approval via Jira or email before suspending the user across Google Workspace, GitHub, and Okta, documenting each action in the Jira ticket. Deprovisioning is fast, authorized, and fully auditable.