Choose the workspace
Confirm which company account should own the integration.
CONNECTED WORK · INTEGRATIONS
Bring the right tools
into the workflow.
Connect collaboration tools to the way your company works, with each organisation controlling its own connection and access.
Teams · Slack · Monday.com · Company-controlled access
CONNECTED WORK AT WORK
Integrations belong to each organisation
Field Serve is designed for company-by-company onboarding. An integration connection is configured for the relevant workspace and should be authorised and tested by that organisation’s administrator. Availability depends on the provider setup and consent required.
Authorise the provider
Sign in with the organisation’s authorised account and grant only the permissions needed.
Test the connection
Verify the intended workflow in a controlled company workspace.
Review access regularly
Keep ownership, permissions and connected accounts current.
A CONNECTION BELONGS TO A COMPANY
Keep identity, consent and data flow explicit.
An integration is not just a button. It is a company-authorised relationship between Field Serve and another provider, with named owners and a documented purpose.
Microsoft Teams
Use your organisation’s Microsoft identity and administrator-approved configuration where required. Agree which team or channel is in scope, what events should be shared and who can disconnect the relationship. Microsoft tenant consent is separate from a Field Serve user’s sign-in.
Slack
Connect an organisation-controlled Slack workspace, select the channels and notifications needed for work and avoid sending full customer records into a broad channel by default. A workspace owner should review the scope and audience.
Monday.com
Decide which project boards or work items need a relationship with Field Serve, what fields can be synchronised and which system is authoritative for each value. Test create, update, deletion and duplicate cases before regular use.
Mailbox connection
Email protocols and permissions need separate onboarding. Use a mailbox the company controls, protect credentials or app access, define sync scope and retention, and test sent mail, replies and disconnect behaviour.
A SAFER CONNECTION CHECKLIST
Know what crosses the boundary before enabling sync.
For each provider, write down the business purpose, company owner, authorised account, data requested, records that may leave Field Serve, destination, retention and revocation route. Grant only the permissions the tested workflow requires. Where a provider requires tenant-wide consent, explain that scope to the customer administrator before asking them to approve it.
Run acceptance checks in a test workspace: verify the correct company is connected, no other organisation’s records are visible, updates go to the intended channel or board, and revoked access stops new synchronisation. Keep a support contact and a process for rotating credentials if an owner leaves.
Company isolation remains the foundation
Each company must connect its own provider account. Never reuse one customer’s token or mailbox for another workspace, and do not grant broad Graph or provider permissions merely to make onboarding easier.
INTEGRATION QUESTIONS
Consent is a customer decision.
Can someone without Microsoft 365 still use Field Serve?
Yes. Field Serve sign-in is separate from optional Microsoft integrations. An organisation without an Entra tenant can use the platform with its supported account method; it cannot use tenant-specific Microsoft sync until it has the required Microsoft environment.
Does Field Serve gain access to every company’s data?
No. A provider connection is authorised by its owning company and must be stored and used in that company’s isolated workspace. Provider consent does not grant one Field Serve customer access to another customer’s records.
Are all integrations ready automatically?
No. Each provider has its own app registration, permissions, plan requirements and approval process. The exact features available depend on completed configuration and the customer’s consent.