# Doppler in Github Codespaces - change account from "workplace\_service\_account" to normal user

**URL:** <https://community.doppler.com/t/doppler-in-github-codespaces-change-account-from-workplace-service-account-to-normal-user/1556>\
**Category:** Need Help\
**Created:** [June 25, 2024, 12:02pm UTC](https://community.doppler.com/t/doppler-in-github-codespaces-change-account-from-workplace-service-account-to-normal-user/1556 "2024-06-25T12:02:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexbjorlig](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/alexbjorlig/32/441_2.png) [@alexbjorlig](https://community.doppler.com/u/alexbjorlig)\
**Post date:** [June 25, 2024, 12:02pm UTC](https://community.doppler.com/t/doppler-in-github-codespaces-change-account-from-workplace-service-account-to-normal-user/1556/1 "2024-06-25T12:02:53Z")

</div>

Hi there.

I’m using Doppler in Github Codespaces with great success, but I have a small question feature request.

Our current setup works like this. We have configured the `DOPPLER_TOKEN ` to a workplace\_service\_account key. This is great, because this means that when freelancers use the codespace they have access to test and local environment in Doppler, everything is fine.

Hoewever, when I as a “real” doppler user uses a github codespace and run `doppler login`, I can successfully log in. But after logging in, I’m still “authenticated” as “workplace\_service\_account” (and thus can’t access stage for example).

Can you help with this, or come with any tips? I’m using `v3.68.0`

---

<div class="post-metadata">

**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\
**Post date:** [June 25, 2024, 8:43pm UTC](https://community.doppler.com/t/doppler-in-github-codespaces-change-account-from-workplace-service-account-to-normal-user/1556/2 "2024-06-25T20:43:34Z")

</div>

Hi @alexbjorlig!

This is because having `DOPPLER_TOKEN` set in the environment takes precedence over the CLI token that’s set when you perform a `doppler login`. There are two things you could do in this scenario. Either:

- Run `unset DOPPLER_TOKEN` in your shell before you do a `doppler login`. That should get your shell session to use the CLI token.
- Run `doppler login` and then run `export DOPPLER_TOKEN=$(doppler configure get token --plain)`, which will reassign the `DOPPLER_TOKEN` environment variable to the new CLI token you got after performing a CLI login.

Ultimately, it might be easier to have a separate Service Account for your more privileged developers that has the additional access permissions and then set things up so their Codespaces get a token from that Service Account injected and then your freelancers get a token from the Service Account with fewer permissions injected (assuming this is possible with your setup!).

Regards,  
-Joel