Integrating external user feedback as studio comments and/or tasks on documents

[vildeserina]

Is your feature request related to a problem? Please describe.
Currently, there's no straightforward way for external users to add comments or tasks directly to Sanity documents via a webpage, which can then be easily accessed within the Sanity Studio.

This limitation makes it difficult to gather and manage user feedback and suggestions efficiently, forcing users to use less integrated methods like email. It also complicates the content revision process as feedback and task requests aren't directly associated with the relevant content in the Studio.

Describe the solution you'd like
I'd like a feature that allows:

1. External users to submit comments or create tasks on a webpage associated with a specific Sanity document, as an anonymous user.

2. These comments and tasks to be integrated seamlessly with the existing Tasks and Comments features in Sanity Studio, direclty attached to the relevant Sanity document.

3. Easy access and management of these comments and tasks within the Sanity Studio, alongside the document they relate to.

Describe alternatives you've considered

1. Try to achieve this with the existing API, but it doesn't seem like this is possible or intended to be possible? And the documentation for querying comments is confusing to me now.

2. Adding comments and tasks as fields to the existing documents, which complicates the document structure and version control.

3. Creating separate comment and task documents and linking them to the main documents, which adds complexity to querying and management, and creates an unecessary amount documents.

4. Using external commenting and task management systems, which lack integration with Sanity Studio.

Additional context
This feature would significantly improve the feedback loop between content creators and users. It would allow for more contextual content revisions and task creation, as feedback and requests would be directly associated with specific documents in the Studio.

This integration would streamline the process of gathering, reviewing, and acting on user feedback and suggestions, enhancing both user engagement and content quality.

It could also be used for user testing! Which would be kinda genius for us.

The ideal implementation would be simple to set up and use, requiring minimal changes to existing workflows while providing powerful new capabilities for user interaction and content management. It would respect the existing permissions structure for tasks and comments, ensuring that external users' input is appropriately managed and visible only to those with the correct permissions.

This feature would be particularly valuable for projects on the Growth plan and up, aligning with the current availability of the Tasks and Comments features. It would extend the collaborative capabilities of Sanity Studio to include external stakeholders, creating a more inclusive and efficient content creation and management process.

[runeb]

Hi @vildeserina, thanks for the detailed feature request!

You are right that your use case is not currently easily implemented by users themselves on top of the current commenting and task feature sets. Sanity would need to create an API and UI components for the writing and viewing of comments and tasks outside of Studios.

I have a few follow up questions, if you don't mind;

• When you say external users, do you mean users who do not have a Sanity account, but would like to leave comments in the Sanity platform?
• Would you be relying on enabling commenting on preview builds that are otherwise protected from open access, or would you want gating of this functionality from Sanity?
• When leaving a comment on a web page that has content from Sanity, what steps do you envision the user taking to making a comment?
• A web page will often contain content from several Sanity documents and multiple fields across those documents. Do you have ideas on what the UX would be to discover what content can be commented, how to view comments already existing on pieces of content?