I created a publishing site in sharepoint online and provided unique permissions. Two users (one internal & other external) provided full permissions. Internal user can access site but external user can't access site. Can anyone please assist what is the problem ?
The problem is solved now. The problem was that there was limitation of external domains in site collection feature. If want to limit external sharing of site, follow below steps:
1- Got to https://portal.office.com and click on Admins.
2- Click on Sharepoint in Admin Centers.
3- Click "More features" in left side.
4- Click "Open" on "Classic site collection page" in right side.
5- Select the site collection of the site and click on Sharing.
6- Go to Site Collection additional settings and add gmail.com (if there is already domain added, put space between two domains).
7- Click save button.
Now access the site using external user account.
Related
I have created a SharePoint tenant. But the root site template type is the classic team.
How to replace my SharePoint root site template with the modern team from the classic team?
Please follow the steps:
STEP 1:MAKE SURE ROOT SITE IS NOT USED
First, make sure that the current, classic root site and subsites (if any) are not used by anyone. If it is or was used, make sure all the content has been backed up and no one is synchronizing any libraries from the root site or its subsites to their computers (otherwise, when the old site is moved over to archival URL – more on this later) – it will cause sync issues.
STEP 2: CREATE A MODERN SITE FIRST
1.Navigate to either a SharePoint Admin Center or SharePoint Start Page and click on Create Site. Then choose Communication Site template
2.Give your site a name, click Finish
Note: This new site must be a Team site (without an Office 365 Group) or Communication site. It can’t be connected to an Office 365 group (the most common type of site in your environment).
STEP 3: NAVIGATE TO THE SHAREPOINT ADMIN CENTER
Navigate to the SharePoint Admin Center >> Active sites
STEP 4: REPLACE A CLASSIC ROOT SITE IN SHAREPOINT ONLINE WITH THE MODERN COMMUNICATION SITE
1.Copy the URL of the Communication Site we created in Step2
2.Now click on the checkbox next to the root site (the one with just [domain.sharepoint.com] in the URL column, then choose Replace site from the top ribbon (you might need to click on three dots to get to that command)
3.On the next screen, paste the URL of the Communication Site from Step2, then click Save
4.And just after a few minutes, your site swap will be completed!
Here is a good blog for your reference:
How to replace a classic root site in SharePoint Online with a modern site
I have a site collection with a subsite. I am storing a roadmap and some other project management documents within a document library in my subsite. I would like to share that document library with an internal user, but I don’t want her to see anything else – just that document library. I don’t want her to see any other parts of the site. Can I do that? How?
Yes,
Go to Site Settings > Site Permissions
Remove the user from all groups (click on Check Permissions to see what permissions she has on your site).
Go to the document library and click on the Library tab in the
ribbon.
Click on Shared With (far to the right)
Click on ADVANCED
Click on Stop Inheriting Permissions, confirm with Ok
Click on Grant
Permissions and give the user the appropriate rights (read, edit
etc.)
EDIT:
This is for a SharePoint 2013 site. Sorry for that. I dont have a SharePoint 2010 site available right now so I cant give you the exact steps, but the concept is still the same:
Remove the users permissions to the site.
Stop inheriting permissions for the document library
Grant the user permissions to the documet library
I have a sub-site (http://mysite/documentcenter). My user is in Site Collection Administrators, so I can see and click the move button in site content and structure of sub-site.
But the other users, who has contribute access to all documents, can't see the Move button - it completely disappeared, it's not greyed out.
How can I make the move button display for the other users?
I know this question is a bit old but, you need to have the following Permission Level enabled or Move is not available.
Manage Web Site - Grants the ability to perform all administration tasks for the Web site as well as manage content.
I would be very careful assigning this permission though as it adds a whole slew of additional access for the user(s).
Make sure Add and Customize Pages permissions is present. There could be a Deny mask coming in from User Policy from central admin, which can overwrite Site Collection admin permissions.
Outside of the "My Site" page in SharePoint, is there any way to allow my sites visitors/users to add or remove web parts on pages without giving them contributor writes? I'm working on a corporate intranet that is being built with SharePoint and they want the home page of the site to be highly personalizable. But besides the "My Site" page, I don't know of any way to allow all of the visitors to add or remove web parts. Can anyone provide any guidance? Thanks.
I tested this with a publishing site on sp2010, and the permissions you need are:
Site Permissions
Add and Customize Pages
Browse Directories
Personal Permissions
Add/Remove Personal Web Parts
Update Personal Web Parts
The personal web part permissions dont work on their own
You could create your own permission set, where you should set "Add/Remove Private Web Parts" permission and "Update Personal Web Parts" permission, but remove those permissions which you don't like in "Contributor" permission set. Then assign this new permission set to users or groups you need.
When I place a test AD account in the Visitors group they are unable to view any pages on my new intranet site. The users receives the "Error access denied" sharepoint screen and indicates that the account was able to authenticate, but that some authorisation rule is permitting it from viewing the page.
When i remove then and place them in the Members or Owners groups they are able to view the pages as well as perform the expected functions like editing content and creating subsites.
Interesting, while in only the Visitors group, users can view the "All Site Content" page that is located here: /_layouts/viewlsts.aspx but not /pages/default.aspx.
Has anyone experienced this before?
Environment info:
1 Web application, 1 Site collection using the Publishing Portal template. A few custom master pages, lots of custom page layouts and user controls. All deployed via features.
Sharepoint 2010 Standard edition, 64bit running on Windows Server 2008 against SqlServer 2008 Enterprise Edition. Authentication is against AD, not any other forms auth providers etc.
One likely reason for such behavior is that it tries to access a resource on a page which might not have been published to a major version. For example, if versioning was turned on on images library and an image's version is 0.1, if that image was used on version 1.0 (published) of the page, the server would deny access to the visitor and ask for credentials.
Make sure following:
At least one major version of the page exists (page was published at least once)
All resources (images, movie files etc) used on the page are published (to major version)
You can use "Draft Check" button on Page Tab of the Page's ribbon to check the unpublished resources that are used by the page.
I had the same issue and I've finaly found out how to do this:
If you check OOB group access, you can find that Visitors group has limited number of pages where it has granted access.
Navigate to /yourweb/_catalogs/masterpage. Here you'll find many
.aspx files (including default.master).
Open this default.master`s permissions and you see it inherits from
Master Page Gallery.
Click this permissions inheritance and you can see that Master Page
Gallery permissions are not inherited from site collection
permissions.
Give here the Contribute permissions to Style Resource Readers (or
modify it as you'd like) and all users will have access to this web
with no permissions to edit etc..
I had a similar issue and the thing I noted in your Environmental comments was the custom master pages. Go to your Site Settings and ensure that your custom master pages have been published. If you need to publish them also check the corresponding html pages after they have been published as they may need to be republished also.
This worked for me.