Tag Info

New answers tagged

0

Check the List settings under Advanced Settings – Item Level Permissions – Read Access. If the Read Items that were created by the user option is selected, the anonymous access cannot be activated.


1

I would just make one document library with three folders, uninherit those folders to make unique permissions, and then create a workflow that takes the document and moves it to a different folder. You can create a view that looks at all documents and the folder it's in.


0

I would like to understand why you would do all this work to make a web part that is viewable by only a few users where all users can see the content, if the content has not been granted unique permissions. What is the requirement? Also, I have, for SharePoint 2010, lately been seeing lots of permissions issues where customers are setting unique permissions ...


0

Unless there is no content being dropped into your page (via web part), you will also need to control permissions of the content. Or people will be able to see the content via the "View All Content" or by simply typing "/_layouts/viewlsts.aspx" in their address bar. Oddly, people often are surprised, after dropping content with unique permissions into a ...


0

i have the same situation, in my case i have 3 sites sharepoint (internet, clients [Extranet], employé [Intranet]), so, i using anonymous access for internet site, and of course windows authentication (active directory) for intranet, and for clients (external users) i use Forms-Based Authentication with SQLMemberShipProvider like that i separate external ...


0

This looks loke something I would do in a few steps. 1 hide the list as @Dolgsthrasir suggests 2 manage permisions for the list / or make specific views for the list remove the read but now write from users. List permissions with PowerShell 3 Provide a quick link for users to contribute to the list / handle it via your application If the PowerShell ...


2

So I figured out that the html for the "PurchasingSearch" page was not published. Both the .js and the .html need to be published.


0

Another option that I have found for restoring a site collection to a different domain to the source domain (and where the source site collection cannot be set up with the site collection admin for the destination domain) is to grant the user account doing the restore access to the web application. $w = get-spwebapplication http://[urltodestinationwebapp] ...


0

Use the impersonating step in the workflow, so you don't need to worry about the permissions. It will skip the permissions but still having your users as the level restricted you want them.


3

