UnifyDesk
In developmentTake a tour
SECURITY

Workspace controls are part of the product foundation.

UnifyDesk is being built with company boundaries, access controls and account protections designed for team-based customer operations.

Controls that match how the workspace is structured.

Company isolation

Keep company data and workspace context separated.

Company-scoped accessSeparate company workspacesCompany-level data controls

Identity & access

Manage who can see and modify product areas.

Role-based permissionsUser managementInvitation flows

Account protection

Protect sign-in and sensitive account actions.

2FA supportSession controlsPassword management

Provider boundaries

Keep external provider credentials and workflows controlled.

Connection permissionsManaged service boundariesProvider-specific scopes

COMPANY BOUNDARIES

Access follows the company and the member.

The developing platform checks company membership and role permissions before allowing company-scoped actions. A company identifier alone does not grant access to its workspace. Active membership, company status and the permission for the requested action matter together.

For a growing team, decide who needs to manage users, work with conversations and connect providers. Review access when responsibilities change so the workspace reflects the company's actual team.

Explore connected conversation work

Keep responsibilities clear

  • Use company roles and permissions for the work each member needs.
  • Limit provider connection management to authorized members.
  • Review membership and account access as the team changes.
See workflows for growing teams

ACCOUNTS & CONNECTIONS

Protect access to the workspace and its providers.

Two-factor account protection

Two-factor verification is part of the developing sign-in flow when enabled for an account. Sensitive account changes also have verification controls. Team members should protect their own accounts alongside the company's role and permission settings.

Session controls

The platform supports revoking an individual session or a user's sessions. Account changes such as a password update can revoke existing access. Session controls help a team respond when an account or device should no longer remain signed in.

Provider credentials

Connected provider credentials are stored in encrypted form and managed behind authorized company access. Disconnecting a connection removes its stored credentials. External account permissions and provider-specific scopes still govern what the connection can do.

PRE-LAUNCH

Security and production-readiness checks continue before broader access.

Public documentation will expand as the platform moves through early-access and production readiness. These controls describe the developing architecture; production verification continues before broader access. No security certification is advertised here.

CHANNEL WORKFLOWS

Plan team access around the customer workflow.