I have problem while creating ACL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Saturday
I have a table leave approval - which will keep records of a catalog - leave application approval. i want- people with hr role can edit fields "state" and "approval status" , rest fields should be read only. so i created these ACLs (mentioned in the image) but there is a user "Shumayla kaur", she has "hr" role. she is able to see list, write it. nd she is able to write or edit every field, except "Reason" field, and "Short Description" field. Even i have checked these fields are not 'Read only'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago - last edited 3 hours ago
Hi @MohdT4835709720,
Isn't there any parent table with ACL defined on top of the current table?
Also, check the ACL definition for wildcard it is the asterisk (*) which defines the rules for all the fields that are not defined.
Example:
your_table.approval_status
your_table.state
your_table.any_field
These three records gives CRUD permitions on these fields
your_table.*
manages access for ALL THE OTHER fields that are not explicitly defined.
If you want to understand this better, go to Access analyser, there oyu can select a table, a field, a record and a user to better understand how the ACLs were evaluated.
Let me know what you found
EDIT: added a screenshot below.
100 % GlideFather experience and 0 % generative AI
