New answers tagged

0

Do you have a link to an example in Sharepoint 2013? The blog you share shows screen shots from the SharePoint 2010 process and I'd love to find an example that walks through 2013. Thanks!


0

Limited Access means a SharePoint user or group has permissions to an item or document or page or library within a Site, but does not have permissions to the entire Site. This is normally used when you want to share content that resides within a site with users but not allow to browse the site. See the following Microsoft TechNet article for further help ...


0

View Items Permission gives only view permission to the Items present in library like below. therefore you can see the name of file only. Actual file is associated with the name and for that Open Item permission is required.


0

Here are my findings: check everything to make sure that your account has permissions for editing in the SPD in the SPD, reopen any closed sites that you had opened before. Then click on the user icon at the bottom left to logout the current user. retry to open the site to edit with your account. Hope this help.


0

I had same issue, so I had to give contribute access to workflow history list http://yourSitePath/Lists/Workflow%20History/AllItems.aspx


0

Check if these users have a unique permission for a specific list within your sub site. to check permission for specific users go to site settings > users and permissions > Site Permissions Also, you might need to run Full User Profile Synchronization service from Central Administration.


0

You can't view a list in datasheet view with read only permissions. Are they able to view the items in a standard list view? – Nate 12 mins ago


0

This is by design, users with read only permission can't get into a datasheet view because that is an edit operation, as evident when you up their permission to contribute. Set the default view of the list to a standard view and they can see the data.


0

The simplest answer for what will be his actual access on this site ? He has a Full Control because it's the highest permission level Check also, Understanding permission levels in SharePoint


1

The highest level permission level will take precedence. In your case, the user has Full Control permission. Similar answer here More on SharePoint permission levels


0

You can propably bypass the active directory and use the ms sqlserver login accounts. Please check the link below SHAREPOINT 2013 LOGIN WITHOUT ACTIVE DIRECTORY


1

The local user is not imported to SharePoint User Profiles. Hence you are unable to login using local user account. You can add local users who belongs to the SharePoint server but not users on the remote client machines. Alternatively using SharePoint User Profiles you can create users and use that for login.


1

SharePoint Office 365 Admin has full control of every object. There is no way you can remove that. One option is to log details of users who are viewing the list/library. You can add JSOM script to capture this information. Also you can put a redirect logic in the pages so if the user is not part of say HR SPGroup then redirect to an access denied page.


0

It seems you are not using inherited permissions. Check the list you are talking about has unique permissions and if that is the case add the Portal Owners group into that.


1

I was faced with the same issue in a workplace that did not understand exactly how Microsoft products work and the answer is no, the administrator has higher power for a reason. What we have compromised on is to have a third party application that monitors accesses and creates daily/weekly reports so that every intrusion by administrators is justified before ...


0

Below worked for me: Steps: 1) Open Excel File. 2) Go to ribbon, select DATA and select From Other Sources, and click on From OData Data Feed. 3) In ‘Data Connection Wizard’ form, provide appropriate REST link and click on Next. REST Link format to get Sp Group users: https:// Your SP2013 Site /_api/Web/SiteGroups/GetById(9)/Users 4) In Next form, ...


0

You need to elevate Workflow permissions in SharePoint 2013 by doing the following : Allow workflow to use app permissions. Grant full control permission to a workflow. Develop the workflow to wrap actions inside an App Step using SharePoint Designer. For more details about How to apply the above steps check The Workflow was Suspended with Unauthorized ...


0

I would suggest creating separate document libraries with required permissions and move the documents from main document library through workflow. Workflow can use the tags attached to a document for making the decision of where to publish.


0

There is no CSOM API for granting app permission so far in SharePoint. A possible way is parsing the appinv.aspx page and submit the form in code ( Don't forget set the appropriate user-agent). I can provider a c# code snippet which works fine if you are interested.


0

When SP User requests access to a Site and you allow it, he/she is added to Site Members Group. What you can do, just to add Everyone to that Group :) STEPS: Site Settings People and Groups YOURSITENAME Members New Add Users Everyone


