You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are instances when we require establishing a unique ROLE assigned solely to a single customer. For instance, consider creating a ROLE named "Domain_1_Location_supervisor."
Our objective is to prevent this role from appearing in any other domain, primarily due to the following reasons:
Each domain might already feature a multitude of other ROLES.
To ensure that when a customer accesses their specific domain, such as "Domain_2," they do not encounter a role unrelated to their domain, like "Domain_1."
I'm seeking guidance on whether achieving this within Casbin is feasible, as I've encountered challenges in deciphering the approach to achieve this goal.
The text was updated successfully, but these errors were encountered:
There are instances when we require establishing a unique ROLE assigned solely to a single customer. For instance, consider creating a ROLE named "Domain_1_Location_supervisor."
Our objective is to prevent this role from appearing in any other domain, primarily due to the following reasons:
I'm seeking guidance on whether achieving this within Casbin is feasible, as I've encountered challenges in deciphering the approach to achieve this goal.
The text was updated successfully, but these errors were encountered: