Hot answers tagged

3

You could require content approval and turn on track changes. (In Word 2013, you can require a password to turn off track changes.) Then the person who has to approve the document can accept or reject individual changes once the document comes to them. Or, there's a "collect feedback" workflow that will route a document for comments.


3

I don't think it is possible OOTB. There is a workaround for it. If you have either Site collection backups or Content Database Backup then you can restore it from before the Inheritance enabled. Or if you have any security related reports then apply the setting manually.


2

That is happening because you are running an service app pool as Network Service or Local System. That account with the $ at the end is your servers identity. You can either authorize that account to access the data or run you service applications as a user that is authorized to access the database. if your Central Admin site root was: http://ca/ then ...


2

You should be able to use SharePoint's draft item security here. Within the document library settings, select versioning settings then select the following: Require content approval for submitted items - yes Create major and minor (draft) versions Under draft item security select 'only users can approve items (and the author of the item). Ensure that ...


2

yes...there are two ways.. one is via coding where if login users are same as CreatedBy field than the documents will be visible or if user is with Owner access he will be able to see the documents. second is via out of box...create two views... One view display all documents and set its Audience Target to be only Owners... And create a second view where ...


2

To work with server , you can't use another machine to deploy solution. You must need to login to server and develop solution there only.


2

If you reestabilish the inheritance, the folder with broken inheritance will keep the broken inheritance. So, it doesn't break unique permissions on children. Anyway, you can try it yourself simply creating a new test library and setting and breaking inheritance. I tried it my self too...


1

What I would do is completely different than what you may have in mind, but I would create an event receiver that would capture any edits/additions, and then copy them to a separate anonymous site. That way the content between each site will be segregated and no funny business would be allowed. You could also just create a PowerShell script that runs once ...


1

This is how to set permission to individual list item on SharePoint 2013 Select individual list item. Click "Share With" button on "ITEMS" ribbon menu. Click Advanced and assign a user or group. Hope this helps!


1

I believe that only the Manage Lists permission is required (at the library level)


1

Can you try this code snippet public static void getPermissionsOfFolders() { using (SPSite site = new SPSite("http://sp")) { using (SPWeb web = site.RootWeb) { SPList list = web.GetList("/Lists/List2"); foreach (SPListItem item in list.Folders) { ...


1

This is expected behaviour If you are Farm administrator but your account is not in local admin on the server. By default, Farm administrator don't have full control on the Central Admin i.e as Farm Admin you can't create the web application can't change the service account etc. The reason is, some activity required local admin rights on server i.e when ...


1

The user who is installing the app that has tenant level permissions should be tenant administrator.


1

<script type="text/javascript" src="../../JSLibrary/jquery-1.3.2.min.js"></script> <script type="text/javascript" src="../../JSLibrary/jquery.SPServices-0.4.8.min.js"></script> <script type="text/javascript"> $(document).ready(function () { var managerName; var userName = ...


1

If you run your code under elevated privileges, user can see everything but then you need security trim(depends on your security rules) parent site. If you just show tree, I might be OK but if user clicks tree node and if user runs some processes based on this click, you need to security trim to your tree and you should be careful that because easily you can ...


1

You could make a separate list (i'd use a discussion board) that ties to the document library through a lookup column to allow users to make comments/questions on a specific document. This separates the concerns of users having access to edit documents that they don't need to edit.


1

You can do it by code also: if (SPContext.Current.Web.CurrentUser.Groups.Cast<SPGroup>().Any(g => g.Name == "hr Group")) { show button } else { hide button }


1

SPGroup.ContainsCurrentUser() is also an option. You can get the HR group as usual and check if the HR group contains the current user. Then, it's just about hide/disable that button.


1

To achieve what you want you should stop inheriting permissions in the subsites. Then you can remove all the reading permissions for the users in the subsites. Doing users will not see and cannot enter the subsites


1

If we're talking reports from SSRS, then an option would be to create a document library for each team and secure it as desired. In the configuration of each library, email enable the document libraries with unique email addresses. Then on the SSRS end, configure the reports to be emailed to this email address. The reports will end up in the respective ...


1

You need to open the "Shared with" menu from ribbon, go to "Advanced settings" from there, "Remove Inheritance" from the edit permissions page that opens from there. Now you could add/remove users from this page. However I must suggest you to use groups of users (instead of individual users) to grant permissions here. So when you need to grant permissions ...


1

It may make sense to allow a group of people access to a single list or library within a site collection without giving them access to other resources on the site collection, including the site’s home page. It is easy to break inheritance to the library, create a security group for the library and add the people to the group. However, this has side effects ...


1

If the sub sites are inheriting permissions from the root parent site.then giving permissions at the root site via group should be sufficient - simplest way If not there is no other easy way as you need to give either manually to each sub site or write a custom powershell /C# console via object model or CSOM and give the permissions through code.


1

I reviewed your code but i think your top bar control should be within SPSecurityTrimmedControl Tag not CssRegistration Tag. Please go through this article Hide ribbon from users without Edit Permission let me know if this is helpful or not Thanks


1

If you can use custom solution then please refer the following steps Create a custom SharePoint solution Create an Event Receiver with ItemAdded and ItemUpdated event In the event handling use BreakRoleInheritance(false) function Now set the custom permission which you want over the item created and iten updated The problem which might be exists here is ...


1

It is not possible to have cascading dropdowns (behavior that you are describing) in OOTB SharePoint forms. There are third party solutions (both farm solution and add-ons) that add this functionality to lists. You can also have a look at SPServices jquery library and add this functionality yourself to the form. This does require some javascript development ...



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