Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Add Edit permissions for a restricted page

Hi, I need to add a user to view and edit a restricted page in a space where he has no access.

There are no permissions set for this user at the space level, but I need him to have the ability to viewe and modify a specific restricted page.

If I add him with view permissions, looks like there are no issues; if I set him with Edit permissions, this appears(look screenshot_1)screenshot_1.png


I can't add him at the space level with view all, because he would start seeing all the pages in that space and I don't want this.

screenshot_2.png

If I try to set it like screenshot_2, then the user disappears at individual permissions (space level)

 

Can you please provide me a solution to this

3 answers

1 vote

To do it "properly", this user needs to be able to see the page.  That means you will need to add them to the "view" permission for the space.

There are a couple of ways to "cheat" if you really don't want to give them the access they need.

  • Move the page to a place they can edit, let them edit, then move it back.
  • Change the page so that it uses "include" for the part(s) of the page that they need to edit, put the page that your include uses in a space where they can see and edit them (as can the other people in this space)

I confirm what @Nic Brough _Adaptavist_  is saying: first of all, the user must be allowed to access the space. This is kind of a consequence of the 'wiki philosophy' based on openness and collaboration.

So, you need to consider the 'Restriction' feature in this way:

  • by default, you grant permission to the whole wiki (all the pages) = if a user is granted access, s/he can access to the whole wiki
  • then, for a specific page, you add a restriction = only one or some users / groups (that you select) can access (only reading or editing) to this specific page. If you limit the reading ("View") to certain users, all other users will NO longer be allowed to access to this specific page and its child pages
  • and based on group permissions, you can limit what actions users can do (e.g. delete pages, change labels, etc.) in the whole space
0 votes

Thanks for the clarification but this is a strong limitation.

It is really against least privilege methodology, Devs from Atlassian should re-think about this.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Confluence

Announcing Team Calendars in Confluence Data Center

Hi Community! We're thrilled to share that Team Calendars for Confluence is now a built-in feature for Confluence Data Center releases 7.11 and beyond.  A long time favorite,  Team Cale...

125 views 0 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you