Allow production to manage user roles

[Remus Avram]

Hi all,

we would like to give production the ability to manage the roles of the user without accessing the Ftrack System settings.

From our perspective, one way to do it is to add in the right-click menu a sub-menu "Roles" like the "Managers" one.

Or adding the roles to the user from the user Profile.

Or to emit an event when a manager type is added to a user. In this way we can match the "Managers" types with the "Roles" types and do it through an action.  ( @Luigi already started a discussion abut this here 

Thanks for your support!

[Mattias Lagergren]

Hi Remus,

This is something that is quite high up on our radar and something that we want to do. We've considered it as part of a revamp of the "Team" page in ftrack - to let the user configure what security roles a user should have.

It would be possible to do custom event listener / action for this (possibly triggered) but will of course require some work to get it efficient for the user.

[Remus Avram]

Thanks @Mattias Lagergren for the update. 

What do you think it would be a quick workaround at the moment?

[Mattias Lagergren]

One example could be to listen to changes when a user is allocated directly on a project:

1. Manager is adding AnimatorA to the project from the Team page.
2. Event listener pick up on this and (create or add to existing Animation group on project and add AnimatorA to it).
3. Based on e.g. Group belonging in System Settings, or by doing a Triggered Action asking the Manager what security role the user should have on the project.
4. Event listener / action script gives the user the given security role on the project.

I guess it will take a few hours to put this together and get it right. But should work and be quite convenient once it is working.

[Remus Avram]

Thanks @Mattias Lagergren for your toughts. 
If there will be an event when a Manager type is added to a user, then we can match the Managers types with the user roles and add the role ones a manager type is added to the user. 

The issue with the event is described here: