A successful imper.ai deployment depends on clear ownership. This article describes operational ownership and responsibilities.
For details on what each role is permitted to do within the platform, see imper.ai Permissions and Access Model.
In this article
imper.ai administrator
The imper.ai administrator owns platform configuration and ensures the environment remains operational and secure.
Typical responsibilities
Manage organization-level settings and permissions
Define and maintain protected user scope
Ensure verification flows are enabled and applied correctly
Coordinate validation before expanding rollout
Integration owner
The integration owner maintains external connections and ensures imper.ai can ingest the data it needs.
Typical responsibilities
Connect and maintain integrations (identity providers, communication tools, HR tools)
Ensure required permissions/scopes are granted and remain valid
Coordinate changes when the external system changes (for example, app permissions or admin policies)
Operational users (helpdesk and security operators)
Operational users rely on imper.ai in real workflows. They typically execute or respond to verification outcomes during sensitive interactions.
Typical responsibilities
Follow verification workflows during helpdesk and communication events
Escalate failed or suspicious verifications based on internal process
Report false positives or workflow gaps to the administrator
Auditors and viewers
Auditors and viewers require visibility for compliance, investigations, or security oversight.
Typical responsibilities
Review verification outcomes and platform activity for oversight
Use the audit log to support investigations and reporting
Validate that process requirements are being met
Recommended ownership model
Admin: Owns configuration, protected user scope, verification flows, and rollout planning
Integration owner: Owns integration permissions, stability, and lifecycle maintenance
Operators: Own day-to-day execution and escalation in real workflows
Auditors: Own periodic review and compliance oversight
Tip: Assign at least two admins or an admin + backup owner to prevent lockout and ensure continuity.