Tag Info

Hot answers tagged

3

If you love the Powershell. Then you create a new Permission level call add-only and assign this permission level to all user who you want add items. Give other person(who can view the items) as full control/ edit or whatever you want to give them You can create an add only permission level using the following PowerShell script. $spweb=Get-SPWeb -Identity ...


2

In order to manage unique permissions for a Securable Object like List or File (via associated List Item) or Folder (via associated List Item) there is a common approach that you could consider: Break role inheritance for a securable object Add/remove the role assignment on the securable object [optional] How to: set unique permissions for a File via ...


2

You could also mimic this functionality with a drop-off library (part of the Content Organizer for all 2013 versions, including SharePoint Online) -- having it move all of the documents there somewhere else after they are uploaded. Then you could have whatever permissions you wanted on the destination libraries


2

Yes you can do this through Permission management. Remove everyone permission after uploading it. The farm administrator will be able to see it anyway.


2

You can use the SPRibbon.TrimById(controlId) method to hide controls. You can use other OM methods to determine the user's permission and call the TrimById method accordingly. For example, you could use DoesUserHavePermissions on the page's list item: ...


2

Option 1. SPWeb.GetSubwebsForCurrentUser method SPWeb.GetSubwebsForCurrentUser method gets the subsites beneath the current site of which the current user is a member Since it retrieves only beneath the current site(1 level only), you could use the following method to return all web sites that are contained within the site collection: private static void ...


1

You can use following : using(SPSite site = new SPSite("http://example/site/")) { using (SPWeb web = site.OpenWeb()) { SPWebCollection webCollection = web.GetSubwebsForCurrentUser(); } } This will give you the list of all webs for current user.


1

The issue you have is, you are looping till index i reaches RoleAssignment count and within the loop you are removing the RoleAssignment one by one. This means, the loop count decreases by one. So, on every run, it will only loop half the total no of permissions. So, you have to run multiple times to delete all permissions. What you can do is create an ...


1

You'll need to make that insert into list B as an impersonation step. This used to be an option in 2010 that would allow workflow actions to execute as the user who publishes the workflow. I'm not very familiar with 2013 yet, but I believe this was moved into a feature that isn't enabled by default called an App Step. See if this article helps you, ...


1

I have done several solutions to this. It's simple ... Just open the SharePoint Designer, open your SharePoint, go to "All Files", after that click "_catalogs" then "masterpage" and open the "seattle.master" in Advanced Editing. Go to more or less line 90, will contain a div with the id "suiteBarRight". Within this div contains all the menus of the ...


1

Are you looking for a no-code solution ? If you are OK with using JQuery or CSS and If you are Using custom master page, you can refer the CSS in the master page so that the link is hidden on all the sites. If you are using the default sharepoint master page you can use a delegate control to inject Jquery/CSS without modifying the master page. Here is a ...


1

You have to break the permission of the list, create a new role and assing it the to group. Then assign the role to the list. $list.BreakRoleInheritance($True) $group = $web.SiteGroups[$GroupName] $roleAssignment = new-object Microsoft.SharePoint.SPRoleAssignment($group) $roleDefinition = $web.RoleDefinitions[$PermissionLevel]; ...


1

thats because anonymous uses are still based on limmited access. have you disabled -> "limmited-access user permission lockdown mode" its a feature within sitecollection that is enabled by default. That should solve your issue. if its still an issue follow this simple guide to setting up anonymous access to your site collection.... its a few areas that ...


1

Although it's not exactly your case, take a look to this link, cos I think is related with your error: http://blogs.msdn.com/b/chandru/archive/2010/10/15/sharepoint-2007-getwebcollection-webs-asmx-does-not-return-webs-based-on-a-user-permission.aspx. Regarding the link, it seems that the method GetWebCollection, actually returns all the Webs, doesn't ...


1

You can break the inheritance of the list, and set the users with a custom permission created by PowerShell with "Submit only" permissions. $spweb=Get-SPWeb -Identity "<site url>"; $spRoleDefinition = New-Object Microsoft.SharePoint.SPRoleDefinition; $spRoleDefinition.Name = "Submit only"; $spRoleDefinition.Description = "Can submit/add ...


1

Our company contacted Microsoft, and this is by design. For security reasons you cannot set the permissions of an app by client side code


1

My solution is dependent on Workflow. Here is solution: Create a Content Type for the Helpdesk Create a Reusable Workflow for the Content Type Add Content Type to lists you wish and make it default Since you are using Content Type so you just need to attach it to the every list you want to behave in similar way.



Only top voted, non community-wiki answers of a minimum length are eligible