Keeper adds Freshservice workflow app for vault and privileged access requests

Keeper Security launched a Freshservice Workflow App that lets IT and security teams search the Keeper vault and handle access approvals directly inside Freshservice tickets. The integration is designed to cut approval delays, keep decisions in the audit trail and avoid moving secrets into Freshservice.

Why it matters: - The new workflow is meant to reduce approval delays that often slow helpdesk and security operations. - It keeps vault and privileged access decisions inside a governed ticketing process instead of routing them through email, chat or other side channels. - Keeper says the design preserves zero-knowledge controls while making Freshservice the request interface, not a secret store.

What happened: - Keeper Security announced a Freshservice Workflow integration on Oct. 1, 2026. - The app connects vault access and privileged access requests to Freshservice ticketing workflows. - Agents can fulfill Keeper vault access and approval requests, including Endpoint Privilege Manager and Cloud SSO device approvals, from a Freshservice ticket. - The integration is available now in the Freshworks Marketplace for organizations with an active Keeper Commander deployment.

The details: - An employee can submit a request through a Freshservice service catalog item. - The assigned agent can search Keeper content, configure permissions and approve or deny the request from a Keeper Vault tab inside the ticket. - Every action runs through a customer-hosted Keeper Commander ServiceMode endpoint. - Keeper says this keeps its zero-knowledge encryption and access controls intact. - Keeper says credentials are not stored inside Freshservice’s IT Service Management and Enterprise Service Management platform. - The integration also supports Endpoint Privilege Manager and Cloud SSO device approvals when paired with Keeper's ITSM for Freshservice app. - Security admins can use one ticketing interface for both incident-driven access requests and routine approval workflows. - More information is available in Keeper's documentation.

Between the lines: - The product pushes privileged access decisions closer to the existing helpdesk flow, which can improve speed and reduce process drift. - The customer-hosted ServiceMode endpoint is the security design choice that lets Keeper claim the attack surface does not expand when Freshservice is connected. - Keeper frames the release as more important as access requests grow across human users, machines and AI agents.

What's next: - Organizations with an active Keeper Commander deployment can adopt the app now through the Freshworks Marketplace. - Teams that already use Keeper for ITSM can extend the same ticketing workflow to additional approval types. - The broader push is toward tighter control of access requests as identity traffic increases across enterprise systems.

The bottom line: - Keeper is betting that security teams want faster access approvals without giving up auditability, zero-standing privilege or control over where secrets live.