I agree with f2a77736a284 and aba047463be6. Our teams need ability to see the dependent work on partner team's Program boards and ability to see the status of dependencies placed on other teams during the PI. Often our teams operate without scrum masters as a role (shared responsibility across the team due to resource constraints), which makes it difficult to communicate between teams on the status of work. When they find out too late that the work wasn't done, it creates huge delays and unnecessary costs that add up quickly. Ability to read-only for other team's boards while having a separate set of system permissions and role(s) on the users own team would open up a lot of visibility and increase our delivery speed, not to mention the rate of adoption for Jira Align. Adding this view-only capability would help to build trust in organizations that are struggling against the forces of shadow IT and business-vs-IT culture. This is an opportunity for a huge game changer that would set Jira Align apart from other similar tools.

Similar ask:  User story:As a User, I want to Modify permissions and roles, so that we can address Compliance and audit concern issues.

As a User, I want to set membership to be read-only at the portfolio or team of team level , so that I have appropriate controls to eliminate risks with data access .Request description:If a user has a Jira Align role (portfolio planning, team planning, strategic planning), it cascades to every portfolio/team of team they are assigned as a member. We need a solution that allows users to designate read only access at the portfolio / team of team access independent of system role. This will eliminates the risk where contributing teams have full access to make changes to portfolio / team of teams

Note that this is likely encompassing multiple other similar asks on other pages.  As a result – please count the votes across ALL these different pages.

Here is a subset example

1. JIRAALIGN-6735Read-only view of Backlog
2. JIRAALIGN-5560Administration: Ability to create a true read-only role in Jira Align
3. JIRAALIGN-5737Integrated Users Read Only the Portfolio Backlog
4. JIRAALIGN-6251Toggle to enable Read-Only access to Programs
5. JIRAALIGN-7090Allow Integrated Users to view Dependencies as Read-Only
6. JIRAALIGN-7610Decouple Capacity Plan Read-Only Permissions across levels

The most common use case we have seen is that Portfolio/Program/team A needs to be able to see the roadmap, backlog and other objects on Portfolio/Program/team B

While you can give membership to the user to access both – it also means that user has create, edit, delete ability on the corresponding portfolio/program/team. 

We can't provide transparency to executives or users in the same role without a risk.  Imagine co-worker making changes to your ranking or your objectives, etc without your knowledge.  

There needs to be the ability so that roles and permissions for your team  membership with CRUD is different than read-only access for other teams where you are need ability to view the roadmap or objectives or item

Eliana P - curious what areas you've come across that you can't make read-only? We have what we think is a read-only role, but perhaps we're overlooking some edit capability we're not aware of. Kyle - what we desperately need is the ability to give read access per team membership; so write access to your working team can be provided at the same time as read access to others/all. Not having this is killing our ability to gain traction with JA organizationally. See also https://internal.jiraalign.com/ideaZone/ideas?ideaID=1354https://internal.jiraalign.com/ideaZone/ideas?ideaID=1018

Thank you for the suggestion. We'll set this to open to gather votes and feedback.