Keeper Security has announced the Keeper Teams App, an integration that embeds privileged access request and approval workflows within Microsoft Teams. The integration is powered by Keeper Secrets Manager and Commander Service Mode, enabling credential access workflows to be managed without requiring users to switch tools.
When access requests are handled through email, ticketing systems, or separate portals, organisations may have reduced visibility for enforcing zero-trust access controls. The Keeper Teams App addresses this by bringing auditable access workflows into Microsoft Teams.
The Keeper Teams App supports five core workflows:
- Record and Folder Access Requests: Users can request access to specific vault records or shared folders, using time-limited access and supporting zero standing privilege. Auto-rotation can be applied after access windows expire for supported record types.
- One-Time Share Requests: Users can request self-destructing share links for passwords or secrets, with optional configurable sharing settings.
- Endpoint Privilege Approvals: Privilege elevation requests from Endpoint Privilege Manager are routed in real time to designated approvers.
- SSO Cloud Device Approvals: Administrators can approve device requests within Teams, including scenarios where additional deployment components are not present.
- Self-Service Secret Creation: Users can create login records with auto-generated passwords directly within Teams, with records stored in designated shared folders.
The application supports mixed environments by identifying whether records are Classic shared records or Nested Shared Folder (NSF) records, applying the appropriate permission model in each case. The customer-hosted Teams App is deployed alongside Commander Service Mode using Docker, allowing cryptographic operations to remain within an organisation’s infrastructure and supporting a zero-knowledge architecture.
The release adds to Keeper’s existing integrations with platforms such as Jira, ServiceNow, and Slack, and is positioned as part of a broader approach to embedding privileged access workflows within commonly used collaboration tools.
