# Single Option granularity Problem
**URL:** https://community.baserow.io/t/single-option-granularity-problem/12937
**Category:** Uncategorized
**Created:** [September 18, 2026, 7:34am UTC](https://community.baserow.io/t/single-option-granularity-problem/12937 "2026-09-18T07:34:31Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@linan](https://community.baserow.io/u/linan)
#### Post date: [September 18, 2026, 7:34am UTC](https://community.baserow.io/t/single-option-granularity-problem/12937/1 "2026-09-18T07:34:31Z")
I have one tickets table , that has status.
For example, there are 3 status, A,B,C.
And this tickets table, I have already few views, for RBAC purposes.
For Example, there are 3 nodes to approval. Node A → Node B - \> Node C.
For people in Node A, there is a View to see the protected data.(People in Node A)
For people in Node B, there is a View to see the protected data.(People in Node B)
But the requirement is that People in Node A can only change from Status A to Status B, not for example , Status A to Status C.
How should I do that?
Before I am thinking about build a view based on status table, but it not works. I can create Status table views with different purposes, but only applicable for one view , not serval views.
Thanks for the answer.
---
### Author:  [@olgatrykush](https://community.baserow.io/u/olgatrykush)
#### Post date: [September 30, 2026, 12:59pm UTC](https://community.baserow.io/t/single-option-granularity-problem/12937/2 "2026-09-30T12:59:38Z")
Hey! I think [restricted views](https://baserow.io/user-docs/view-level-permissions) can help with the visibility part, but they won’t fully enforce the approval flow.
For example, you can give Node A a view filtered to `Status = A`. They can edit the Status, but they could still change it from `A` directly to `C`. The ticket would simply disappear from their view after the change.