Connect with a clear boundary.
A customer connection needs more than a saved token. We agree the purpose, permissions, processing locations and recovery responsibilities before using live company data.
Workspace and role boundaries
Server sessions establish workspace membership and application role. Data access is checked by the server. Private HR cases have their own requester and HR boundary. Customer acceptance should verify the deployed roles and the actual information each role can read.
Provider authorization
Stored provider secrets use AES 256 GCM encryption bound to the workspace and provider. The deployment needs a stable protected encryption key. API responses do not return those stored secrets. Your administrator grants the scopes needed for the selected operations.
Company sign in
Atria supports configured OIDC sign in and scoped SCIM Users provisioning. Identity membership must exist before company sign in. Company identity policy can provide MFA; local password sign in does not include a separate MFA service. Provider directory reads are distinct from login provisioning.
Data location and recovery
Hosting, database, attachments, backups, logs, email and optional AI processing all affect the data flow. Canadian data residency must be selected and verified for the complete deployment. Backup tooling exists; schedules, protected storage, monitoring and recovery objectives remain operational decisions.
Optional AI assistance
Authorized and redacted context can support summaries and other assistance when configured. The AI integration cannot grant itself permissions or run connector writes. The customer decides whether external AI is permitted and which provider and data categories can be used.
What to review together
Review data categories, retention, attachment handling, processors, incident contacts, support and offboarding. The application does not include a malware scanning engine or establish SOC 2 or ISO certification. Customer requirements determine whether additional infrastructure or controls are needed.
Plan your next step
Tell us about the workflow and systems involved. We will review the fit before proposing a pilot.
Plan your pilot