Forum Discussion
Sharing with everyone available but sharing within organization is disabled
All, just asking a couple of 'dumb questions'.
Does this setting have anything to do (or could be a conflict) with whether the site was created from the SP Admin portal or via the SharePoint portal (Create site)? And, if it was created from the SP Admin portal, does it have anything to do with the general Sharing settings or the Sharing settings on the individual site?
I can't replicate this issue. We allow (a) for Sharing, 'Allow users to invite and share with authenticated external users', and for individual sites where sharing is allowed, 'Allow external users who accept sharing invitations and sign in as authenticated users'
- bart_vermeerschNov 10, 2017Iron Contributor
In our case it's our root tenant site (which was provisioned automaticaly).
Our users have no access on the site itself, only on the libraries (images and pages).
- AndrewWarlandNov 12, 2017Iron Contributor
Thanks Bart. Wherever possible, we do the following on our sites:
- Allow 'everyone (except external users) read only access
- Restrict only what needs to be restricted; this includes changing the Members to 'read only' if we don't want changes made
- Keep an eye on the audit trails
We follow this model after many years of trying to fix up customised permissions on libraries and lists (and some pages), and even folders and individual documents, which became a nightmare to manage.
On our root site (name.sharepoint.com), we allow 'everyone (except external users)' read only access to the content as we use that site as a general 'portal' site to point users to where they may want to go to, e.g., their OneDrive, their SharePoint, their O365 etc. We did think to use it as a replacement intranet but changed this strategy once we saw the potential complexity involved.
- Salvatore BiscariNov 10, 2017Silver Contributor
So, if I understand well, you have modified the standard permissions of the root site collection of the tenant (i.e. "tenantname.sharepoint .com").
And you have broken inheritance for a bunch of document libraries under the root site and implemented additional permissions for such doclibs.
Correct?
Could perhaps this be the reason for the odd behavior of sharing in such doclibs?
Just an idea...
- bart_vermeerschNov 10, 2017Iron Contributor
Salvatore Biscari correct.