If you only want to hide the list from "All Site Content", the SPList class has a "Hidden" attribute. If you set this attribute to true, nobody will see the list via "All Site Content", but you can still access the list with the direct link. You could set the "Hidden" attribute with Powershell or a console application, for example (or do it at feature ...


1

In a feature event receiver upon FeatureActivating, get a handle on your list and set it to hidden, http://msdn.microsoft.com/en-us/library/office/microsoft.sharepoint.splist.hidden(v=office.14).aspx This will hide it from the All Site Content and still give users the ability to add items to it. If anyone did know the underlying list name, they could ...


2

You can use spsecurity.runwithelevatedprivileges to edit the list from the application. Go through the below link on how to use the above method. No need to give user any special permissions. Give edit permission to the application pool account. That should solve it. If you want to save the user name as well in the list you can do by creating a new column ...


0

If you want to set permissions on a single page within a site then: In Site Content go to the Site Pages library. Then set the permissions on a page level the same way you would set permissions on a document, folder or site. i.e Click on the ellipses next to the page name and Share it with only one person.


1

Break permissions from top site. Then either make a new SP group and add a user to the group or Invite a user to the page and give him permissions. First method is much easier to maintain in the long run. Worth remembering: The Top level admin can read this page and if you are using SharePoint online the global admin will still be able to read ...


2

You are out of luck. a SP group cannot contain any other SP group. It’s a big limitation.Although SharePoint groups can contain (AD) users and AD groups. Check this Technet: http://technet.microsoft.com/en-us/library/cc262690%28v=office.15%29.aspx http://www.spdockit.com/blog/permissions-management-sharepoint-2013-part-two/


4

No, that is not permitted. You could add security groups into the Sharepoint groups if they exist though, distribution lists are not supported.


0

Try getting the listItemAllFields object for your Folder which will have the get_roleAssignments() method on it. Then you can use the .get_roleAssignments().add() method to assign a user to the right role for that object like in this MSDN sample: "How to: Work with Roles Using JavaScript" You'll need to load it first (with another call to load or with an ...


0

According to this link, this is expected behaviour if a user has never previously accessed SharePoint... Check Permissions queries the UserInfo list to retrieve permissions and if a user has never accessed SharePoint, then they won't exist in the list and the Check Permissions would return "none". This is true for all versions of SharePoint 2010 and 2013.


0

Taking a new initiation form we get the workflow to work. So what's the difference? The old form had within its PlaceHolderMain section an WebPartPages:WebPartZone tag. Probably it was copied from another aspx and this led to the sorry error message. So take care what you are doing within an aspx on one hand but on the other hand Microsoft could deliver ...


0

Go to List Settings -> Advanced Settings -> Create and Edit access. Check option: Create items and edit items that were created by the user


0

Usually the way I would get around this is assign an administrator (really Edit Rights) to a power user that will use this the most, or someone that is a SharePoint savvy user. Also, make it known on SharePoint that "User A" has the keys to that document library. That way it falls out of your hands, and gives the users drive to use the company's ...


0

this is default behavior. two things you can do it. Create the another permission level copied from Read Permissions level and add Manage Permissions. this will allow the user to share the doucments but it will give them the ability to share withfull control. other way is enable the "allowing the Access Requests" will be the best options. ...


1

Mike's alternative is the easiest to implement. You can also implement a Web Service to do the required actions for you and lastly (and I guess what you really want), you can try to implement the calls listed in this article in successive HTTPSend activities. The JQuery version of the REST calls are listed below. // Change placeholder values before you ...


1

The "contribute" access rights consists of "add", "modify" and "delete" access rights. You may try to create a customized access right to allow only "modify", i.e. without "add", nor "delete" access rights. User who is assigned to this customized access rights would be only able to update the existing entries in the list, so as to trigger a workflow, but ...


0

Custom Action declaration have EnabledScript property, where any valid JS function can be placed, it can check any conditions and should return true or false. So VisualStudion is needed or direct access to sharepoint filesystem so one can modify proper ribbon xml declarations.


0

I've been able to apply unique permissions on a SharePoint 2013 list item by creating a new SharePoint 2010 workflow. This allows you to use an Impersonation Step. Here is a screenshot of the configuration for this step. As long as you've broken inheritance on your list this should work.


0

Assuming here that the App has deployed an App Web you could check the EffectiveBasePermissions. Something like context = new SP.ClientContext.get_current(); web = context.get_web(); this._currentUser = web.get_currentUser(); context.load(this._currentUser); context.load(web,'EffectiveBasePermissions'); ...


0

Go to another view of the list and try to delete the item from there. It could be an issue with the view


0

Attach a event recevier and add item added / updated event to it for assigneing permission. First break permission on item and then add required permission as per item status / metadata.


1

One way of elevating code is, as you already mentioned, using SPSecurity.RunWithElevatedPrivileges which will run SPSecurity.CodeToRunElevated with Full Control rights. From MSDN documentation of the method for SP 2013 (http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsecurity.runwithelevatedprivileges.aspx) you can see that this code runs ...


0

Yes in those cases you should elevate the code, do the operation. There is no other way around this.


0

The issue is that my environment allows both Claims and Forms authentication. Because of this, it is necessary to convert a LoginName to a WindowsClaim. I did this by hardcoding "i:0#.w|" to the start of the LoginName and everything worked. I don't know if this string is the same for everyone, but you can find it by looking at the details of a user that ...


2

You need to Stop Inheriting permissions from the parent site, and then you will see Anonymous Access option, click the option and set to None.


1

I made this same mistake and selected the two key users who would be administering the site in the future, assuming my domain admin account would still be able to log into the site. In Central Admin, go to Application Management > Change site collection administrators. Set one of them (primary or secondary) to yourself.


0

Set permission in site scope(for that user can access library): site actions -> site permissions -> Grant Permission -> choice user and select only the permission "Contribute - Can view, add, update, and delete list items and documents." UPDATE: Set permission in list(InfoPath): Library Permissions -> add user with full control. this permission ...


0

I'm a complete idiot. Permissions were trimmed for the list and I overlooked that. Once I added the new group directly to the list everything worked. No mystery to solve here.


0

You need to set the Credentials of the Report Data Source please refer to http://msdn.microsoft.com/en-us/library/dn198312.aspx for details on this. We use a single database user account (the 'ReportUser') and stored credentials. This has been inherited from our stand alone configuration and works fine in SharePoint. Report Builder is running fine because ...


1

I assume you do have the group in another site collection where you can look up what permissions the group have, and just create a new group with the same permissions. Go to another site collection where you got the group intact and go to Site settings > site permissions > permission levels. From here select "Style resources reader" to see exactly what ...


0

Instead of changing the STS configuration as suggested in the blog posts, I'd suggest to just clear the Logon Token Cache. Clear-SPDistributedCacheItem –ContainerType DistributedLogonTokenCache


1

Powershell You can use Remove-SPUser command as shown below: Remove-SPUser "Contoso \jdoe" -web http://test/web1 The following script can also be used (and converted into relative C# code) Function RemoveUser($LoginName,$SiteUrl) { #Get site $Site = Get-SPSite | where {$_.url -eq $SiteUrl} If($Site) { $Web = $Site.openweb() ...


1

you can set the filter on the list view, like this Having done that set the modified view as default and delete all others views, as administrator create a new view but as Personal View, so only you can see it. And for disable the alerts, follow this link None of this solutions are 100% efficient if the user are not set in groups Good louck with that.


0

I was only able to solve this after filing a ticket with microsoft. Their solution was to delete my root site collection and then re-add it as a team site. After that I was able to enable publishing features.



Top 50 recent answers are included