I'm creating a site that will have people that work for my company using it( on the domain) and contractors who are not currently on the domain. I'm trying to figure out how to give access to the people who are not on our domain to the Sharepoint site.
Can someone point me in the right direction?
You need to set up a zone with Forms Based Authentication for the people not on the domain.
Look at this series on MSDN for guidance: Forms Authentication in SharePoint Products and Technologies
To bring this answer up to date (2018), the features are now available in Sharepoint Online/Office365:
https://support.office.com/en-us/article/manage-external-sharing-for-your-sharepoint-online-environment-c8a462eb-0723-4b0b-8d0a-70feafe4be85
Related
SharePoint Admins in Microsoft 365 can create Team Sites and Communication Sites using the admin center.
In addition, individual users can have Personal Sites (Otherwise known as My Sites)
Using the Microsoft Graph .NET SDK I can retrieve all sites like this:-
await client.Sites.Request().GetAsync();
However this appears to include all Team, Personal and Communication Sites. Is there a way to limit the request to only one type of site, or detect the type of each site returned from the query? I could not find anything in the documentation about this.
Edit: If there's a way to get this information via SharePoint CSOM, I would be interested in that too
Unfortunately this is not available as of now but there is a uservoice already raised. Please upvote it so that this feature may be implemented in the future.
I don't know if it can help you but I found a workaround how to differentiate between a team/communication site and a personal site.
A personal site contains in the WebUrl field the string "my.sharepoint.com/personal/", then after you make the call: var sites = await client.Sites.Request().GetAsync(); you can use this filter to retrieve only personal site: var personalSites = sites.Where(s => s.WebUrl.Contains("my.sharepoint.com/personal/")); (Microsoft does not allow to use a filter on this request directly, so this is the reason why I used the filter after fetching all sites.)
I started a modern team site in SPO and added lots of pages and link to them in the quick link.
Now the users want Mega-Menu instead of the quick link.
I tried to copy the pages to a new communication sites that has mega-menu but there is a difference in the site template that does not let me do it.
I also tried to get the rest call to create the menu with jQuery.
https://{mydomain}.sharepoint.com/{musite}/_api/contextinfo tells me:
Access denied. You do not have permission to perform this action or access this resource
Is there a way to query the quick link and build a mega-menu?
Any good we to transform a team site to communication site?
Thanks in advance
If your team site is a classic team site then no, you can't have a megamenu unless you make a custom one.
IF your team site is a modern team site then you inherit the megamenu from a hub site I believe.
I have a feeling you have a classic team site with modern pages in it.
Is there a way of getting usage statisics across my whole Sharepoint 2007 portal?
I can get the figures at a site level by appending _layouts/SpUsageWeb.aspx
to the path, i.e. http://intranet/teams/hr/_layouts/SpUsageWeb.aspx for the HR page or http://intranet/_layouts/SpUsageWeb.aspx for the front page.
What I'm trying to do is see how many unique users access the portal (across all the sites it contains). Using the above method on each site and summing the total users for each doesn't take into account users who visit more than one site.
I've seen commercial tools that seem to do this but surely there has to be built in functionality that does this for a product as all-singing-and-dancing as Sharepoint?
The URL of the site collection statistics page is http://intranet/_layouts/SpUsageSite.aspx.
This functionality does not exist in SharePoint 2007. It was added to SharePoint 2010. You can now report on stats in central admin for web applications etc.
I'm attempting to justify this functionality to my boss.
So as the title says, what are the advantages of mySites in SharePoint 2007?
We were exploring the use of MySites as a repository of useful information on the employees. As an example, I could convey my skill set through MySites (i.e. ASP.NET, JavaScript, etc.) and then someone else could do a search for that skill set and be presented with people like myself. You could do the same thing with project experience, etc..
We were also exploring the possibility of importing information from AD and our HR database, associating it with employee profiles in SharePoint, and then making that information accessible through search. You could see the organizational hierarchy, phone numbers, departmental information, etc..
Lastly, individuals can use MySites as a way of sharing information (Word documents, etc.) with other employees. This is an alternative to emailing documents, hosting them on network shares, creating shares on desktops, etc..
Unfortunately we hit a road block (huge changes in the company) that have put this initiative on hold - but we were really excited about doing this and it seemed like a real possibility as we began exploring the functionality in dev.
For me SharePoint 2007 MYSITE is a central location to manage and store users' documents, content, links, and contacts.
SO far I have not explored other possibilities.
Just need to use find a simple way to have AD authenticate as the login for a Sharepoint site. This fairly quick and simple to get going ?
Thanks!
For SharePoint 2007, see this article. You probably want to set it up to do Windows integrated authentication with NTLM. Getting authentication working is probably not too hard, getting your site setup the way you want with permissions/authorization working probably isn't. Depends on how complex your site is. I wasn't directly involved but I know that it took a few months to get our intranet up and bug free.
One recommendation that I would have is to use AD groups or SharePoint groups that contain AD groups rather than individuals to control access. It's much easier to clean up AD group membership when an individual leaves than to track down all the places where you've given them individual access (including membership in SharePoint groups).
You need your server to be part of the domain before installing SharePoint.
If you do that, the default configuration will be AD authentication.
Here is a decent discussion of SharePoint security links
http://blogs.msdn.com/joelo/archive/2007/06/29/sharepoint-groups-permissions-site-security-and-depreciated-site-groups.aspx
Essentially, you will either need to add users to the appropriate SharePoint group. The defaults for a site are generally xxx_Visitor, xxx_Members and xxx_Owners, with each group having increasing security rights.
You can either add an AD domain to these groups or else add individual AD users