Configuring Team Development
concept australia Updated Sep 10, 2026 1 min read configuring-team-development.md
Configure Team Development for your instance.
Configuration overview
-
To enable parallel development on multiple non-production instances, administrators can set up the Team Development instance hierachy and grant access rights for developers.
-
Application developers can create an exclusion policy to prevent pushes or pulls to particular instances in the team development hierarchy.
-
Define other instances in the hierarchy as remote instances.
-
You can require a code review of all changes pushed to an instance.
-
An instance can have multiple peer instances but only one parent instance.
-
Set up an instance hierarchy that best supports your development life cycle.
46 lines · 2.3 KB
---
title: Configuring Team Development
description: Configure Team Development for your instance.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/application-development/team-development/configuring-team-development.html
release: australia
product: Team Development
classification: team-development
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Team Development, Planning your application, Classic app development, Building applications]
---
# Configuring Team Development
Configure Team Development for your instance.
## Configuration overview
1. [Access rights for developers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/team-development/r_GrantingAccessRightsToDevelopers.md)
To enable parallel development on multiple non-production instances, administrators can set up the Team Development instance hierachy and grant access rights for developers.
2. [Create an exclusion policy](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/team-development/t_CreateAnExclusionPolicy.md)
Application developers can create an exclusion policy to prevent pushes or pulls to particular instances in the team development hierarchy.
3. [Define a remote instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/team-development/t_DefineARemoteInstance.md)
Define other instances in the hierarchy as remote instances.
4. [Enable a code review](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/team-development/t_EnableCodeReview.md)
You can require a code review of all changes pushed to an instance.
5. [Select the parent instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/team-development/t_SelectTheParentInstance.md)
An instance can have multiple peer instances but only one parent instance.
6. [Set up an instance hierarchy](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/team-development/t_SetUpAnInstanceHierarchy.md)
Set up an instance hierarchy that best supports your development life cycle.
| title | Configuring Team Development |
| description | Configure Team Development for your instance. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/application-development/team-development/configuring-team-development.html |
| release | australia |
| product | Team Development |
| classification | team-development |
| topic_type | concept |
| last_updated | 2026-09-10 |
| reading_time_minutes | 1 |
| breadcrumb | Team DevelopmentPlanning your applicationClassic app developmentBuilding applications |