0

The "Read items created by user" and "Create and edit item created by user" settings override item-level permissions. The only I've found to allow users to view items created by someone else is to grant Manage List or Full Control over the entire list. As you suspected, you'll need to disable the custom Read Access and Create/Edit Access settings and use an ...


1

I don't need to give you academic definition but you should follow the mentioned steps below to check the difference between all permissions level types not only Full control and Contribute Go to site settings > users and permissions > site permissions. From the above ribbon select permission levels You can check the difference between all ...


0

In order to manage permissions for a folder or list, the Manage Permissions capability is required. There are only two permission levels that have this capability by default: Full Control, Manage Hierarchy you can check the settings here at https://yourdomain/_layouts/15/role.aspx


0

In case of managing specific items I think both full control and Contribute has same permissions. Contribute permission level does not have rights to Manage list so you can't use it to manage permission or list setting for the list or library. To manage permission for folder or list you can use Full control or Edit permission level


0

Full Control permission level: Contains all available SharePoint permissions. By default, this permission level is assigned to the Owners group. It can’t be customized or deleted. Contribute permission level: View, add, update, and delete list items and documents. Reference


1

I did something like this, but it was just a list so it may or may not work. I gave everyone create rights to the list. When the created an item a 2010 workflow fired off. I gathered there department info and set it to a variable. It then would look to another list that had a list of departments in one field and in a corresponding field users that where ...


1

You can use Powershell to reset inheritance $webUrl = "http://mycoolsite" $web = Get-SPWeb $webUrl $list = $web.Lists["mycoollib"] foreach ($item in $list.items) { $item.ResetRoleInheritance() } Also to get items that do not inherit permission you can use following powershell script $web = Get-SPWeb "http://mycoolsite" $list = $...


2

One of my favorite ways to automate repetitive tasks is to use PowerShell + CSOM. The Client Object Model allows me to run my scripts on top of on-prem SharePoint or Office 365 using the exact same code, so I don't have to migrate it in order to make it run in one or the other. Here is an example of how you use the client dll in a PowerShell script to ...


0

Maybe it's this user policy thing: see this technet blog Solution: If you set the Super User & Reader Accounts to a domain account for the Web Application(s) using PowerShell, make sure they have been added to the Web Application(s) via Central Admin with the appropriate rights. More Information: By default, the Portal Super User account ...


0

Resolution : have site collection access, define a new level permission, test it, do a powershell script to copy/past it on each site collection.


0

Yes, you are right. It is best practice to create security groups and assign these groups rights in SharePoint, for once the security groups have been correctly configured there is no need to return and fiddle with SharePoint securities if new users get added for example. Read more here: Using Office 365 security groups with SharePoint Online


0

You have two supported options: Add JavaScript through UserCustomAction, which check if it's the sbnewweb.aspx page and if to sets the radio button and hides the section Add css (through AlternateCssUrl) to the site which hides #ctl00_PlaceHolderMain_idPermSection and have an event receiver to break inheritance (and set AlternateCssUrl) Finally if you ...


0

