New answers tagged permissions
1
Have you broken permission inheritance anywhere in the site collection?
When permission inheritance is stopped anywhere within site collection, then ASPX pages (and its content) in that site collection will not be indexed by default.
This is a security feature implemented to prevent users from using the search to view information where they don't have the ...
0
It turns out that someone had changed a setting on our authentication provider. The SSL parameter for the Stage endpoint was set to only accept certificates. The accounts that were unable to reach the Stage environment were all non CAC accounts, so the setting to also allow Kerberos was changed, and we were back in business!
Hope this helps if anybody ...
1
Check under WebApplication permission that your crawl account has Read Access.
In Central Admin:
Application Management --> Manage web applications --> Click the line
of the web app --> In Ribbon "User Policy"
Make sure that the Search Crawling account is added as Full Read
1
Your site collection admins will be able to do anything and everything that SharePoint allows, including the creation of SP groups. You can turn this off at the web application level, but it doesn't sound like that's something you want to do to all of your other site collections. I think the basic issue you're running into here is that anything you set at ...
1
What you're looking at are the primary and secondary site collection administrators that you set upon initial site creation. In addition to being added to the site collection administrator list cited by John Chapman, their logins are also added to the site fields "Owner" and "SecondaryContact". This can be useful in situations where you need to be able to ...
1
To answer your first question -> When you grant a specific user permissions to a site, they are added automatically to the hidden User Information list.
As far as an Active Directory group -> The group gets added to the hidden User Information list, but the user does not get added until they access the site. (As an example, I granted an AD group ...
0
Leave full control for your "super admins", and then create an "Almost Full Control" permission level for your regular site owners. Your group of "super admins" would have to include the site collection administrators though - I don't see a way around that.
0
It really depends on the business role of the security officer. Ideally, permissions should only be given through the portal or even better through powershell.
While, powershell requires local administrator rights on the farm, its better to do it through the portal in the web browser.
What you essentially need is a site administrator with manage ...
1
Management of public views requires the Manage List permission. You can create a custom permission level or use one of the out-of-the-box permission levels that includes the Manage List permission: Full Control, Design, Manage Hierarchy are a few
Keep in mind that Manage List also enables users to manage list columns or delete the list altogether
2
When you add user with permission in some list or library, SharePoint adds the user automatically even if user haven't visit the site, but if you add Active Directory group or role, SharePoint adds the group or role automatically, and when user visits the site then SharePoint adds it.
1
The only way to add more than two is to goto Site Permissions in the Site Collection and select the Site Collection Administrators button on the ribbon.
0
There is a hidden taxonomy list at site collection level which is populated with terms as they are used. The default is for all users to have read access on this list. However, if you start with something like a blank site template and then retro fit MMD then it seems this permission does not always get applied.
Navigate to the hidden list at ...
1
This is called Anonymous access. Here si a guide to enable it for Sharepoint 2010: http://www.topsharepoint.com/enable-anonymous-access-in-sharepoint-2010
There is tons of other material about this on the web, just search for "Anonymous access Sharepoint"
1
I don't have one that takes a specific object as input, but this may help. It will list out the role assignments on web, list, items for users and SharePoint groups.
Start-SPAssignment -global
$sites = Get-SPsite -limit All
foreach ($site in $sites)
{
foreach ($web in $site.allwebs)
{
Write-Host -BackgroundColor ...
1
Your group and permissions are fine. Just on the pages document library stop inheriting permissions from its parent and give read only access to all groups except for Designers and Site Administrators.
3
You can create a custom permission level that allows adding but not editing.
See this MSDN article about how to do that. You will want to copy the contribute permission but remove the edit permissions.
0
Please make sure that you are calling the RunWithElevatedPrivileges() outside the point where you are getting an SPSite reference otherwise it has no effect.
SPSecurity.RunWithElevatedPrivileges(delegate()
{
using (SPSite site = new SPSite(siteUrl))
{
// do your stuff in here
}
});
-1
Please give your search content account access to the managed metadata service application:
http://get-sharepoint.com/2013/04/failed-to-run-flow-microsoft-customdictionarydeployment/
** EDIT: Above I stated content access account, it should be the service account (windows) that's running search. Apologies for confusion.
1
I don't know why this happens but I've seen it before. So much so that when I built my code on top of this I put a try catch in and had it do the command a second time before I was convinced that I didn't work as expected.
1
Dave is right. You might can try to use the migrateuser functionality to see if that will fix the sids for you. Stsadm or powershell
http://blogs.msdn.com/b/sowmyancs/archive/2012/01/07/migrate-users-groups-powershell-script.aspx
2
Not directly from within SharePoint, at least not without close collusion with your AD administrators as well as some aggressive scripting. Besides, you would only be protecting SharePoint and it sounds like this is really a much larger issue that affects the whole company.
A better approach would be to look at your firewall or routing hardware and see if ...
0
you can manually manage the list of users who are allowed to access the site. Instead of using All Authenticated Users create a new Group, insert all of the employees into it, and when they leave/are terminated you can remove them from it.
0
After research on this, I believe there is little hope for a fool-proof method. We adopted an alternate route of picking up a version change in the document, then canceling the workflow if one is detected. This can be done OOTB in SharePoint.
0
One Possible option is to add xsl inline in xsltListViewWebPart. See this blog here -
http://www.manvir.net/how-to-add-xsltlistview-webpart-to-sharepoint-publishing-page
2
Check Site Collection Administrators group.
Check Web Application Permission Policies so that these users aren't included in a policy granting them read/write permission to the web application.
0
I have similar problem but with site. I must edited permission on v4 site.
Maybe other users are in group "Members of this site"?
Anyone have access to this folder? Any user/group?
0
The code snippet above just returns a collection with properties for the root web (and maybee som sub webs..) of the current web, no matter how the permissions has been granted.
To check permissions for every web you would need to retreive the SPRoleAssignment objects from each web and try to find the current user in it. Though this will not work if the ...
-1
If you have followed the guide in this link to enable content approval to hide items from other users until they are approved, my last suggestion is to create a view and only show items which are already approved by everyone.
0
Palani,
Get-SPWebApplication "http://server-name:8080"|Get-SPSite -limit ALL|Get-SPWeb -limit ALL|Select-Object Title,Url,AssociatedOwnerGroup
This will give you Title, Url and the Associated Owner Group for the site... You can than reference the powershell script:
PowerShell Script for SP2010 to pull Farm and Site Collections Administrators
Try merging ...
Top 50 recent answers are included
