I am writing to suggest some exciting new features that could greatly enhance the collaborative aspect of Scratch studios.

1. Customizable Studio Roles, Permissions, and Comment Sections:
Currently, Scratch supports three studio roles: “Studio Host,” “Manager,” and “Curator.” While these roles are useful, I propose the introduction of a feature that allows users to create and customize their own studio roles, along with specific permissions tailored to each role. Additionally, it would be beneficial to have role-specific comment sections within studios. This would enable users to have focused discussions and feedback within specific roles, fostering collaboration and organization. For instance, users could define roles such as “Designer,” “Moderator,” or “Contributor,” each with its own set of permissions and a dedicated comment section (certain roles could have permissions to look/moderate comments. Studio owners would have the ability to assign certain roles access to specific comment sections, allowing for controlled and targeted communication.

2. Automated Studio Invitations and Role Assignments:
Another feature that would greatly enhance the studio experience is the ability to send automated in-game studio invitations to users playing the project, along with the assignment of a specific role. This feature would ensure that invitations are received within the Scratch platform, preventing potential spam and maintaining a seamless user experience. Users could set up triggers or events within a project by using a block like this,

 give invitation the user to [Studio Name v] as a/an [Role v] and wait::events 

and when those conditions are met, Scratch would automatically generate an in-game invitation to join a specific studio for the designated users. Along with the invitation, the assigned role would be communicated to the user within the Scratch interface. This mechanic would streamline the process of expanding studio membership and faster engagement among users, encouraging them to collaborate and contribute to various projects.

3. Role-Based Monitoring of Comment Sections:
To further support moderation and ensure a safe and constructive environment within studios, it would be beneficial to have customizable options that allow certain roles to view and monitor comment sections assigned to other roles. Studio owners should have the ability to define which roles can access specific comment sections, providing oversight and the ability to monitor behavior and interactions. This feature would help maintain the integrity of the studio community and provide a mechanism for responsible role-based moderation.

I believe these enhancements would significantly enrich the collaborative experience on Scratch, enabling users to have more control over their studios, fostering targeted communication, and promoting a safe and constructive environment for collaboration.

Thank you for considering my suggestions. If you have any questions or would like further clarification, please feel free to reach out. You can change some things about the suggestion if you’d like.

Please do not make a list of suggestions unless they are related to each other (example: new blocks for an extension). Thanks

Scratch--TheCat wrote:

Please do not make a list of suggestions unless they are related to each other (example: new blocks for an extension). Thanks

The blocks are related to the studio suggestion.

Can’t get rid of this.

Infinity_Rex wrote:

Scratch--TheCat wrote:

Please do not make a list of suggestions unless they are related to each other (example: new blocks for an extension). Thanks

The blocks are related to the studio suggestion.

They are still a suggestion hub since it's a list of suggestions.

Infinity_Rex wrote:

Delete this

You can't “delete” a forums discussion topic.

Crispydogs101 wrote:

Infinity_Rex wrote:

Scratch--TheCat wrote:

Please do not make a list of suggestions unless they are related to each other (example: new blocks for an extension). Thanks

The blocks are related to the studio suggestion.

They are still a suggestion hub since it's a list of suggestions.

What I’m saying is that there are 3 suggestions in the post all related to each other. That’s why the block suggestion is in there.