Forum Discussion
Modern Communications Hub Site- Error on Hub Home Page
MicrosoftMeg Simmons let me know if after the re-index if you're still having issues so i can look into this.
Hi Tony Hignett ,
Unfortunately I have not found any workaround for the use case you mention.
For my client it was a bit different because the invitation of external guest was moderated by some members of the organisation.
The general flow was :
- An external guest member with access enters a request on the team or communication site in a custom list.
- A Microsoft flow is triggered and notifies the organisation approver
- The approver confirms the request
- The flow resumes and creates a guest user in the Azure AD to which is assigned pre-defined security groups granting him the right level of access to the SharePoint sites.
- The flow creates an email with the guest invitation link to accept and redeem his invitation.
HiPhilippe Ouimet I also used the tips from this article which is great.
But in my case, the Hub site is associated to a collection of Office Groups with Microsoft Teams. My expectation is that users can invite External Guests to the individual teams. These external's can then access the hub and see all relevant news, site activity etc. where appropriate.
The trouble is none of this will work without someone also giving them minimal access at the root site of the tenant. This is a headache, If anyone has a good approach to managing this, I'd love to hear it.
Still no changes.
The site web part does not work for guest users and still has the same permission issues.
Never had any issues however with the news webpart on the hub except for the permissions issues on the image preview handler which was fixed using the tips in this article https://laurakokkarinen.com/sharepoint-online-guest-user-troubles-and-how-to-get-past-them/
I am getting exactly the same error message on the hub home page when testing with an guest user. News or "my sites" do not appear. The news web part do seem to work on other sites, but the sites web part do not show up similar to the hub home page.
I have tried giving the user read permission on the root site collection (https://xxx.sharepoint.com/_layouts/15/sharepoint.aspx) Did also try to give the user member-permission without any change. (Because the SP group "everyonce except external users" is already a member)
Philippe Ouimet What is your status on this problem?
- Hey there,
Unfortunately the only thing that worked for me is granting read-only access to our root site collection. If you have sensitive data on your root site collection you could consider granting read-only access to the site collection itself but, break inheritance and restrict access to lists and libraries that contain the sensitive data. - Hey there,
Unfortunately the only thing that worked for me is granting read-only access to our root site collection. If you have sensitive data on your root site collection you could consider granting read-only access to the site collection itself but, break inheritance and restrict access to lists and libraries that contain the sensitive data. I have a similar issue with the Sites web part placed on a hub site displaying all the associated sites.
It works perfectly for licensed users but all the guest users see the following error:
ERROR: Couldn't get sites. [object Object] Http status code: 403. Error code: 401000. SPHome-CV: Ki7HIIqFq02lTdeQq4P8cA.0. SPHome-Server: RD00155D5E6ED1 2018-08-24T15:27:43.3418588Z.
The guest users have read access as visitors on the hub and some of the associated site.
From the previous post I tried with test user to see if adding him as reader would fix the error to narrow down the cause but with no success.
Unfortunately even if that would have worked my root site collection is in use and it is not an option for me to grant guest read access.
Is someone else having similar issues?
- This happened to us as well, and the solution seems to have worked, thank you! Does anyone know why they need to have read access to the root site collection? We were trying to block our users from going there so they only go to the new hub site, we put in a redirect from the root site collection to the new hub site collection.
That did the trick. Thank you!
Yes, it was. My root site collection is not in use as we are building on the Modern experience. Granting my users read access to the root site collection fixed this issue on my Hub site.
Was this issue ever solved? I'm running into the same thing right now.
