ITSM / Deployments
Deployments
Push a catalog service to a targeted audience on a schedule, track who completed the form and which tickets were created, without emailing the whole company manually.
Real-world scenario
Maya Chen · IT Manager at Bluewave Labs
Security needs every engineer to re-attest VPN usage this quarter. Maya deploys the VPN Access Request service to the Engineering folder with reminders, instead of chasing 80 people in Slack.
Before you begin
- ITSM license enabled
- At least one published catalog service
- Employee folders or teams for audience targeting
Overview
ITSM deployments roll out a catalog service to a defined audience, departments, teams, workplaces, or all employees, for a time-bound campaign. Recipients get portal notifications; each submission creates a service ticket you can track alongside organic requests.
For example
Use cases
- Compliance attestations. Annual security or software policy acknowledgments
- Onboarding campaigns. New hire equipment selection or standard software bundle
- Department rollouts. Push a new Figma request form when Design hires spike
- Access reviews. VPN or privileged access reconfirmation by team
Deployment lifecycle
Deployments move through clear phases:
- Draft. Configure service, audience, and dates before anyone is notified
- Scheduled. Queued to start on a future date
- Active. Recipients see prompts in the portal; submissions create tickets
- Completed. End date passed; review completion rate and export status
Each phase shows recipient counts, completion rate, and linked service tickets on the deployment detail page.
Create a deployment
See How to Create a Deployment for the full walkthrough, select service, audience, dates, and notification channels.
DEX parallels
Related articles