---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Team Development roles

# Team Development roles {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

To use Team Development, developers must have admin access to their development
instance.

To allow pushes to the parent instance, a [remote instance
connection](https://servicenow-prod.fluidtopics.net/ILI2nKrR68L8crxazg0M3Q "For each instance, define other instances in the hierarchy as remote instances.") must be defined with a user account that has admin access to the parent
instance.

To limit developer access to the parent instance, see [Granting Access Rights to Developers](https://servicenow-prod.fluidtopics.net/JH_nKxzh4L__ZZu3SvogOw "To use Team Development, application developers must have a set of credentials for each instance in the Team Development hierarchy.").

To use code review features, users must have the teamdev_code_reviewer role. See [Code Review](https://servicenow-prod.fluidtopics.net/zFiUacUKVTbPQrGma_BwSg "Team Development administrators can require that pushes undergo code review before accepting pushes.").