In a group space, I have individual pages created for various team members which are used to assign tasks. These users have view access to the top level space, but edit permissions on their respective task page. They can see the tasks assigned to them in their tasks view, or task list macro, but cannot complete the task via the check box. They receive a permissions error when attempting to do so. Where am I going wrong?
Here is what I suggest to folks in this dilemma:
1. Create (or give permission to existing) the home page with open permission (view & edit) to everyone.
2. Create folders to house the things you dont want people to see or edit
3. Create a special folder with view & edit permissions OPEN, then restrict the pages inside it as you see fit.
This way, no one knows about anything in the space that you dont want them to see - they just know the space exists with the pages you have given them permission to. This happens ALL THE TIME at my work.
If there is stuff you want on the home page you dont want others to see, I believe you can use "Include page" macro and restrict the include page so the home page will look blank to restricted users.
It did take a few efforts and think around's, finally I managed to get the desired results
Not ideal, but manageable atleast
What constitutes "edit permissions" at the space level? For example, is it enough to have "Delete Own" permission? Must I have permission to "Add Pages"? Must I have permission to "Delete Pages"? What--exactly--are the minimum set of permissions to a space that a user must have in order for that user to be able to check off an assigned task as having been completed?
That may be the case, but it's completely illogical in the real world.
There are many many many use case where we want to expose only one/few documents. Having to grant permissions to the entire space makes no sense.
Having to grant permissions to the entire space, and then manually lock down everything EXCPET THE DOCUMENT YOU ARE TRYING TO SHARE is way too much work.
This is a BUG. Fix it!
If I (feeling like a little Bambi in Confluence at times) follow this logic. I would assume that when I:
these restrictions & users should be same for all pages you add to this sub page. Regretfully this does not seem the case.
Am I really misunderstanding it all?
I came her for the same use case, someone needing to tick the box of tasks i've assigned to them, without them needing edit access to the whole space and me not wanting to give edit permissions on space level and than to have restrict about all pages accept for one :-(....
I've run into this limitation of the current authorisation architecture of Confluence many times :-(.
- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...
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