How to Set Up Multiple Sites and Locations in ManageEngine ServiceDesk Plus?
Quick Summary
Organizations with more than one office often struggle to apply a single help desk configuration across time zones, holidays, and regional teams. ManageEngine ServiceDesk Plus – ITSM Software solves this with multi-site support, which lets administrators manage several branches from one installation while keeping each site’s settings independent. This guide explains what sites and regions are, how to create and configure them, how requests route across locations, and how to keep a growing site structure organized.
What Are Sites and Locations in ServiceDesk Plus and Why Do They Matter?
A site in ServiceDesk Plus represents a physical branch or office, complete with its own time zone, operational hours, holidays, and service level agreements. Rather than forcing every branch to share one global configuration, the platform allows each site to operate under settings that reflect its local reality.
Within ManageEngine ServiceDesk Plus – ITSM Software, this matters because a single organization can span multiple countries, each with different working hours, public holidays, and staffing structures. As a result, multi-site support allows a central IT team to govern the entire help desk from one hub while still delivering consistent, locally appropriate service to every office.
How Do Regions Relate to Sites?
A region groups related sites under a shared geography, such as EMEA or North America, which makes large deployments easier to organize and report on. Rather than managing dozens of individual sites as a flat list, administrators can nest them under regions, so reporting, administration, and delegated access can happen at either the site level or the broader regional level.
How Do You Access the Site and Region Configuration?
Reaching the site configuration screen requires administrator access, since site settings affect SLA calculations, ticket routing, and technician access across the entire deployment.
Where Is the Site Configuration Located?
First, log in with an account that holds SDAdmin privileges. Next, click the Admin tab in the header pane. From there, locate the Account Details or Helpdesk block and select Sites to open the site list view. Finally, click Add New Site to open the site creation form.
Regions are configured in a similar way: from the Admin tab, select Regions under the Account Details block, then click Add New Region. Because sites can be assigned to a region during or after creation, it is often easier to set up the region structure first, then create sites underneath it.
How Do You Create a New Site Step by Step?
Setting up a site involves entering a handful of core details, then layering on the settings that make the site behave independently from others in the same deployment.
What Fields Make Up a Site Configuration?
The site creation form asks for several pieces of information that together define how the site operates within the broader help desk.
| Setting | What It Controls | Example |
| Site Name | Identifies the site across menus, tickets, and reports | London Office |
| Region | Groups related sites under a shared branch or territory | EMEA |
| Time Zone | Aligns SLA timers and business hours to local time | GMT+0 |
| Address & Contact Info | Records the physical location and site contact details | 21 High Street, London |
| Site-Specific Settings | Applies local holidays, operational hours, SLAs, and business rules | UK bank holidays |
Once these fields are saved, the new site becomes selectable in the New Request form, and any technician or group associated with it gains the appropriate access.
How Do You Add a New Site?
Creating a site generally follows a short, repeatable sequence:
- Open the Sites configuration page from the Admin tab.
- Click Add New Site to open the site creation form.
- Enter the Site Name, which is a mandatory field, along with a brief description of the site’s purpose or activities.
- Select the region the site belongs to, along with its time zone, address, and contact information.
- Click Save to add the site to the list, or Save and Add New to continue creating additional sites.
After creating a site, administrators typically return to configure its holidays, operational hours, and SLAs. These settings determine how the system measures and escalates tickets from that site.
How Does Request Routing Work Across Multiple Sites?
When a requester submits a ticket, ServiceDesk Plus applies the site-specific settings that administrators configured for the request’s originating site instead of using one global configuration. For example, a request from a Sydney office follows Sydney’s operational hours and SLA rules, even if a technician based elsewhere handles the request.
Furthermore, the system filters the groups and technicians in the New Request form based on the selected site, keeping the assignment options relevant to that location. A technician’s ability to view or reassign requests from other sites depends on the viewing permissions configured for their account. Administrators can restrict access to the technician’s own site, extend it to associated sites, or allow access to all sites across the organization.
How Do Site-Level Settings Work Alongside Other Configuration Areas?
Sites rarely function in isolation. Several other configuration areas either inherit from or interact directly with site settings, which is what allows each branch to operate with its own rules while still belonging to a single ServiceDesk Plus instance.
| Configuration Area | How It Applies Per Site |
| Regions | Groups multiple sites under a shared geography for reporting and administration |
| Operational Hours & Holidays | Defines working hours and non-working days specific to each site’s calendar |
| SLAs and OLAs | Applies site-specific service levels, or inherits settings from a default base site |
| Technicians & Groups | Associates technicians and support groups with one or more sites for access and routing |
| Business Rules | Routes incoming requests based on the site from which they were raised |
For instance, administrators can configure an SLA for a specific site or set it to reference a designated default or base site. Any OLAs within that SLA automatically inherit the same site-level settings.
How Do You Associate Technicians With Specific Sites?
When adding or editing a technician, administrators can associate that technician with one or more sites and groups, which determines the access privileges the technician receives. This means administrators can link a technician who supports two regional offices to both sites, while restricting a technician who serves a single branch to that site. This keeps access aligned with each technician’s actual responsibilities.
What Are Common Scenarios for Multi-Site Configuration?
Seeing how organizations typically apply multi-site support can help administrators plan a structure that matches real operational needs rather than guessing at settings in isolation.
- A company with offices in London and Sydney configures separate time zones and holiday calendars for each site so SLA timers pause correctly outside local business hours.
- A regional retailer groups dozens of store locations under a single “North America” region, simplifying reporting without managing each site individually.
- A global enterprise sets one headquarters site as the default base for SLA policy, then overrides only the fields that differ, such as response time, for higher-cost regions.
- An organization with traveling field technicians associates those technicians with several sites at once, allowing them to pick up tickets wherever they are currently working.
In each scenario, the underlying goal is the same: apply a single, centrally managed ServiceDesk Plus instance while still respecting the operational differences that naturally exist between branches.
How Do You Edit or Delete an Existing Site or Region?
Site and region structures change as organizations open new offices, consolidate branches, or restructure regional operations. From the Sites or Regions list view, an Edit option reopens the configuration form, allowing the name, description, time zone, or associated settings to be updated without recreating the site from scratch.
Deleting a region requires particular caution, since removing a region also removes every site nested under it, along with attributes such as groups, SLAs, business rules, and holidays tied to those sites. Therefore, it is worth reassigning or backing up any dependent configuration before deleting a region that has been actively in use.
What Are Best Practices for Structuring Multiple Sites?
A few habits help keep a multi-site deployment manageable as an organization expands into new locations:
- Group sites into regions that reflect real administrative or geographic boundaries, rather than creating a flat, unorganized list.
- Configure holidays and operational hours for every site individually, since applying a single global calendar often produces inaccurate SLA measurements.
- Use a designated base site for shared SLA policies, then override only the settings that genuinely differ at other sites.
- Review technician-to-site associations periodically, especially after reorganizations, to avoid stale access permissions.
- Coordinate business rules with site-based routing so requests reliably reach the groups and technicians assigned to that location.
Applying these practices consistently generally leads to more accurate SLA reporting and a smoother experience for requesters at every location.
Conclusion
Multi-site support gives administrators a practical way to govern several offices from a single, centralized instance of ManageEngine ServiceDesk Plus – ITSM Software. From creating sites and regions to configuring time zones, holidays, SLAs, and technician access, the Admin tab provides everything needed to reflect how a distributed organization actually operates. Businesses that plan their site and region structure carefully typically see more accurate SLA tracking, cleaner reporting, and a more consistent support experience across every location.
How Can Solution for Guru Help With Your ServiceDesk Plus Multi-Site Setup?
Rolling out multi-site support effectively depends on understanding how an organization’s branches actually operate, not just entering names into a configuration form. Solution for Guru specializes in CRM and ITSM implementation, helping organizations design site and region structures, SLA hierarchies, and technician associations that mirror their real operational footprint. Whether a business is expanding into new locations or consolidating an existing multi-site deployment, an experienced implementation partner can help avoid misconfigured SLAs and routing gaps between offices.
Frequently Asked Questions
Yes, administrators can configure an SLA to reference a designated default or base site, which allows multiple sites to share the same service level policy. Individual sites can still be given their own SLA configuration where local requirements genuinely differ from the shared baseline.
Deleting a site can affect any open tickets, business rules, or reports tied to it, so those dependencies should be reviewed first. Deleting a region is even more significant, since it removes every site nested underneath it along with their groups, SLAs, business rules, and holidays.
Yes, a technician can be associated with multiple sites and groups at the same time. This is common for technicians who provide remote support across several branches, since it lets them view and work on requests from each associated site without needing separate accounts.