Options: 1) Item level security Set-level security item list. This allows to reach the maximum level, but it has two problems. It is complex to administer. On the other hand you can meet with the ceiling of security elements in a list. 2) Item level security (c#) The second option is a variant of 1. You can set permissions from an event handler. The ...


0

Give your users "Edit Items" permission as well. Since you mentioned that you do not want the users to edit the form you can either Create another second list. Give users permission to edit the list 1 but not list 2. Use your workflow on list 1 to fire the email and also copy data from list 1 to list 2. You can secure the second list by not giving your ...


0

This site shows the permissions that should be checked in the Contribute permission level. Go to permission levels on your Sharepoint account, click on Contribute and make sure that those permissions under Contribute permission level is checked.


0

You need to elevate Workflow permissions in SharePoint 2013 by doing the following : Allow workflow to use app permissions. Grant full control permission to a workflow. Develop the workflow to wrap actions inside an App Step using SharePoint Designer. For more details about How to apply the above steps check elevate Workflow permissions in SharePoint ...


0

In case of you got “The server was unable to save the form at this time. Please try again.” for all users. SharePoint Search Host Controller service may need to restart to free up some memory space. Anonymous Authentication was disabled in IIS. “minFreeMemoryPercentageToActivateService” attribute is not set to serviceHostingEnvironment Tag in Web.Config. ...


0

If the workflow is sending an email, check to see if the email is being sent to a group. If the group settings do not allow everyone to view membership, you will get a suspended workflow.


0

Regarding your error message, Retrying last request. Next attempt scheduled in less than one minute. Details of last request: HTTP Unauthorized to [site]/_vti_bin/client.svc/web/lists/getbyid(guid'5427d1e2-d15c-47db-aa39-8c77a1a1b879')/Items(2) It looks a permission issue and you need to elevate workflow permissions


0

You can use "AppOnlySequence" from the workflow toolbar to run any workflow activity with elevated permissions. Note: In Visual studio this option is under SP-Utilities header on workflow toolbar.


0

I think you can use Powershell to add bulk several users at a time Bulk User using Powershell or you can use csv file. Microsoft provides a template which you can download and add users into it. Adding Bulk User using CSV


1

BreakRoleInheritance has two params. Just use false and true for copyroleassignments and clearsubscopes respectively then add the groups you want: $list.BreakRoleInheritance($false,$true) $group = $ctx.Web.EnsureUser($group) $roleDef = $web.RoleDefinitions.GetByName($role) $ctx.Load($group) $ctx.Load($roleDef) $roleBinding = New-Object Microsoft.SharePoint....


-1

Please check the following code $web=Get-SPWeb http://site url $list = $web.Lists["list/library name"] [Microsoft.SharePoint.SPRoleAssignmentCollection] $spRoleAssignments=$list.RoleAssignments for([int] $a=$spRoleAssignments.Count-1; $a -ge 0;$a--) { if($spRoleAssignments[$a].Member.Name -eq "groupName") { $spRoleAssignments.Remove($a); } }


0

I tried asking around in other forums, and was told that this happens with folders by design, and using document sets instead would be a good workaround. The document sets seem to be working so far, so I think that's what I'll use. Thanks for everyone's help! Source: https://social.msdn.microsoft.com/Forums/sharepoint/en-US/3ebdb5e2-5d42-4817-a779-...


0

The user will need at a minimum read permissions to the library. If they go into the library, they will only see the folder they have permissions to. If you want them to be able to edit files, then you'll need to give them read access to the site. What exactly is being called by the client applications (Word, Excel) I don't know, but in testing super ...


3

You are miss-using SPSecurity.RunWithElevatedPrivileges. You need to create (and dispose) new SPSite/SPWeb objects inside the elevated section. Using contextual objects inside the elevated section has not effect on these objects: they're still old SP objects opened with the permissions of the initial user... See for instance the second part of http://...


0

It's only hypothesi : your list is from a custom list template ? (if yes, your custom list template may have been deleted). May be there is Lock on all your items. you start workflows on your items, The Workflow Manager Lock you item, do the stuff and release the lock. You have started 50 workflow in the same time, may be the workflow manager crach and do ...


0

As site collection administrator, is your account a system account? You can check simply, if you have sys account, your name/id is replaced by word 'system'. Thing is system accounts treat several things differently, e.g. they can edit list items without changing modify date. If your WF was running under such account it may have caused some trouble in ...


0

This can be done based on web part permission .Usually all the web parts inherit from site collection permission. Go to Webpart gallery from Site Settings and remove inherit permission for the particular Webpart . So that only Site Collection admins will have permission to that Webpart .This Webpart will not visible to other users.


5

You will need Full Control permission level to be able to edit a MasterPage in SharePoint Designer 2010. Reference: User permissions and permission levels (SharePoint Foundation 2010)



Top 50 recent answers are included