# Same application.yml different access-groups

**URL:** <https://support.openanalytics.eu/t/same-application-yml-different-access-groups/2649>\
**Category:** ShinyProxy\
**Created:** [October 17, 2023, 2:40pm UTC](https://support.openanalytics.eu/t/same-application-yml-different-access-groups/2649 "2023-10-17T14:40:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kramerrs](https://support.openanalytics.eu/user_avatar/support.openanalytics.eu/kramerrs/32/793_2.png) [@kramerrs](https://support.openanalytics.eu/u/kramerrs)\
**Post date:** [October 17, 2023, 2:40pm UTC](https://support.openanalytics.eu/t/same-application-yml-different-access-groups/2649/1 "2023-10-17T14:40:44Z")

</div>

We have a development and production sever. Is there a way to restrict access on the development server so that users don’t inadvertently end up using the development server? In general I am trying to keep the application.yml and what not the same between the servers. Is it possible to set a top-level/default access-groups using an environment variable for example?

It isn’t clear from the documentation how to go about doing this(Using SAML with LDAP mapped roles) if that helps.