Trustdesk
Trustdesk is cidaas's central administration hub for platform 4.x. It replaces the legacy Admin Dashboard with a cleaner, purpose-built workspace where operators manage the full lifecycle of identity and access configuration: registration, authentication, permissions, branding, and security.
cidaas 4.x Admin Dashboard remains availableThere is nothing you need to migrate. Your existing configuration, users, apps, and roles keep working. Trustdesk is a new administration UI on the same instance; open it at /trust-desk. The legacy Admin Dashboard at /admin-ui continues to run in parallel during the transition. New 4.x capabilities are available in Trustdesk only. See Migrating to Trustdesk below.
What Trustdesk means
Settings are grouped by purpose (Users, Integrations, SecureOps, Branding, and more) instead of scattered legacy menu tabs.
Define fields, layouts, providers, and scopes once, then reference them by ID across applications.
Eight functional personas map to Trustdesk sections. Assign roles to match responsibilities; not everyone needs full admin.
Migrating to Trustdesk
Short answer: you do not need to migrate anything.
Trustdesk is the new administration UI for cidaas 4.x. It reads and writes the same instance configuration as before. There is no data migration, no reconfiguration of apps or users, and no cutover project required to start using it.
| Question | Answer |
|---|---|
| Do I need to move or re-create apps, users, or settings? | No. Existing configuration continues to work. |
| Will Admin Dashboard stop working? | No. /admin-ui remains available in parallel during the transition. |
| Where do I open Trustdesk? | https://{your-instance}/trust-desk |
| What is only available in Trustdesk? | New 4.x capabilities (for example Group Verification Filter, hosted page layouts & theming, Translation Management, SecureOps enhancements, Agentic Chatbot). |
| What should my team do? | Start using Trustdesk for day-to-day administration. Keep /admin-ui as a fallback while you learn the new layout. |
Trustdesk requires cidaas 4.x. On older platform versions, continue using the Admin Dashboard.
For a detailed Admin Dashboard → Trustdesk menu mapping (where each legacy setting lives now), see the Introducing Trustdesk upgrade guide.
How you use it
/trust-desk.
Find your role
Pick the persona closest to your day-to-day work. Assign the matching cidaas roles in the CIDAAS_ADMINS group; Trustdesk menus and actions are gated by those roles. Prefer scoped manager/viewer roles over ADMIN / SECONDARY_ADMIN unless someone truly needs full platform access.
Admin users must be members of CIDAAS_ADMINS. Roles listed below are the primary Trustdesk roles for each persona. Legacy Admin Dashboard roles (for example APP_CREATE, USER_READ, SETTINGS_CREATE) still work during the transition where they map to the same areas.
- App Developer
- Support Engineer
- Security Officer
- Brand Manager
- Compliance Officer
- Administrator
Software developers who integrate applications with cidaas via OAuth/OIDC, APIs, and SDKs.
APP_MANAGERINTEGRATION_MANAGERSCOPE_MANAGERAPP_VIEWERSCOPE_VIEWERLegacy: APP_CREATE, APP_READ, APP_DELETE, SETTINGS_CREATE, USER_INVITETypical first task: Register your first OAuth application and configure redirect URIs.
Support engineers who troubleshoot user issues, recover accounts, and diagnose login problems.
USER_MODIFIERUSER_VIEWERLegacy: USER_READ, USER_CREATETypical first task: Find a user account and review their status, groups, and devices.
Security professionals who monitor threats, configure MFA, and enforce password and fraud policies.
SECOPS_MANAGERSECOPS_VIEWERUSER_MODIFIERANALYSTLegacy: SECURITY_CREATE, SECURITY_READ, MFA_ACTIVATE, MFA_READ, REPORTTypical first task: Review the Security Dashboard for configuration issues and suspicious activity.
Brand strategists who shape the visual identity and localized experience of login and registration flows.
UISETUP_MANAGERUINLS_MANAGERUISTYLE_MANAGERUISETUP_VIEWERUINLS_VIEWERUISTYLE_VIEWERLegacy: SETTINGS_CREATE, SETTINGS_READ, SETTINGS_DELETE (branding)Typical first task: Ship a branded login page in German and English with consistent wording per application.
Compliance professionals who ensure regulatory adherence, consent management, and audit evidence.
CONSENT_MANAGERCONSENT_VIEWERANALYSTUSER_VIEWERAPP_VIEWERSECOPS_VIEWERPlus other *_VIEWER roles as needed · Legacy: SETTINGS_READ, GROUP_READ, SECURITY_READ, USER_READ, APP_READTypical first task: Review consent definitions and export activity evidence from Reports.
IT administrators responsible for platform reliability, user access, and overall system configuration.
ADMINSECONDARY_ADMINOr combine module manager roles instead of full adminTypical first task: Open Trustdesk Home, confirm your instance version, and check Reports or critical Integrations for anything that needs attention.
For full persona profiles and access scopes, see the Introducing Trustdesk upgrade guide.
Standout capabilities
These capabilities define the Trustdesk experience in cidaas 4.x beyond a menu reorganisation.
Application Hub
When you open an application under Integrations → Applications, the Application Hub groups that app’s settings into clear buckets so you can see what is already configured, what is still available to configure, and what no longer belongs for that app type.
| Bucket | Meaning |
|---|---|
| Configured | Sections already filled in for this app type; edit them in place |
| Still configurable | Allowed for this app type but empty; look for Add or Required badges |
| Other / legacy | Data exists but is no longer valid for this app model; shown with a warning |
How Trustdesk helps avoid wrong configuration:
- App-type rules: only sections that apply to the application type appear (for example, SAML SP versus Regular Web)
- Hub status: the UI reflects which sections are configured, still available, or leftover from older models
- Validate before save: check a configuration segment without persisting it
- Creation wizards: guided flows for creating apps and providers
- Shared references: apps link to existing User Setup and Hosted Pages Layout profiles instead of copying settings; create the shared config first
Learn more: App management · Application types
Brand every touchpoint centrally
Trustdesk separates structure (layouts), visual identity (theming), and wording (translations) so you can brand login and registration without redeploying code.
- Hosted Pages Layout: structure of login and registration pages
- Theming: colors, typography, and visual settings
- Translation Management (
Branding → Translations): centralized localization for:- Hosted Pages Display Text (login, registration, and related UI copy)
- Field labels on registration and profile forms
- Scope descriptions and other localized resources
Translation sets let different applications use different wording for the same locale. A layout points a Hosted Pages resource at a translation set; the application references that layout. Two apps can share one layout (same set) or use different layouts (different sets) while you edit strings in one place. At runtime, hosted pages resolve the assigned set and locale from CDN.
| Goal | How you configure it |
|---|---|
| Same look and same wording | Both apps use the same layout (and thus the same translation set) |
| Same look, different wording | Separate layouts, each pointing at a different translation set |
| Edit copy once | Change Hosted Pages Display Text in Translation Management; apps pick it up via their layout |
Learn more: Translation guide · Hosted pages management · Theming
SecureOps
SecureOps brings security operations into one place instead of scattered legacy menus.
Illustrative view of the Security Dashboard. Replace with a production Trustdesk screenshot when available.
- Security Dashboard: configuration issues and suspicious activity
- Verification Methods, Verification Options, and Suggest Verification
- Password Policies, Security Keys, and FDS Settings
Learn more: SecureOps mapping · Authentication methods · Password policy
Permission Setup: Group Verification Filter
Control who can log in and what appears in tokens at two levels.
- Per-app restriction: under Integrations → Applications, define group and role filters that run at login. Users who do not match cannot sign in; matched groups and roles can be embedded as hints in the JWT.
- Persistent rules: under Permission Setup → User Group Verification Filter, store reusable Group Verification Requests by ID for runtime verification APIs.
Benefits: smaller, application-specific tokens; login blocked when rules fail; optional runtime re-validation when permissions change.
Learn more: Groups and role restrictions
Agentic Chatbot
Trustdesk includes a built-in Agentic Chatbot, an AI assistant in the administration header that helps you navigate configuration, understand dependencies, and complete multi-step setup tasks.
- Guided navigation: find settings without browsing every menu
- Configuration guidance: understand how apps, scopes, hosted pages, and verification relate
- Operational troubleshooting: diagnose redirect URI mismatches, missing scopes, or webhook failures
- Same permissions: the chatbot inherits your session; it cannot elevate privileges
Responses from the Agentic Chatbot are AI-generated and may be incomplete or inaccurate. Verify critical configuration changes before applying them in production.
Learn more: Agentic Chatbot architecture
Workspace at a glance
Next steps
/admin-ui experience.Please contact us directly on our support page or reach out to cidaas support at [email protected].