Self-service Action RBAC becomes less manageable when housing multiple scenarios/journeys in a single SSA. It becomes confusing for the Admin to mentally track context when establishing/reviewing the RBAC policy and how it applies to various scenarios within the SSA. When I say scenario, what I mean is a specific set of value(s) are selected in the SSA by the executing user, e.g. we may enact a different RBAC policy depending on a form field like environment (e.g. Int, Stage, Prod), or depending on the deployment type (Database, Standard), or even more complex where it's a matrix between both (or potentially even N number of dimensions/fields).

For example: In RBAC you can create your own "scenarios" this way, when field A = X, field B = Y, and field C = Z enact RBAC policy 1.