Hi @vidbina,
Thanks for asking this here! 
Itâs possible to some extent, but not completely. The reason is: even if the developer doesnât have access to the Secrets on the Web UI, they can access it during the build, so they can e.g. echo it.
Itâs not possible to do it any other way, because if your build can access a Secret that means it have to be able to access the value and use it, and if you grant access to developers to modify the workflow they can modify it in a way that they can print/send/⌠the value.
This isnât just a âBitrise limitationâ, itâs simply not possible technically to grant access to a value, but donât grant access to someone who has access to the build configuration.
If all you want is that your developers donât have access to the Secrets directly, on the Web UI, then you can e.g. store the build configuration in the repository, what the developers can access, and donât grant Admin access to them on bitrise.io
With this they wonât be able to view/modify secrets on the Web UI, but they still can access it through builds.
If youâre interested in this solution, you can find the related docs (how to store the build config in the repo) on our DevCenter: Managing an app's bitrise.yml file - Bitrise Docs
If you have any questions just let us know!
Happy Building! 