---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Create an application - Classic

# Create an application - Classic {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Create applications using the Classic UI or the Service Catalog.

## Before you begin

Role required: sn_devops.admin or sn_devops.app_owner

## Procedure

1. You can create applications using the Classic UI, or the Service Catalog.  
   * Classic UI: Navigate to AllDevOpsApps \& PipelinesCreate App (legacy).
   * Service Catalog: Navigate to AllService CatalogCatalog DefinitionsMaintatin ItemsCreate DevOps ApplicationTry It.
   {#app-create-all__ul_ehm_l1g_wwb}
2. On the Create DevOps Application form, choose whether to create a new application and new application model or to base the application on an existing application model.

   | Choice | Actions |
   | New application | Enter a name for the new application. * The system generates a new DevOps application, a new application model, and a new SDLC component (SDLC-C) in the CMDB. * The SDLC-C is assigned the same name as the new application. * If the DevOps Config application is installed, then DevOps associates the application to the CDM application. {#app-create-all__ul_y2y_5zc_ftb} |
   | Existing application model | Select the application model from the list. The system generates a new DevOps application from that application model. * The application is given the same name as the application model. * If an SDLC component exists for the application model, then DevOps associates the SDLC-C to the new application. * If an SDLC component doesn't exist for the application model, then DevOps generates a new SDLC-C with the same name as the application model. * If DevOps Config is installed, then DevOps creates a CDM application and associates the SDLC-C to the application. {#app-create-all__ul_ivg_dzc_ftb} |
   |-|-|

   {#app-create-all__choicetable_ddn_pxv_2tb}
3. Select Submit.

## What to do next

You can view the list of all the applications from the Apps page in the Classic UI. Navigate to AllDevOpsApps \& PipelinesApps and select your application.  
For each application, you can:

* Update details such as  Business app, State (Active), and  Log Level. Applications marked as Active are polled daily for updates to associated plans, repositories, and pipelines.
* Control access to the application by adding user groups to the Maintained by field. You can select any group that has at least one user with DevOps roles.  
  When user groups are added:
  * Users with DevOps App Owner role or DevOps Administrator role can edit and associate objects with the application.
  * Users having other DevOps roles can view the application.
  * Users having DevOps roles, but aren't part of the groups added can't view the application.
  {#app-create-all__ul_qnp_fkx_5wb}  
  Note:  
  DevOps admins can always see and edit everything in DevOps.
* View and associate plans, repositories, pipelines, and artifact repositories. Associate the appropriate tool objects to the application to ensure that all the DevOps data is grouped and tracked. For more information, see [Associate tool objects to applications -- Classic](https://www.servicenow.com/docs/k~ggIJs3~p1L0R7TAC2pJw "After creating an application, you can associate plans, repositories, pipelines, and artifacts with it.").
* Delete the application record.
{#app-create-all__ul_ib1_bvl_cvb}

*[\>]: and then