# Reveal secret vars only for non-fork Pull Requests **URL:** \ **Category:** Released\ **Created:** [March 17, 2020, 11:21am UTC](https://discuss.bitrise.io/t/reveal-secret-vars-only-for-non-fork-pull-requests/12276 "2020-03-17T11:21:00Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![gmaclennan](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/gmaclennan/32/2090_2.png) [@gmaclennan](https://discuss.bitrise.io/u/gmaclennan)\ **Post date:** [March 17, 2020, 11:21am UTC](https://discuss.bitrise.io/t/reveal-secret-vars-only-for-non-fork-pull-requests/12276/1 "2020-03-17T11:21:01Z")
## Description of the feature request Currently Secret Vars are either not available to any PR, or available to all PRs, including PRs from forked repos. Github Actions and Travis CI both allow access to secret vars from PRs from non-fork PRs. ## Use case / for what or how I would use it Making Secret Vars available to PRs from forked repos is a security risk, but making them available for internal PRs is very useful (creating signed test builds, adding comments to PRs, etc). ---
**Author:** ![koral](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/koral/32/357_2.png) [@koral](https://discuss.bitrise.io/u/koral)\ **Post date:** [March 17, 2020, 10:00pm UTC](https://discuss.bitrise.io/t/reveal-secret-vars-only-for-non-fork-pull-requests/12276/2 "2020-03-17T22:00:30Z")
It seems that you can currently achieve the same result in a little bit different way. On Bitrise If secret is available to PR builds and PR is from a fork then the build need to be manually approved. > **[Bitrise | SAML SSO and manual approve for PR builds landed on Bitrise](https://blog.bitrise.io/post/saml-sso-and-manual-approve-for-pr-builds-landed-on-bitrise)** > > We've introduced two new features: one to keep your secrets during PR builds, and one to enhance access control for Bitrise organization. Read the details.