1 ACCEPTED SOLUTION
Hi @ChrisGetint,
these aren't ACLs, they are in "Access control" in your instance.
And they would be in a format:
- table.none
- giving access to the whole table
- table.field1
- access to the particular field 1
- table.field2
- access to the particular field 2
- table.field3
- access to the particular field 3
- table.*
- access to all the fields that is not explicitly define
- all the table field except of 1, 2, and 3
Beside that you define the operations - read, write, create, delete.
And with all this you can set the access who can read (view) what fields. for example Number will be visible by everybody but a field Salary would be restricted to a group or role...
To update or create ACL records you need security admin role, the highest role existing.
The tables you mentioned are not granting access:
- Dictionary Entry [sys_dictionary]
- definition and attributes of form fields
- e.g. field Assigned to - defined as reference, Number as integer, etc.
- Field class [sys_glide_object]
- definition of fields - string, integer, ...
- Choice [sys_choice]
- all the choices in the platform
- e.g. State > New, Closed, etc
- State for Inc, states for change, ... as they can vary
- Journal Entry [sys_journal_field]
- stores Additional comments and Work notes
- e.g. from an incident, from a change, all...
For all the tables above add .list and you can do inspection to observe and understand what they store:
- sys_glide_object.list
- sys_dictionary.list
- etc
