How to set up restricted permission pages / spaces in Jira/Confluence
Asked by Sandra Lawrence:

Hi we have our project setup (PMMSS) in Jira and Confluence. We are now looking for the best way to set up pages/dashboards/spaces for a **restricted group of people** (our internal team, not for everyone).

What is the best practice for doing this?


Answers:
author: Ollie Guan
body: Hi [@Sandra Lawrence](/t5/user/viewprofilepage/user-id/4448641) ,

If you need to set that only a specific group can access Jira Project and Confluence Space, then the permission scheme can do this.

If you need to make more detailed classification, for example, a certain issue is visible to certain users/user groups, and certain pages are visible to certain users/user groups, then you need to further set Jira's Issues security scheme and Confluence page restrictions.

comments: author: Sandra Lawrence
body: Ollie - thanks so much for this clarification! I believe your answer "...certain pages are visible to certain users/user groups, then you need to further set Jira's Issues security scheme and Confluence page restrictions" is what we need to do. I have another question for you : where can I learn to set Jira's issues security scheme and learn more about the Confluence page restrictions?


author: Sandra Lawrence
body: Ollie - the research I have found speaks to setting these security scheme's at a project level, not on how to do it within a certain space or page...that is my question. Thanks


author: Sandra Lawrence
body: Ollie - any more details or where I can go to make utilize your answer "...certain pages are visible to certain users/user groups, then you need to further set Jira's Issues security scheme and Confluence page restrictions" Would appreciate any links or resources (youtube even) to help me figure out these 2 particular solution sets.


author: Sandra Lawrence
body: Ollie - let me share my situation a different way. We have 1 project in Jira/Confluence which equates to 1 backlog. That backlog is for our agile development team. What I want to do is create another backlog within the same project. This backlog would be for only business issues. can we do this (create 2 bcaklogs in 1 project)?

Or - is it a best practice to enter 'business related' issues into the same backlog but filter them out so the development side never sees them? If a best practice, I am interested in understanding what are the best ways to isolate business issues from development issues so neither side has to see the others. Thanks


author: Ollie Guan
body: Hi [@Sandra Lawrence](/t5/user/viewprofilepage/user-id/4448641) ,

sorry for late, Hope the following content is helpful to you.
> certain pages are visible to certain users/user groups, then you need to further set Jira's Issues security scheme and Confluence page restrictions.

[Add or remove page restrictions](https://support.atlassian.com/confluence-cloud/docs/add-or-remove-page-restrictions/)

[Configure issue security schemes](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/)
> is it a best practice to enter 'business related' issues into the same backlog but filter them out so the development side never sees them? If a best practice, I am interested in understanding what are the best ways to isolate business issues from development issues so neither side has to see the others.

You can try to filter different issues through the panel settings, such as by Issue Type, label, or other conditions that you can use to distinguish.

Then you can split it into two boards, and distribute permissions so that different users cannot see different boards.

[Editing a board's filter](https://support.atlassian.com/jira-software-cloud/docs/configure-filters/)


Tags: cloud

confluence-cloud

jira

permission

space