Restrict access to decision tables with the role Decision rule author

Flavio4
Kilo Sage

Hello,

How is it possible to restrict access to decision tables with the role "Decision rule author"?

I guess that a way is by Application.

Are there any ways to do it in the Global application?

Thanks
Flavio

4 REPLIES 4

Arpan Baishya
Kilo Sage

Hi @Flavio4,

 

By default, for the decision table [sys_decision], read access is provided to the following roles - 

 

itil

decision_table_reader

decision_table_admin

change_manager

sn_change_read

 

As far as create, write, and delete access is concerned, a user needs the decision_table_admin role in order to perform any of those operations.

 

Hope that answered your query.

Thank you Arpan.
What I need is to limit the access to one (or few) decision table for a user who has the decision_table_admin role (or Decision rule author role should be enough, perhaps?).

Can I achieve this with ACL? If yes, how?

Flavio
 

Hi @Flavio4,

 

If you wish to restrict a user having the decision_rule_author role to access only a few Decision Table records, you may create a new ACL. Under the Role section, you can provide the role name and then under the Data Condition, you can build a condition that looks like this.

ArpanBaishya_0-1718653656530.png


By providing a list of decision tables, the user with the decision_rule_author role would be able to access only those. However, any user with the decision_table_admin role would be able to access any decision table record due to the OOB ACL rules.



Thank you Arpan!

I tested what you propose and indeed it works as far as editing is concern.
Unfortunately there is an issue I had not realized: the user allowed to edit only one decision table, can actually see (read only) all other decisions tables (content included), which is not very favorable to data privacy.

Do you know any ways to limit also the read rights for uses on any decision tables but the one(s) for which the ACL provides edit rights?

If we manage to do this, it will be awesome and issue is solved.