# Adding a new scope for handling variables at folder level

**URL:** <https://community.postman.com/t/adding-a-new-scope-for-handling-variables-at-folder-level/59885>\
**Category:** Help Hub\
**Tags:** variables, collections\
**Created:** [April 12, 2024, 10:44am UTC](https://community.postman.com/t/adding-a-new-scope-for-handling-variables-at-folder-level/59885 "2024-04-12T10:44:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fernandolahoz](https://avatars.discourse-cdn.com/v4/letter/f/c37758/32.png) [@fernandolahoz](https://community.postman.com/u/fernandolahoz)\
**Post date:** [April 12, 2024, 10:44am UTC](https://community.postman.com/t/adding-a-new-scope-for-handling-variables-at-folder-level/59885/1 "2024-04-12T10:44:30Z")

</div>

Hello guys, I’m part of a team who is using big collections, using forks and Pull Requests to be able to do feature branching to test our APIs.

Our collections has been growing through the time and we are handling every request with variables to be able to modify it locally without affecting the whole team, resulting in a very big list of variables in the collection.

Is there any way to handle these variables at folder’s scope? I have read about doing it with a pre-request script but this solution doesn’t fit very well for us because we want to continue using the feature of having an initial value and a local value for every variable.

Is this feature planned for next Postman releases?

Thanks a lot!  
A big fan of Postman

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/system/32/29796_2.png) [@system](https://community.postman.com/u/system)\
**Post date:** [May 12, 2024, 10:44am UTC](https://community.postman.com/t/adding-a-new-scope-for-handling-variables-at-folder-level/59885/2 "2024-05-12T10:44:50Z")

</div>

Closed on May 12, 2024, 10:44am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.