Visibility: clean, clear, and consistent

[SimoneZaza]

Description

This epic establishes clear rules for what is visible to whom, and where across the platform. It aims to clarify visibility for user profiles, contributions, innovation packs, and venture capital (VC) details, both in public and private spaces.

Key considerations:

• Public vs. Private Spaces: Define visibility rules for content based on space type (public or private).
• Visibility Transitions: Notify users when a space changes from private to public to ensure transparency.
• Unauthenticated Access: Review and update visibility for unauthenticated users, such as access to forums and other features.
• Platform-Wide Consistency: Establish a unified approach to visibility that applies across all sections of the platform.
• User Awareness: Make these rules and changes easily accessible for users to read and understand.

Goal

Describe how this Epic impacts an initiative the business is working on.

Hypothesis

What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit.

Must have scope

• Visibility of user information, whiteboard: https://alkem.io/studiosimone/challenges/denisesimone/collaboration/visibility/whiteboards/whiteboard
• Clarity about visibility when entering a Space/organization
• Notifications on changes
• ...

Stakeholders

Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the Epic project.

Design

Figma file:
Comments are highly appreciated. When commenting in Figma, please also leave a note in the comments box below this issue to notify us