RoboDesk / Platform
Configuration & deployment
Roles, integrations, privacy controls and where the whole thing runs — the layer your security and IT teams actually review.
Access and identity
- Role-based access control with team-scoped visibility, so an agent sees only the interactions they should.
- Single sign-on across every RoboDesk application, against your own identity provider — Azure AD, Okta or Google Workspace.
- Single-session enforcement, which prevents credentials being shared across devices.
Operational configuration
- Feature enablement. Modules and capabilities are switched on per tenant, so you run what you need.
- Integration settings. Channels, CRM, telephony and intranet connections configured without a code change.
- Privacy controls. Anonymization, PII masking in exports and audit support.
Deployment models
| Cloud | Google Cloud, Microsoft Azure, AWS, Huawei Cloud or Alibaba Cloud. |
|---|---|
| Regions | Egypt, Saudi Arabia, the GCC and Europe. |
| On-premise | The whole platform inside your own data centre, deployed in days rather than months. |
| Isolation | A dedicated namespace per tenant; no shared application runtime between customers. |
What it is not
This module configures RoboDesk. It does not replace your IAM platform, own your compliance certifications or stand in for your DevOps tooling. See Security & compliance for the full control set.
See it run on your own traffic.
Thirty minutes with a CX engineer. No slideware.