Describe your environment
Share your hosting, network and identity constraints.
DEPLOYMENT · TENANT INSTALLED
Your environment.
Your deployment plan.
For organisations that need a deployment in their own environment, Field Serve can scope hosting, identity, integration and operational requirements with you.
Deployment discovery · Technical scoping · Field Serve
DEPLOYMENT AT WORK
Start with requirements, then agree the design
A tenant-installed deployment needs a clear technical and operational scope. The right approach depends on your environment, identity requirements, data handling, integrations and who will manage updates and support.
Map the required features
Confirm users, CRM modules, field service workflows and integrations.
Agree operating responsibilities
Define update, backup, security and support ownership.
Plan implementation and validation
Set out installation, testing and acceptance steps before rollout.
TECHNICAL DISCOVERY BEFORE A QUOTE
Scope the environment and operating responsibility together.
A tenant-installed deployment is a separate project. The right design depends on your infrastructure, identity, integrations, recovery objectives and who will operate the service.
Hosting and network
Document the target environment, supported operating system or container platform, outbound access, DNS, TLS termination, expected users, storage growth and any restrictions on external connections. Identify who monitors capacity and availability.
Identity and access
Decide how users authenticate, who provisions accounts, how MFA and recovery work, how the four platform roles are assigned, and what happens to sessions and records when someone leaves.
Data and integrations
Identify database ownership, encryption expectations, backup destination, retention, restore testing, migration scope and any mail or collaboration provider permissions. Keep secrets out of source archives and ordinary support email.
Service ownership
Agree who applies updates, monitors logs, manages certificates, responds to incidents, tests backups and supports end users. Define the change window and escalation path before go-live.
WHAT A DEPLOYMENT PLAN SHOULD CONTAIN
Turn assumptions into acceptance criteria.
A proposal should state the environment diagram, software components, version strategy, identity design, data migration boundaries, integration dependencies, recovery approach, security responsibilities, testing stages and support model. It should distinguish what Field Serve operates from what your IT team operates.
Plan a proof stage with representative test accounts and sample records. Verify sign-in, role restrictions, tenant boundaries, backups and restore, mail or provider connections, engineer mobile use and customer-facing links. Record who approves each test and what counts as a pass before production data is loaded.
Security and privacy are part of the scope
Confirm where data resides, who can access it, how access is logged, which subprocessors are involved and how incidents are handled. If the deployment processes personal data, document controller/processor responsibilities and applicable data-processing terms.
TENANT-INSTALLED QUESTIONS
Agree operations before installation.
Is tenant-installed the same as Field Serve Cloud?
No. Field Serve Cloud is accessed in a browser on Field Serve-managed infrastructure. Tenant-installed places the deployment in a separately scoped customer environment and needs its own technical and support agreement.
Can you quote from a hosting screenshot?
A screenshot is not enough to confirm capacity, network, identity, backup or security requirements. Onboarding should collect a technical discovery checklist and agree responsibilities with your infrastructure owner.
Who handles upgrades and backups?
Those duties must be explicitly assigned in the proposal or support agreement. Do not assume they are included until the operating model and service scope are documented.