Additional Permissions for Custom Roles

What is the challenge?

We need the ability to create custom roles that go beyond configuration settings and allow us to permit or restrict access to specific object types (e.g., ideas, epics, goals, initiatives). For example, our Customer Success team needs access to create and view ideas and generate idea reports, but we don't want them to see sensitive information such as initiatives, epics, or features.

What is the impact?

Currently, there is no way to restrict or permit access to specific objects within a workspace. This limitation means that when we grant Customer Success access to our workspace, they gain visibility into all development details, including timelines and statuses. This can lead to the unintentional sharing of incorrect or premature information with customers, creating potential confusion and misaligned expectations.

Describe your idea

Introduce configurable object-level permissions for user roles. This functionality would allow us to grant access to specific objects (e.g., ideas) while restricting access to others (e.g., initiatives, epics, features). This customization would help ensure that team members have the access they need without compromising sensitive information.