A configuration saves the board’s Jira source and presentation choices so you can return to a useful view or share it with colleagues. It does not copy Jira issues or grant permission to read them.
Find the controls
Use the saved-board selector and Save in the app header. The adjacent Manage board menu contains Rename, Save as, Share and Delete for boards you own.
Rename, Save as, Share and Delete are separate actions.
Select a saved board to reopen it. Use Save as when you need a separate copy rather than replacing the current configuration.
Save and reopen your first board
Start by saving your current board, then reopen it using the selector. The reference below explains updates, copies, ownership and sharing.
- With a source loaded and unsaved changes, select + Save in the header.
- Enter a descriptive name and confirm with Save or Enter.
- Find that name in the saved-board selector and select it. Check that the source and layout are the ones you intended to keep.
Enter a descriptive name, then confirm with the checkmark. This capture stops before saving.
This image shows name entry before confirmation, not a completed save. Entering a name alone does not save the configuration.
Check that your new board was saved
After confirming Save, look for your new name under My boards in the saved-board selector. You can type part of the name to narrow the list. To check that it remains available across visits, reload Board Studio, select the saved name and compare the restored Jira source and board structure. Reloading is a useful check, not a requirement for saving.
In this staging example, Lea saved a new private Northstar Treasury board with Status then Priority in its name. After reloading the app and reopening that board, the Frontend source and the Status, then Priority, dimensions in Rows were restored. Columns remained empty. The screenshot shows the new entry under My boards and the reopened Story-level layout together.
After saving and reloading, find the name under My boards and reopen it.
Saving this configuration does not change Jira issues. It keeps the view private until you explicitly share it; the existing Frontend Kanban configuration was not overwritten.
Recognise a reopened board
In this staging example, Lea selects her existing Frontend Kanban saved configuration. Its header identifies the Frontend source, while the sidebar shows Status in Columns and Priority in Rows. Ten Stories appear on the board from 32 loaded work items across levels.
Check the saved name, source, Status columns and optional Priority rows.
This is a verified load of an existing saved board, not a new save confirmation. Compare the name, source and arrangement with what you intended to save. The current Jira cards can change between visits even when the saved configuration stays the same.
What is stored?
| Setting area | What is saved |
|---|---|
| Data source | Space or Filter and the selected source. |
| Board structure | Swimlanes, grouping and level-specific presentation choices. |
| General settings | Sorting and other configuration choices. |
| Links | Link visibility and per-type visual styles. |
Loading a configuration restores its settings together. Use the header’s configuration selector to choose your own boards or those shared with you.
Saved boards include the dedicated Northstar documentation configuration.
Create a saved board
- Choose a Jira source and configure the view.
- When there are unsaved changes, select + Save in the header.
- Enter a descriptive name in the name field.
- Select Save or press Enter to submit it. Select Cancel or press Escape to leave name entry without saving.
The plus-icon Save button opens name entry. It is not a separate one-click update button. The confirmation Save and Cancel controls appear while you are editing the name.
Update an existing board
- Load your saved configuration and make the required changes.
- Select + Save. The name field starts with the current saved name when available.
- Keep that name and select Save or press Enter.
- If the save reports an existing name, review the overwrite confirmation. Confirm only when you intend to replace the existing configuration and have permission to do so; otherwise cancel and choose a different name.
If the name is already in use, follow the validation or confirmation shown. An existing name does not give you permission to overwrite someone else’s board. Do not assume every name-edit action, including Rename, has the same overwrite flow.
Actions in More
Open More beside the configuration selector for these operations:
| Action | Purpose | Who can use it |
|---|---|---|
| Rename | Change the saved configuration’s name. | Owner only. |
| Save as | Save an independent copy under another name. | Users who can load the configuration. |
| Share | Edit the people and groups who can use this configuration. | Owner only. |
| Delete | Permanently remove the saved configuration. | Owner only. |
Rename
Select More → Rename, edit the name and confirm with Save or Enter. Use Cancel or Escape to abandon name entry. Follow any validation message shown rather than assuming a conflicting name will always offer overwrite.
Save as
Select More → Save as, enter a new name and select Save or press Enter. The copy is independent: changes to it do not update the original. Sharing recipients are not copied, so review sharing separately if the new configuration should be available to others.
Recipients of a shared board can adjust their current view and use Save as to keep their own version. They cannot rename, share or delete the owner’s configuration.
Delete
Select More → Delete and confirm the deletion. This removes the saved configuration, including its availability to recipients. It does not delete Jira issues.
Share with people and groups
- Select a configuration you own, then choose More → Share.
- Search for people or Jira groups. Enter at least two characters to search.
- Add the desired recipients. People and groups can be included together.
- Remove recipients you no longer want to include.
- Select Apply to commit the sharing changes.
A Jira group that covers your organisation can make the configuration available to all its members. There is no separate Entire organisation switch. Choose the group deliberately and consider its membership before applying.
This dialog has no selected recipients. Cancel leaves sharing unchanged.
The screenshot shows the sharing dialog with no recipients selected. It locates the controls; it does not show completed sharing or a recipient’s view.
Remove sharing
Open Share again, remove individual recipients or clear the recipient list, then select Apply. Clearing all people and groups and applying makes the configuration private again. Editing the draft recipient list alone does not commit the change.
What recipients can access
Recipients can find the shared configuration in their selector and load its layout. They still need the appropriate Jira project, filter and issue permissions. Sharing a Board Studio configuration does not grant Jira access, and recipients may see different work if their Jira permissions differ.
Newly added individual users can receive a best-effort sharing notification in an open app session. Delivery is not guaranteed and there is no persistent sharing inbox or group-wide notification fan-out. Recipients should check Shared with me even if no alert appears. See Sharing Configurations.
Persistence and practical tips
Configurations are stored in Atlassian-hosted app storage for the Jira site and remain available across sessions and devices. They are private until explicitly shared.
- Give each configuration a name that describes its purpose, such as Release readiness or Sprint dependency review.
- Use Save as before experimenting with a working view.
- Share with the smallest appropriate set of people and groups.
- Check Jira filter sharing separately when a configuration uses a saved Filter.
- Delete obsolete configurations to keep the selector useful.
Related
- Global App Interface: locate the selector, Save and More controls.
- Board Configuration: shape a reusable view.
- Data Sources: source scope and Jira permissions.
- Guided Tours and Contextual Help: activate Help and select the configuration region for an in-place explanation.





