10
Is there a way to limit which substatus values can be selected depending on the security role assigned to an individual. Role A might be able to pick one substatus value e.g. awaiting payment, and Role B can select the substatus value Paid. But Role A can't select Paid. Can this be done without coding? Any suggestions?
Thanks for the idea. I can understand how to use those concepts to restrict access to an entity or even a field on an entity. But I'll have to read up as I don't follow how they can be used to manage access to values in a field. If I am following what you are thinking, then I need to assign specific records in the substatus table to different BUs and then use read, append, and append to permissions so I am limiting for instance, a BU from seeing/appending a specific substatus record to a Work Order record
Also, Role B in this case is making a change to the substatus value via an integration - dual write from F&O.
I will give it a go.
Yes, it takes a bit of an understanding of security but, by using business units and BU level read, append, and append to permissions, you can achieve your goal.
Role A is in BU A, Role B is in BU B. Then make Awaiting Payment owned by someone in the BU A Business Unit and BU B owns the Paid substatus. In this way, they will not see the records not in their BU.
If there are some substatuses that are shared, use teams to add the users both to more than one BU.
If they share most records and only don’t share a few, I’d add them both to teams that belong to the respective BUs that you will use to give them access to the smaller set of specially privileged records.
If this was hard to follow, read more about security, business units, and teams.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (