You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi, I am trying to work with vendor and contractors at work, who are onsite engineers that has some limited access to everything or something.
I have created a dashboard/confluence page and sub pages for each vendor.
I am trying to add these vendor/contractors to their respective space/page(s), but so far have not been able to figure out a way to do that.
Please advise if there is a way or feature to add/grant individual access.
Thank you in advance!
@Fei Lin In Cloud (if you're on that), the user has to have permissions to access the parent page to be able to access the child page. I think this extends up the tree.
So all of the vendors would need access to the dashboard page and then each vendor to their own sub-page.
You can start with this page for information: https://support.atlassian.com/confluence-cloud/docs/add-or-remove-page-restrictions/
Thank you for your response!
The whole idea is to prevent any access to the parent page but only provide access to the page designated to the specific vendor/contractor(s), and the child page(s) within that page(Dashboard created for the planning, task distributions, updates, results, documentations etc.)
Would assume we can always created a page/dashboard within any parent page and just add individual(s) to that specific page/dashboard and all the child page(s) under that page/dashboard, regardless what restriction the parent page of that dashboard has.
I did not find any information on that yet.
But hope this is a basic feature that is built in the Confluence platform/tool.
Hello @Fei Lin
Welcome to the Atlassian community.
Are you working with Confluence Cloud or Confluence Data Center?
If the URL is similar to the following then it is Confluence Cloud:
Otherwise you are using Confluence Server/Data Center.
Have the users been made licensed users of the Confluence product?
Are they able to access the instance at all?
Can you provide a screen image of the error that the users are actually getting?
We are using Confluence Server/Data Center.
The URL is based on company's website.
The vendor/contractors are onsite working with employees but all they get is Page Not Found for the same link/page provided to them.
I understand due to security and privacy concerns there is a permission/access limitation but I would always think we can add individual to the page and the inherited child page(s) so to limit their access only to the pages they are added to.
This would be a very basic and fundamental feature for a platform like confluence.
Hope this is not something too much to ask for. :-)
Addressing your comment on my answer and on @Barbara Szczesniak 's answer about giving users access to a page and that enabling them to access the child pages under that, that is how inheritance of page access works.
However, the user must have access at the highest level in order to access any descendant page in the tree.
If you have a page tree like this:
|-- Page 1.1
|-- Page 1.1.1
|-- Page 1.2
In order for a user to have access to Page 1.1.1, the user must have access to Page 1.1.
In order for a user to have access to Page 1.1, the user must have access to Page 1.
You can't give the user access just at Page 1.1 level. Since page access is inherited, Page 1.1 restrictions grant access to more people than Page 1 restrictions.
The users will need to be made licensed users of Confluence, first. Then they must have access to the highest level page that is a parent above the pages the users should be able to access.
If you don't want the user to have access to Page 1.2 and its descendants, then you will have to set page restrictions on Page 1.2 to prevent their access to that page and its descendants.
You may have to adjust the page tree structure to create a top level page to which the users can all be granted access, and then create a child page under that per vendor where you can set the restrictions on each of those pages to the users for that vendor.
If the space has other pages that the vendor users should not be able to see, you will have to set up restrictions on those pages also.