*** title: Version control for Postman collections and environments updated: 2025-03-24T00:00:00.000Z max-toc-depth: 2 ---------------- Postman provides version control for your API collections and environments so you can iteratively and collaboratively build your APIs in Postman. Learn how to fork a collection or environment, make updates to the fork, create a pull request, and merge your changes into the parent element. * You can fork collections and environments from a parent element. Forking enables you to contribute to an element without having Editor access to that element. Learn more about [forking Postman elements](/docs/collaborating-in-postman/using-version-control/forking-elements/). * Create a pull request when you're ready to merge changes you made in your forked element into the parent element. Learn more about [creating pull requests](/docs/collaborating-in-postman/using-version-control/creating-pull-requests/). * You can view the changes, comment, approve or decline the request, and merge the forked collection or environment into the parent element. Learn more about [reviewing pull requests](/docs/collaborating-in-postman/using-version-control/reviewing-pull-requests/). * Watch a pull request to receive in-app notifications when a team member modifies a pull request. Learn more about [watching pull requests](/docs/collaborating-in-postman/using-version-control/watching-pull-requests/). Version control for collections and environments is different from API versioning. For information on managing multiple versions of APIs in the Postman API Builder, see [Manage changes with Git in the Postman API Builder](/docs/design-apis/api-builder/versioning-an-api/overview/).