---
title: "Configuring Read-Only Access for BigPicture Boxes in Jira"
canonical: "https://support.appfire.com/space/SUPPORT/3504144436/Configuring%20Read-Only%20Access%20for%20BigPicture%20Boxes%20in%20Jira"
format: markdown
---
This article explains how to configure BigPicture to allow users to view Box contents without the ability to create or modify data. This is useful for stakeholders who need visibility into project timelines or resource plans but should not make changes.

### Summary

This article covers the configuration of read-only access for BigPicture Boxes by utilizing specific App-level permissions and Jira synchronization settings.

### Use Case: Sharing a Read-Only View of a Box

**Problem/Context:**  
A user wants to share a specific Box view with a group of users but needs to ensure they cannot edit tasks, modify the Box structure, or change configurations.

**Solution:**  
To achieve a read-only experience, you must configure the user's permissions at the App level and optionally align visibility with Jira's native security settings.

#### 1. Assign "App User" Permissions

The primary way to restrict editing capabilities is by assigning the **App User** role. Users with this role can view the app's contents but lack the authority to create or modify Boxes and tasks.

- **Action:** Navigate to BigPicture **Administration > Security** and ensure the target users or groups are assigned the **App User** role rather than App Admin or App Editor.

#### 2. Enable "Respect Jira Screen Scheme"

To further ensure that users cannot edit fields they shouldn't, you can enable the toggle that forces BigPicture to follow Jira's field configurations. If a field is read-only or hidden in Jira's screen scheme, BigPicture will respect those settings.

- **Action:** Go to **App Configuration > Advanced** (or relevant toggle section) and enable **Respect Jira screen scheme**.