You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we have to add write permissions to all users for AYON id and AYON path custom attributes in ftrack so they can integrate versions with related AYON id. That is not idea and we probably should find a better approach how to achieve it.
Suggestes approach
It is possible that won't have to handle this if we will make ftrack service that will sync reviewables from AYON to ftrack. In that case it will be handled by service where should be used API user.
If that would not solve the issue, we might need to trigger special AYON event that would contain ftrack id and AYON id of version so a service would set the id and path in ftrack custom attributes?
The text was updated successfully, but these errors were encountered:
iLLiCiTiT
changed the title
Stricter permissions to write to AYON id and AYON path attribute
Stricter permissions to write to AYON id and AYON path attributes
Jul 22, 2024
Description
Right now we have to add write permissions to all users for AYON id and AYON path custom attributes in ftrack so they can integrate versions with related AYON id. That is not idea and we probably should find a better approach how to achieve it.
Suggestes approach
It is possible that won't have to handle this if we will make ftrack service that will sync reviewables from AYON to ftrack. In that case it will be handled by service where should be used API user.
If that would not solve the issue, we might need to trigger special AYON event that would contain ftrack id and AYON id of version so a service would set the id and path in ftrack custom attributes?
The text was updated successfully, but these errors were encountered: