# How to not sync Tokens in Oauth2

**URL:** <https://community.postman.com/t/how-to-not-sync-tokens-in-oauth2/6245>\
**Category:** Help Hub\
**Created:** [July 2, 2019, 12:46pm UTC](https://community.postman.com/t/how-to-not-sync-tokens-in-oauth2/6245 "2019-07-02T12:46:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![it1](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@it1](https://community.postman.com/u/it1)\
**Post date:** [July 2, 2019, 12:46pm UTC](https://community.postman.com/t/how-to-not-sync-tokens-in-oauth2/6245/1 "2019-07-02T12:46:19Z")

</div>

Hello we are developing using POSTMAN, which is great by the way.

Our devel environment is in local through Docker Containers, every developer has its own instance.

So, once we sync, the team gets the same token and this only works for 1 person.

¿Is there ny way to not to sync Auth tokens?

---

<div class="post-metadata">

**Author:** ![postman-paul540](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/postman-paul540/32/149_2.png) [@postman-paul540](https://community.postman.com/u/postman-paul540)\
**Post date:** [July 2, 2019, 1:09pm UTC](https://community.postman.com/t/how-to-not-sync-tokens-in-oauth2/6245/2 "2019-07-02T13:09:17Z")

</div>

I believe this has been answered:

> [@Ability to keep variables 'private'](https://community.postman.com/t/ability-to-keep-variables-private/2550):
>
> When using shared collections with teams, the environment variables that one person creates get shared out to everyone. This can be useful in 2 scenarios: In case of sensitive data, like internal URLs In case of dev instances of the same application. When dev teams are using the same collection to test their own individual endpoints, environments get really cluttered. This feature may also partially solve the need for a private/onsite instance, see feature request on github by another user [ht…](https://github.com/postmanlabs/postman-app-support/issues/5020)

TL;DR - Only values that are set as “Initial Value” for an environment are synced with your team members. The “current values” for an environment are private.

Here’s an example of my environment that is used across the company, I’ve deleted other sensitive data from the screenshot for obvious reasons 😛

 ![image](https://us1.discourse-cdn.com/getpostman/original/3X/f/b/fb85396aa2528ac77f09fcddb73330d463d3131e.png)

So when a user that is part of the workspace selects this environment, they will not have the “auth-token: 9847583475ugjhghuirtoigh895h” env variable.

---

<div class="post-metadata">

**Author:** ![jetison](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/jetison/32/12_2.png) [@jetison](https://community.postman.com/u/jetison)\
**Post date:** [July 2, 2019, 9:52pm UTC](https://community.postman.com/t/how-to-not-sync-tokens-in-oauth2/6245/3 "2019-07-02T21:52:05Z")

</div>