Top questions asked by nonprofit customers - Q3 answered!

[#1]

Continuing the series on top questions asked by nonprofit customers, I'd like to share another common question: 

How do we manage permissions and user access in Jira and Confluence?

While Atlassian encourages an open-by-default approach to knowledge-sharing, protecting Personally Identifiable Information is particularly important when working with vulnerable populations.

Getting permissions right also means less chance of human error such as accidental deletions, editing settings that affect multiple teams and a proliferation of unwieldy Jira projects.

Permissions in Jira and Confluence are managed through groups and roles.

• Assign users to groups based on their responsibilities (e.g., admins, contributors, viewers).

• Use project roles to control who can view, edit, or administer projects and spaces.

• Review permissions regularly to ensure security and compliance.

Fun fact...

Rovo will respect these permissions when searching for knowledge. Read more: https://support.atlassian.com/rovo/docs/rovo-data-privacy-and-usage-guidelines/

Refer to the Jira Permissions Guide and Confluence permissions documentation for more information.