Hello,

Thank you for sharing your idea with us! We truly appreciate your input and are interested in seeing how the rest of the community feels about it. Your suggestion could be a candidate for future improvements.

Could you please confirm if your idea is similar to the one discussed in the following thread? 🙂 If it is, combining them would help gather support more effectively!

Thanks,

Toku (Japanese is also welcome!)

Hello, thank you for your reply. Yes, the idea I proposed is similar to the thread you referenced. To build on that discussion, I think having default user roles such as developer, designer, manager, and client could be useful. It would also be great to allow custom roles that users can create themselves.

Assigning roles can be used to:

• Set editing permissions for each role


• Select which pages each role can access (Ex. Users assigned the ‘dev role’ can only see pages 2 and 5)


• Use ‘@ role’ to ping a team of people


• Selecting ‘Mark as ready for dev’ should automatically notify anyone with the developer role

Thank you. Please let me know if anything is unclear.

Best, Yusuke

Hi Yusuke san!

Thanks for the clarifications. It’s very helpful! Considering your input, I think it’d be best to keep this discussion separately. Let’s see how community reacts!

Thank you so much!

Toku

I believe that having a way to adjust different levels of access to different roles is really a great solution, but maybe a “dev” role would already improve a lot the current situation.

I’m part of a team on an enterprise plan.

By default we don’t enable in our files “Allow viewers to copy, share, and export this file” (because it also allows “viewers” to duplicate the file). But recently we came across the situation that if this option is not enabled, devs are not able to use community plugins nor export items from the file.

So, my idea would be basically what the other community member suggested some time ago here.

Thanks and all the best,

Jackie