Synced Kitsu users should be granted project accesses through distinct project access groups

[Tilix4]

Is there an existing issue for this?

• I have searched the existing issues and added correct labels.

Please describe the feature you have in mind and explain what the current shortcomings are?

Currently, all synced kitsu users are put into a single default access group. If you want to manage access to different projects, you must manage access group manually using Ayon, even though this has already been done with Kitsu by adding users to the projects' respective teams. Users synchronization should allow to assign kitsu users to several access groups based on the project teams.

Suggested implementation?

• Creating several access groups based on the project teams. An access group by Kitsu project would be created, with a name Kitsu <Project Name> and synced users would be added to the groups based on the Kitsu project teams they belong to.
• All users would still be put into default kitsu group (current implementation) as default.

Question: Should this feature be an option or the new default behaviour as the described implementation doesn't break the current one?

Describe alternatives you've considered:

No response

[MustafaJafar]

So, a TL;DR; to "Map the Kitsu project teams to AYON project Access groups on synchronizing users"?

I'm not sure if this is the correct approach as syncing users should match the user creation on AYON where we set a default project access group. and I think this is what happens atm.

Instead, I think the access should by synced on project creation/sync as each project includes its own project access list.