---
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 JFrog using Workspace

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

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Connect to your JFrog instance using the DevOps Change Workspace playbook to track artifact repositories published to JFrog.

## Before you begin

Complete the tasks specified in the [Getting started with DevOps Change Velocity](https://servicenow-prod.fluidtopics.net/zYfXM71OMizgQDlC6XiIiA "Learn about the setup process for DevOps Change Velocity that is required before configuring integrations with your toolchain.") topic.

Install the JFrog plugin (x_snc_jfrog) from the ServiceNow® Store to enable bearer token authentication and integration with JFrog AppTrust application. For more information, see [Integration with JFrog AppTrust application](https://servicenow-prod.fluidtopics.net/TqpBVE5dcEpNgjhrFmKhTw "Integrate DevOps Change Velocity with JFrog AppTrust applications to automate change request creation, approval, and evidence collection as application versions are promoted through life-cycle stages.").

Role required: sn_devops.admin or sn_devops.tool_owner

## Procedure

1. Navigate to WorkspacesDevOps Change Workspace and use one of the following options to open the Playbook to onboard JFrog.

   | Option | Steps |
   | Homepage | 1. Select the Connect tool widget 2. On the  Connect to a tool  modal, select JFrog from the Artifact category. {#devops-jfrog-connect-workspace__ol_e5j_4y1_fwb} |
   | Applications module | 1. Select Applications (![Applications icon.]()). 2. Select an existing application, or create one. To create an application, see [Create an application - Classic](https://servicenow-prod.fluidtopics.net/oMhI9exh6yQ3ocq8_41FzQ "Create applications using the Classic UI or the Service Catalog."). 3. From the  Recommended actions  pane, select the  Connect a tool  card. 4. On the  Connect to a tool  modal, select JFrog from the Artifact category. {#devops-jfrog-connect-workspace__ol_u24_mz1_fwb} |
   | Tools module | 1. Select Tools (![Tools icon.]()). 2. From the Capability list, select Artifact. 3. Select Connect a tool. 4. On the  Connect to a tool  modal, select JFrog. {#devops-jfrog-connect-workspace__ol_fjs_k1b_fwb} |
   |-|-|

   {#devops-jfrog-connect-workspace__choicetable_m3t_ky1_fwb}
2. Specify a name for the tool in the Tool name field, and select Next.  
3. On the JFrog instance details playbook activity:
   1. Enter the URL of your JFrog instance.
   2. Select the credentials type as Basic Auth or Bearer Token.
   3. Based on the credential type, do one of the following:  
      * For Basic Auth, select the login credentials of the primary user.
      * For Bearer Token, select the bearer token associated with the project.  
        Note:  
        Bearer token can be generated from the AppTrust Integrations page of your JFrog tool. For more information, see [Integration with JFrog AppTrust application](https://servicenow-prod.fluidtopics.net/TqpBVE5dcEpNgjhrFmKhTw "Integrate DevOps Change Velocity with JFrog AppTrust applications to automate change request creation, approval, and evidence collection as application versions are promoted through life-cycle stages.").
      {#devops-jfrog-connect-workspace__ul_b43_lsw_f3c}
   4. **Optional:** Select the MID Server option and enter its details if your JFrog instance is attached to a MID Server.  
      A MID server is required if your tool instance is hosted on-prem. For more information about MID server, see [MID Server selection](https://www.servicenow.com/docs/access?context=c_MIDServerSelector&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US).

   {#devops-jfrog-connect-workspace__substeps_lfr_qqz_2wb}  
4. Select Connect.
5. Permission checks are run based on the credential type and credentials that you entered.  
   Permissions required and permissions that are available are displayed. If you want to enter credentials with better permissions, select Re-enter credentials. The credentials that you specified must have the Administer Platform role in JFrog for seamless discovery and import of tool objects. This is a limitation from JFrog. For detailed information on all the required permissions, see Jira permissions in [Permissions required for DevOps tools](https://servicenow-prod.fluidtopics.net/rkQZOOxQSNdDZ7d5eHch0A "Permissions required in your third-party tool to connect to DevOps Change Velocity.").  
   You can choose to continue with the tool connection even if you don't have all the required permissions.  
   Note:  
   If your tool credential has changed, you must update the credentials in your ServiceNow instance. For more information, see [Update third-party tool credentials in DevOps Change Velocity](https://servicenow-prod.fluidtopics.net/W3H0I3eiOCLVglPK635qzA "If your tool credential has changed, you must update the credentials in your ServiceNow instance to avoid getting disconnected.").

6. Select Next.
7. Specify the access for the tool.  
   1. If you want to control access to the tool, add the groups that must be given access to the tool in the Maintained by field.  
      The tasks these users in the groups can perform depends on the role assigned to them.
      * DevOps Tool Owner role: Can view and edit the tool.
      * DevOps App Owner role: Can view the tool and can associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects (such as plans, repositories, and pipelines).
      * DevOps Administrator role: Can edit all tools.
      * Other DevOps roles: Can view the tool.
      {#devops-jfrog-connect-workspace__ul_csp_h5c_xwb}  
      Note:  
      If you don't select a group and skip this step, all users with the DevOps Tool Owner role will be able to edit the tool.
   2. If you choose to control access to the tool, the All App Owners can view and associate tool objects to applications option becomes available for selection.

      This option enables all users having
      the DevOps App Owner role to access the tool. If selected, they'll be able to view, associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects.
   3. Select Assign.
   {#devops-jfrog-connect-workspace__ol_slg_2tz_cxb}
8. From the Summary page, select View tool record to review the details of the connected instance.

## Result

You've successfully onboarded your JFrog tool to DevOps Change Velocity.

*[\>]: and then