Let’s define your first connected workspace.
Start with a clear pilot brief: the company, the services and the people who will own them.
A useful first conversation.
Pilot access is coordinated with the Sanaddesk project owner. Prepare the details below to share through your existing contact channel.
- Company and expected employee count
- First services and responsible departments
- Branches, roles and approval requirements
A public sales email or booking channel has not been configured. This page does not submit or collect your information.
Keep the first scope clear.
Copy a short template, fill it in and share it with your Sanaddesk contact. Do not include passwords or confidential records.
Company: Employee count: Branches: First services: Responsible departments: Approval requirements: Pilot contact:
Good questions. Clear answers.
Is every service approval-based?+
No. Incidents such as email and network problems go directly to support. Services can instead use one or two configured approval stages before assignment and fulfillment.
What is available in the limited pilot?+
The pilot includes requests, the service catalog, approvals, company administration, finding-to-closure internal audit, assets and contracts/subscriptions. Availability follows enabled company modules and acceptance. Dedicated HR, government-license workflows, full audit planning and advanced analytics remain planned.
How do employees sign in?+
Use the workspace link provided by your company administrator and your company employee number. Sign-in happens on app.sanaddesk.com, separate from this marketing website.
Does the pilot mean development is complete?+
No. Readiness comes first. New modules are developed and tested separately, then released with data-preserving migrations and an appropriate rollback plan. The user guide follows the accepted release.