# \[Editor\] Staging and Production credentials handling

**URL:** <https://community.weweb.io/t/editor-staging-and-production-credentials-handling/7317>\
**Category:** Ask us anything\
**Created:** [February 28, 2024, 11:08am UTC](https://community.weweb.io/t/editor-staging-and-production-credentials-handling/7317 "2024-02-28T11:08:28Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Alexis](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/alexis/32/13248_2.png) [@Alexis](https://community.weweb.io/u/Alexis)\
**Post date:** [February 28, 2024, 1:31pm UTC](https://community.weweb.io/t/editor-staging-and-production-credentials-handling/7317/6 "2024-02-28T13:31:57Z")

</div>

Not yet. We could make it bindable but I think it’s part of a larger discussion we have around environment variables.

I dont want to make it bindable because it could prevent us to change the way it work, if we want to introduce a new kind of secure field to manage credentials.

I know it’s a blocker in the meantime as there is now way to configure a different URL and public key by environment so it should be prioritised asap imo, I will discuss it with the product team 🙂

Edit : Actually, we cant make it bindable because we need them also in the backend when checking the page access, and formula can be evaluated only in the frontend, so we will have to release this new feature to allow such use case (different instance per environment)

---

_[View the full topic](https://community.weweb.io/t/editor-staging-and-production-credentials-handling/7317)._