Owners evaluating account access, customer data, deployment networks, and third-party integration risk.
Security and governance
WslinkDesk security design and deployment boundaries
WslinkDesk follows least-privilege access, backend-only secret storage, traceable critical actions, and visible failure states. The project includes role permissions, session and operation audit, controlled connection settings, and private deployment evaluation when delivery conditions allow.
This page describes current design and does not claim ISO 27001, SOC 2, or any certification not explicitly published. Final security also depends on the deployment environment, provider, account policy, and operations.
Identity, permission, and audit
Admin, operator, and read-only roles restrict access to read and mutation operations. Critical configuration changes create audit records, while customer-service access follows account, team, and conversation authorization.
Secrets and third-party connections
DingTalk webhook URLs, signing secrets, and similar credentials stay in backend configuration. The public site can read availability but cannot read credentials. Third-party requests use timeouts, response validation, and explicit failure states.
Deployment responsibility
For private deployment, the customer owns host, database, backup, TLS, outbound network, and administrator-account security. WslinkDesk owns software configuration and product security fixes within the delivery scope.
Frequently asked questions
Does online support expose the DingTalk robot URL?
No. The browser receives only enabled and available states; the webhook and signing secret remain in the license-center backend.
Is WslinkDesk SOC 2 or ISO 27001 certified?
This page makes no such certification claim. Procurement reviews should rely on the latest formally supplied compliance material.
Maintained by WslinkDesk Product Team · Updated 2026-08-13