Even though attributes (examples: 'Open for Time Entry' or 'Active') are on secured subpages, the fields are still editable from the list page. The expectation is that the secured sub-page should prevent users from updating this field while still being able to edit other fields.
Steps to Reproduce (using example of Open for Time Entry field on Resource list view)
Expected Result: The 'Open for Time Entry' shouldn't be editable
Actual Result: The 'Open for Time Entry' is editable
This issue was reviewed as DE39961 by Product Management and it is determined to be working as designed.
Release: All Supported
Component: Clarity Studio