DEPLOYMENT & CONTROL

GoDesk cloud
or your own servers.

Choose the modules, deployment and administrative structure that fit your organisation or service offering.

TWO DEPLOYMENT PATHS

Choose where your platform runs.

We agree the environment and responsibilities before rollout.

Cloud and self-hosted deployment: planning considerations
Consideration	GoDesk cloud	Self-hosted / on premise
Hosting	A managed GoDesk hosted service.	The platform in your own environment.
Best starting point	Teams wanting managed infrastructure.	Organisations with specific infrastructure or data-control requirements.
Updates & support	Hosted updates and backup, with agreed service scope.	Agree upgrade, backup and support responsibilities.
Voice & channels	Configure numbers, providers and business accounts.	Validate network, trunks, endpoints and channel access.
Branding & tenants	Scope tenant configuration and white-label requirements.	Scope customer or business-unit environments and central administration.

CONTROL ACROSS THE ORGANISATION

Define what each customer, subsidiary or business unit can access, along with the administration and reporting your central team needs.

Separate data, configuration, users and branding per tenant.

Assign responsibilities through granular roles and module access.

Fit operational records and work states to your business.

Review change history and scope central reporting against agreed measures.

A PRACTICAL ROLLOUT

Confirm modules, users, channels, access and the work you need to improve.

Configure the environment, train a pilot team and test your critical workflows.

Roll out with agreed acceptance criteria, support and reporting.

Capacity, availability, recovery, data location and retention form part of deployment design. A rollout schedule follows from the agreed scope.

YOUR NEXT CHAPTER

Tell us which GoDesk products you need, how many people will use them and whether you are buying for your business or offering services to customers.