Hi @mark.fin ,
we have the same issue. What we need is a lock system for the Ftrack entities and attributes. Please have a look at this discussion http://forum.ftrack.com/index.php?/topic/788-lock-system-for-entity-attribute/ .
Until this is implemented, we are using an Ftrack action which works pretty nice for us.
How the action works:
- it listen for all the events
- ones an event match the conditions, we process it.
Example: we allow production to create an asset and update the name as long as the status is not changed. Ones the status is changed, we mark it (set a key in metadata). If the production renames it now, the action detects that the asset is marked and rename it back to the previous name and let the user know why he/she can't do it.