ITSM / Deployments

How to Create a Deployment

Launch a time-bound campaign that pushes a service form to the right people, and tracks completion without spreadsheet chasing.

Real-world scenario

Maya Chen · IT Manager at Bluewave Labs

Forty new engineers start next month. Maya deploys External Monitor Request to the "June Cohort" folder so everyone selects a monitor before day one, tickets auto-create for procurement.

Before you begin

  • Published catalog service with a complete form
  • Audience defined via teams, workplaces, or employee folders

Overview

A deployment pushes an existing service request form to a defined audience for a limited time. Unlike organic portal submissions, you get recipient-level completion tracking and scheduled reminders, ideal for compliance and onboarding bursts.

Create a deployment

  1. 1

    Open Create Deployment

    In ITSM, go to Deployments and click Create. You'll pick which catalog service to roll out.

  2. 2

    Select the service

    Choose the published service, e.g. VPN Access Request or External Monitor Request.

  3. 3

    Define the audience

    All employees, specific teams, workplaces, or folder-based filters. Target Engineering only if that's the compliance scope.

  4. 4

    Set the schedule

    Start and end dates, plus optional reminder cadence before the deadline.

  5. 5

    Configure notifications

    Email and in-app alerts for launch day and reminders. Sophie sees a portal banner when she logs in.

  6. 6

    Review and publish

    Confirm recipient count and dates, then publish. Recipients can complete the form from portal notifications.

Example campaign

Q2 VPN Re-Attestation

  • Service: VPN Access Request
  • Audience: Engineering team + Design team (142 recipients)
  • Start: Jun 1 · End: Jun 21
  • Reminders: In-app + email on Jun 7 and Jun 14
  • Goal: 100% completion for security audit evidence

After launch

Track progress on the deployment detail page, completion percentage, not-started list, and linked tickets. Export recipient status for audit evidence. Open Service Requests to fulfill tickets created from submissions; filter by deployment to separate campaign volume from day-to-day Sophie requests.

Expect a dashboard spike while the campaign is active. Correlate with ITSM Dashboard filters and run Sentiment Analysis on textarea answers if the form collects feedback.

Service must be published

You can only deploy published services with a valid form. Finish service setup before scheduling a campaign.

Related articles