Extending Permissions to Item Properties
Has anyone successfully extended permissions to the item property level?
I need to configure property‑level permissions in Aras Innovator so that modification and visibility of specific properties on an ItemType are controlled by user identity, beyond the standard item‑level permission and lifecycle security.
This cannot be a purely UI/visual restriction (e.g., hiding fields via Forms or client‑side methods only). It must be enforced as a true permission/authorization control so that users cannot modify restricted properties using AML, REST, external integrations, or custom clients.
Example Situation:
Starting with 3 ‘Property Permission’ sets, one for Electrical, Software, and Mechanical
Each Permission Set has 4 identities, one for Mechanical Engineers, Electrical Engineers, Software Engineers, and Non-Engineers. The permissions allow all of the engineers to Discover / get, but only one engineering group can update, and non-engineers have no access.
Then modifying the 'Property' itemtype to have a lookup property to permissions
And creating an ItemType called ‘PropertyPermissionItemType’ with 3 properties 'owned' by the different engineering groups, linked to the previously created permissions
And the idea is that these property Level permissions would determine who could view and update these properties.
It seems like theres a basic structure for it, but what would have to be done to actually implement the permissions at this level?
