Workforce identity
SAML/OIDC, MFA and Conditional Access at the IdP, verified domains, and discovery from a work email.
Autopen's organization controls are in design-partner validation. This page says what is live today, what is being validated, and how to start a pilot.
Autopen’s enterprise direction starts with the information procurement, security, privacy, and identity teams need for a structured evaluation.
Managed domains, SSO policy, directory lifecycle, roles, and session revocation define access.
The audio, transcript, notes, metadata, provider, storage, and deletion path is documented explicitly.
Retention, export, sharing, app lock, offline access, and participant notice can be restricted.
Operational, real-tenant, endpoint, deletion, and independent assurance evidence remain required.
Production identity is delegated to WorkOS. The design supports organization SAML or OIDC SSO, verified-domain policy, directory-driven joiner/mover/leaver events, bounded roles, and revocable Autopen sessions.
SAML/OIDC, MFA and Conditional Access at the IdP, verified domains, and discovery from a work email.
Signed directory events with timestamp checks and duplicate-event handling, with durable processing and reconciliation.
Active membership, Enterprise entitlement, role, tenant ownership, and restrictive policy are rechecked by the API.
Autopen separates governance metadata from meeting content. Administrators can investigate, contain, and delete without an ordinary route for opening private member transcripts or notes. On a protected account, the member's saved transcript and notes are encrypted to the member's key.
Where an organization manages the account, the organization may hold a recovery copy of that key, and the member cannot turn it off from the app.
Independent transcript, notes, and Trash retention; export and sharing controls; app lock; offline grace; participant-notice requirement; SSO and MFA intent.
Suspend or deprovision members, revoke normal sessions, preserve role hierarchy, and guard against removing the final organization owner.
Platform, app version, enrollment, last-seen, and wipe-command status without collecting a stream of meeting activity.
Aggregate consumption, append-only security events, CSV export, and signed security-event feeds for your SIEM, built to carry no meeting content.
Autopen’s application-level containment path revokes normal sessions immediately and leaves a narrow, device-scoped credential able only to receive and acknowledge its own deletion command.
Normal access and refresh sessions are invalidated immediately.
The narrow credential can receive only its own expiring control command.
Content, cache keys, preferences, and normal credentials are removed.
Only a returned acknowledgement changes the command from pending.
The final-owner guard and privilege hierarchy prevent lower or equal roles from using a different endpoint to contain a more privileged peer.
| Capability | Owner | Admin | Security admin | Member |
|---|---|---|---|---|
| View organization, members, devices, and aggregate usage | Yes | Yes | Yes | No |
| Revoke sessions or suspend a member | Yes | Yes | Yes | No |
| Change administrator roles | Yes | No | No | No |
| Change security and data policy | Yes | No | Yes | No |
| Wipe devices or purge member content | Yes | No | Yes | No |
| Read another member’s private transcript or notes | No | No | No | No |
Source implementation is not operating evidence. We make that distinction explicit so a design partner can evaluate the real maturity of each control.
Design partners help define the IdP, directory, retention, processing-region, MDM/MAM, SIEM, DLP, consent, procurement, and assurance requirements before real meeting data enters a pilot.