Zenphi adds automated Google Workspace access approvals based on employee context

Zenphi says its September platform release now automates Google Workspace access requests that identity providers do not cover, routing approvals by factors such as department, cost centre, site and reporting line. The update targets manual exceptions that often slow IT teams and create gaps in access governance.

Why it matters: - Google Workspace organizations can now automate access requests that depend on employee context, not just account provisioning. - The update is aimed at requests that are usually handled manually, such as shared drive access, delegated Gmail access and temporary elevated permissions. - Zenphi says the change helps close a common gap in identity tooling: approving access after an account already exists.

What happened: - Zenphi added a new Google Directory Get User first-class action in its September platform release. - The no-code workflow automation platform now returns flattened tokens for Department, Cost Centre, Direct Manager, Employee ID and Desk Location. - Those tokens can drive approval routing across hybrid identity estates in Google Workspace environments. - Zenphi says the feature routes requests based on the requester’s site, business entity, department, contract type and the owner of the resource being requested.

The details: - Directory sync still creates accounts, assigns job-based groups and provisions licences, but follow-on employee requests fall outside that process. - Common examples include access to a shared drive outside a standard role, creating a Group for a project, delegated access while a colleague is on leave and elevated permissions for a fixed period. - Zenphi says these requests are often treated as edge cases and resolved manually because the needed context was not available at provisioning time. - The new directory attributes can be used without custom parsing, which allows workflows to branch automatically. - A request can be routed to a local manager at one site, to both a manager and a data owner at another, or through an extra approval step for specific cost centres or business entities. - The same context can also support shared drive permission management, Google Group membership and Gmail delegation. - Zenphi said the workflows can now use the employee’s organisational context at the time of the request instead of relying on provisioning-time assumptions. - In a webinar poll of IT leaders earlier this month, 60% said they have a ticketing system but IT still does the work by hand. - Another 23% said they have no formal process. - Only 7% said the process is fully automated. - In the same poll, one-third of respondents said their team handles more than 50 such requests manually each week.

Between the lines: - The release reflects a broader shift from static identity setup to context-aware access decisions. - That matters because many access requests are tied to changing business conditions, not permanent job titles. - Zenphi is positioning itself as the execution layer between identity providers, service desks and Google Workspace rather than as a replacement for those systems. - The company is not a dedicated access control or approval workflow vendor, but it is pushing deeper into access operations. - Zenphi cites customers including Gordon Food Service, Google Cloud’s Customer Experience Center and Emerson College. - Documented implementations have reduced IT ticket volumes by 83% and cut administrative time spent on Google Admin tasks by up to 85%, according to Zenphi.

What's next: - Organizations using Google Workspace can apply the new routing logic to more request types as they move away from manual exception handling. - The update is designed to support approval decisions that vary by location, reporting line and resource ownership. - Zenphi says its workflows will continue to work alongside existing identity providers, service desks and IGA tools.

The bottom line: - Zenphi is trying to automate the messy middle between user provisioning and everyday access requests, where identity systems often stop short.