Granular permissions for initiatives (user-level access control)

Problem:
Currently, Aha permissions are primarily managed at the workspace level. This creates challenges for initiatives that are confidential or limited to specific stakeholders. To restrict access, teams often create separate workspaces, which leads to fragmentation, duplication, and added administrative overhead.

Proposed Solution:
Introduce the ability to assign permissions at the initiative level, including its associated features and schedule. Workspace owners should be able to:

• Grant access to specific users or user groups for a given initiative

• Restrict visibility of related features and roadmap elements

• Maintain standard workspace access for non-restricted initiatives

Use Case:
For confidential initiatives (e.g., strategic partnerships, sensitive product launches), only a subset of users should have visibility. Instead of creating a separate workspace, teams could manage access directly within the initiative.

Benefits:

• Improved confidentiality and access control

• Reduced need for creating additional workspaces

• Cleaner workspace structure and better collaboration

• Less administrative overhead

Impact:
This would streamline how teams manage sensitive work while keeping everything organized within a single workspace.