Beyond Provisioning

User provisioning handles the predictable access that can be assigned when an account is created: the account itself, standard groups, licences, and organisational-unit placement. Access request automation handles what happens afterwards — requests for project groups, Shared Drives, delegation, temporary permissions, third-party applications, elevated roles, and other access that depends on context that could not be known at provisioning time. Workflow platforms like Zenphi can help connect these post-provisioning requests to approvals, Google Workspace actions, expiry, and audit records.

The requested action is usually simple; the context is not. A single request may depend on employment status, contract type, legal entity, site, current manager, resource owner, access level, duration, and additional security policy. Platforms like Zenphi can help resolve that context from existing systems and route the request according to the policy that applies to that specific combination.

Yes. Google Workspace and Admin APIs are accessible from Apps Script, so the capability is there. The challenge appears as the process grows: conditional routing becomes harder to maintain, approvals need persistent state, expiry needs reliable scheduling, audit history must be built deliberately, and ownership becomes risky when only one or two people understand the code. Workflow platforms such as Zenphi can be an alternative when the process needs shared ownership, visual logic, approvals, auditability, and easier maintenance.

No. An existing helpdesk or ITSM can remain the front door. A ticket can trigger the workflow, which resolves context, applies policy, routes approvals, performs the Google Workspace action, records the result, and updates the ticket. Platforms like Zenphi can sit behind the existing service desk as the execution layer, or support form- and chat-based self-service where that model fits better.

A robust automated access request should include structured intake, context lookup, policy checks, approval routing, provisioning, confirmation, audit logging, and review or expiry. The exact lookups and policies change by request type, but the underlying sequence remains consistent across Shared Drive permissions, Group membership, licence assignments, site transfers, and similar requests. Platforms such as Zenphi can be used to coordinate these steps in one workflow.

Temporary access should carry an end date from the moment it is approved, with revocation scheduled automatically. If removal depends on somebody noticing a reminder later, permissions tend to accumulate. Workflow platforms like Zenphi can help tie the approval and expiry together so temporary access is removed as part of the same governed process rather than treated as a separate manual task.

Start with a recurring request that has a consistent shape, an approver that can be determined from data you already hold, and an action that can be performed through Google Workspace administration. Then compare monthly volume with the number of approval layers: the qualifying request with the highest coordination load is usually the strongest first build. Platforms like Zenphi can then be used to model that request end to end before expanding to more complex cases.

Gordon Food Service used Zenphi behind its existing Employee Center and ServiceNow environment to automate Google Workspace service-delivery workflows including Groups, mailboxes, delegation, licences, access visibility, Chrome and OAuth requests, forwarding alerts, and Shadow IT monitoring. The team reported an 83% reduction in ticket requests and an 85% cut in admin time spent on Google Admin tasks.