Documentation forSolarWinds Service Desk

Before you begin

On this page


Before you begin setup of your SolarWinds Service Desk (SWSD) account, ask yourself: How can the SolarWinds Service Desk improve service management throughout my organization?

These quick facts might help you answer that question:

  • Incident management consolidates, manages, and prioritizes incoming tickets. It also highlights areas that need improvement to run more efficiently.
  • Service catalog standardizes service request and fulfillment processes.
  • Fully integrated IT asset management compiles hardware, software, POs, and other assets.
  • The IT service desk can quickly restore the end user to productivity by:
    • Using problem resolution
    • Providing end-user education
    • Generating workarounds

Factors to consider

SWSD and its AI tools can help to quickly restore end users back to productivity. This can be accomplished via numerous features, for example, by:

  • Providing a user-friendly service portal where end users can:
    • Open incidents
    • Open service requests
    • Find knowledge base articles and frequently asked questions
  • Setting up automations to ensure prompt ticket handling

  • Setting up workflow processes to streamline actions

To maximize efficiency of services, you need to clearly understand the end-user experience so SWSD can meet their technological needs. This is best accomplished by:

  • Tracking tickets
  • Identifying recurring issues
  • Maintaining services so they are up to date with current technologies

The above items all factor into assuring:

  • Smooth continuity of services
  • A service portal for users to have a single place to submit tickets and requests

Plan a setup that will meet your organization's needs

Before you begin your setup you should consider your organization.

  • What is the basic setup of the organization?
  • How can you best manage all of your ITAM and ITSM needs to meet organizational goals?
  • Do you need a high level of confidentiality between your departments? For example, can IT access HR data?

Based on the answers to these questions and other organizational factors, you may decide to use a single tenant account for ITSM, or use an ESM (Enterprise Service Management) account that allows them to keep departments separate from one another.

Single-tenant (ITSM) customers

Customers can use our single-tenant architecture, which supports only one tenant per instance. In relation to SWSD, your organization would be the single tenant: most often the IT department. They can use ticketing categories and subcategories in addition to special roles and permissions specifically created for each department, but managed by IT.

Enterprise Service Management (ESM) customers

Some organizations choose to use a multi-tenancy setup. They have a single SWSD account, but can set up resources for multiple service providers (sub-tenants), for example, HR, and Facilities. Underlying resources are shared among all the tenants, but each tenant is guaranteed privacy and certain configurational customizations. See Enterprise Service Management (ESM).

Because HR requires a high level of confidentiality, setting HR up as a service provider would prohibit IT staff from accessing any of the HR related service records. Your HR account administrator for the HR service desk account can be a member of the HR team rather than the IT team. This approach can prevent IT from accessing unauthorized data.

Understand the setup process

The Getting Started Setup order guide provides you with the best order for your initial setup of SWSD. The Administrator setup guide leads administrators through the initial setup and configuration process. It provides documentation on how to configure each setup feature. It also provides information on the order in which to perform setup, so that you configure your foundational building blocks first, then move on to your structures and workflows to align your SWSD setup with your organization's needs.

Foundational building blocks

Your foundational building blocks include configuration of some default settings, such as default time zone, default language, setup of your sites and departments, and your service desk's default business hours.

After establishing those settings, you set up your user accounts, groups within your organization, queues for managing the work of the service desk, roles and permissions for your users, and establish your single sign-on method.

By establishing these building blocks before moving forward you provide assurance that your instance of SWSD is well aligned with your organizational needs.

Structure and workflows

After the foundation of your SWSD account is built, you can add structure and flow. This includes setup of the service desk's email settings, categories for tickets, and custom states. It also includes custom forms, custom fields, domain management, setup of your CMDB, service portal, automations, and integrations. Lastly, it includes asset discovery.

See the Administrator setup guide for more guidance.

Related topics