---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Onboard using workspace

# Onboard to DevOps Change Velocity using Workspace {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read  
After installing DevOps Change Velocity, you can integrate with your DevOps toolchain and automate change requests directly from the DevOps Change
Workspace.
You can onboard as a DevOps admin, a tool owner, or an app owner.

## Onboard as DevOps admin {#onboarding-using-devops-change-workspace__section_npq_d1k_wyb}

Role required: sn_devops.admin.  
1. From the Home page, from the Get started with DevOps Change Velocity guide, select Connect a tool.

   Note:  
   To automate change requests for pipelines, connect your orchestration tool.
2. Using the connect playbook activity, connect to your DevOps tools.

   For more information about connecting to a tool, see [Integrating DevOps Change Velocity with third party tools](https://servicenow-prod.fluidtopics.net/pViQYW50q3XmI0CgMeO7rA "Integrate your orchestration, planning, coding, artifact, software quality, and security tools with DevOps Change Velocity for end to end change traceability and automation.").
3. Select Create an application to create an application and associate objects to it.

   For more information about creating an application, see [Create an application - Workspace](https://servicenow-prod.fluidtopics.net/0Q3U7QvoyazFAJLrEFh1bg "Create applications using the DevOps Change Workspace and associate pipelines, plans, and repositories to it.").

4. To automate change requests for pipelines, connect your orchestration tool and associate the pipelines with your application.For more information on associating pipelines, see [Associate tool objects to applications - Workspace](https://servicenow-prod.fluidtopics.net/d~RLHHIdnkfXhP1np3FsoQ "After creating an application, you can associate plans, repositories, and pipelines with it. Applications group plans, repositories, and pipelines from DevOps tools, which provides traceability to user stories, commits, test results, and so on.").

5. Select Automate change to create an automated change request.

   For more information about creating automated change requests, see [Automate DevOps change request creation](https://servicenow-prod.fluidtopics.net/Pw_QtOjaK96KhuVzwFBcSQ "Modify your pipeline to automatically create a DevOps change request.").

6. Modify your orchestration pipeline to enable change control. You can run the pipeline to verify that change requests are automatically created.

{#onboarding-using-devops-change-workspace__ol_ux4_p1k_wyb}

The getting started guide will be marked as complete when the first automated change request is created by the orchestration pipeline.

## Onboard as a tool owner {#onboarding-using-devops-change-workspace__section_jb2_wvw_wyb}

Role required: sn_devops.tool_owner.  
1. From the Home page, from the Get started with DevOps Change Velocity guide, select Connect a tool.

   Note:  
   To automate change requests for pipelines, connect your orchestration tool.
2. Using the connect playbook activity, connect to your DevOps tools.

   For more information about connecting to a tool, see [Integrating DevOps Change Velocity with third party tools](https://servicenow-prod.fluidtopics.net/pViQYW50q3XmI0CgMeO7rA "Integrate your orchestration, planning, coding, artifact, software quality, and security tools with DevOps Change Velocity for end to end change traceability and automation.").
3. If an application hasn't been created, ask your DevOps admin or app owner to create an application and associate objects to it.

   For more information about creating an application, see [Create an application - Workspace](https://servicenow-prod.fluidtopics.net/0Q3U7QvoyazFAJLrEFh1bg "Create applications using the DevOps Change Workspace and associate pipelines, plans, and repositories to it.").

4. To automate change requests for pipelines, connect your orchestration tool and associate the pipelines with your application.For more information on associating pipelines, see [Associate tool objects to applications - Workspace](https://servicenow-prod.fluidtopics.net/d~RLHHIdnkfXhP1np3FsoQ "After creating an application, you can associate plans, repositories, and pipelines with it. Applications group plans, repositories, and pipelines from DevOps tools, which provides traceability to user stories, commits, test results, and so on.").

5. Select Automate change to create an automated change request.

   For more information about creating automated change requests, see [Automate DevOps change request creation](https://servicenow-prod.fluidtopics.net/Pw_QtOjaK96KhuVzwFBcSQ "Modify your pipeline to automatically create a DevOps change request.").

6. Modify your orchestration pipeline to enable change control. You can run the pipeline to verify that change requests are automatically created.

{#onboarding-using-devops-change-workspace__ol_kb2_wvw_wyb}

The getting started guide will be marked as complete when the first automated change request is created by the orchestration pipeline.

## Onboard as an app owner {#onboarding-using-devops-change-workspace__section_rpt_ssx_wyb}

Role required: sn_devops.app_owner.  
1. Ask your DevOps admin or tool owner to connect to your DevOps tools.

   Note:  
   To automate change requests for pipelines, connect your orchestration tool.
2. Select Create an application to create an application and associate objects to it.

   For more information about creating an application, see [Create an application - Workspace](https://servicenow-prod.fluidtopics.net/0Q3U7QvoyazFAJLrEFh1bg "Create applications using the DevOps Change Workspace and associate pipelines, plans, and repositories to it.").

3. To automate change requests for pipelines, ask your DevOps admin or tool owner to connect your orchestration tool.
4. Associate the pipelines for which you want to automate change requests with your application.For more information, see [Associate tool objects to applications - Workspace](https://servicenow-prod.fluidtopics.net/d~RLHHIdnkfXhP1np3FsoQ "After creating an application, you can associate plans, repositories, and pipelines with it. Applications group plans, repositories, and pipelines from DevOps tools, which provides traceability to user stories, commits, test results, and so on.").

5. Select Automate change to create an automated change request.

   For more information about creating automated change requests, see [Automate DevOps change request creation](https://servicenow-prod.fluidtopics.net/Pw_QtOjaK96KhuVzwFBcSQ "Modify your pipeline to automatically create a DevOps change request.").

6. Modify your orchestration pipeline to enable change control. You can run the pipeline to verify that change requests are automatically created.

{#onboarding-using-devops-change-workspace__ol_spt_ssx_wyb}

The getting started guide will be marked as complete when the first automated change request is created by the orchestration pipeline.

## Workspace widgets {#onboarding-using-devops-change-workspace__section_dgw_1bc_wyb}

Tools widget
:   The Tools widget gives an overview of your connected tools, with the following details:

    * Number of tools that are in the connected state. You can select the card to see the list of connected tools.
    * Number of tools that need attention. You can select the card to see the list of unconfigured tools.
    * Number of tools that are in disconnected state. You can select the card to see the list of disconnected tools.
    * Number of tools grouped by their capabilities. You can select a capability to see the list of tools created for that capability.
    * Number of tools grouped by their tool types. You can select an integration type to see the list of tools connections created for that particular tool type.
    * DevOps admins and tool owners can connect to a tool from the widget.
    {#onboarding-using-devops-change-workspace__ul_l3l_jwx_wyb}

Applications widget
:   The Applications widget gives an overview of your applications, with the following details:

    * Number of applications with at least one associated pipeline. You can select the card to see the list of apps with pipelines.
    * Number of without any pipelines. You can select the card to see the list of apps with no pipelines.
    * Number of work items, commits, and pipeline executions from all applications in the last 30 days. You can select the card to see the list of disconnected tools.
    * Number of tools grouped by their capabilities. You can select a capability to see the list of tools created for that capability.
    * Number of tools grouped by their tool types. You can select an integration type to see the list of tools connections created for that particular tool type.
    * DevOps admins and app owners have the option to create an application from the widget.
    {#onboarding-using-devops-change-workspace__ul_ldb_mgy_wyb}

Automated change requests widget
:   The Applications widget gives an overview of your applications, with the following details:

    * Number of change requests created in the last 30 days. You can select the card to see the list of change requests.
    * Number of change requests that are pending approval in the last 30 days.
    * Number of pipelines with change control enabled, but hasn't automatically created a change request.
    * Number of tools grouped by their capabilities. You can select a capability to see the list of tools created for that capability.
    * Number of tools grouped by their tool types. You can select an integration type to see the list of tools connections created for that particular tool type.
    {#onboarding-using-devops-change-workspace__ul_svc_mhy_wyb}