# DevOps Pipeline instance access
**URL:** https://discourse.nodered.org/t/devops-pipeline-instance-access/88235
**Category:** FlowFuse
**Created:** [24 May 2024 14:04 UTC](https://discourse.nodered.org/t/devops-pipeline-instance-access/88235 "2024-05-24T14:04:17Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@SynoUser-NL](https://discourse.nodered.org/u/SynoUser-NL)
#### Post date: [24 May 2024 14:04 UTC](https://discourse.nodered.org/t/devops-pipeline-instance-access/88235/1 "2024-05-24T14:04:17Z")
Hi,
FlowFuse now supports having a DevOps pipeline, where I can have (for example) 1 instance designated for Development, one for Testing, and one for Production.
Users who have access to the Production instance should not have access to the Test instance, nor should they have access to the Development instance.
All instances are in the same Application, and thus in the same FlowFuse Team.
How can I now differentiate in access between the different instances at the FlowFuse level?
Thanks,
DenW
---
### Author:  [@gdziuba](https://discourse.nodered.org/u/gdziuba)
#### Post date: [24 May 2024 16:57 UTC](https://discourse.nodered.org/t/devops-pipeline-instance-access/88235/2 "2024-05-24T16:57:36Z")
It sounds like you are looking for a more granular control of RBAC. For now, I would recommend looking at [Instance Protection Mode](https://flowfuse.com/changelog/2024/03/instance-protection-mode/) to see if that can help you out for now.
There is an [issue](https://github.com/FlowFuse/flowfuse/issues/3093) created for adding more granular RBAC.
Grey
---
### Author:  [@SynoUser-NL](https://discourse.nodered.org/u/SynoUser-NL)
#### Post date: [24 May 2024 18:35 UTC](https://discourse.nodered.org/t/devops-pipeline-instance-access/88235/3 "2024-05-24T18:35:25Z")
Thanks.
Instance Protection Mode would not work for us.
I'll add to the Github issue referring to this thread.