New answers tagged

0

Unfortunately no, that is one of the drawbacks. Each time you create an app, the database is actually created in azure. There is no way to separate user’s ability to edit and read various tables. In other words, it does not support role based permissions.


0

Create a form load rule that checks to see if the user is an admin or not, and switch views depending on that condition. For example if current user not admin, switch to Edit view.


1

After further search, we found out that some stored procedures might be used with Microsoft support. Examples of unsupported database changes include, but are not limited to, the following: [...] Calling existing stored procedures directly, except as described in the SharePoint Protocols documentation And the proc_SecResetItemPerm is documented in ...


1

Consider using the Repair method available on SPContentDatabase objects, documented by Microsoft here. You can invoke this from Powershell (once the SharePoint Powershell snapin is loaded) like so: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue $databases = Get-SPContentDatabase $databases | %{ $_.Repair($false) } If you're ...


0

Maybe I'm missing what you are trying to accomplish but why wouldn't you just create a table or div in the top of the in the table after the </sharepoint:SPSecurityTrimmedControl> <!--Hide Ribbon if Read Only Permissions --> <Sharepoint:SPSecurityTrimmedControl ID="SPSecurityTrimmedControl2" runat="server" ...


0

It seems like a permission issue. Make sure the group members can be viewed by everyone and not only by group members.


0

A user with Contribute permissions cannot delete a public view. They need at least Design permissions to do that. Be sure to check the permissions on the list, since it may not inherit the perms from the parent site. don't know that one Why don't you restore the view from your backups? Also, a list view should not be too hard to create. List views are not ...


3

Break permission inheritance of that document library. Remove other users. Then only assign permission to the owners. This will hide the library from other users.


0

I thinks that the SPService is the way to go, it looks like something easy enough to implement, and there seems to be alot of guids on how to. Another question. If one wants to go a step further and populate some of the lists with some external data (make them dynamic), instead of manually create the items. Maybe use some Navision tables to derive data from ...


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 ...


0

[SharePoint Online] I've had this problem too, it was not the App principal that was returned but the site admin as current user. The problem for me was that I had not yet added this to the app manifest: <AppPermissionRequests AllowAppOnlyPolicy="true"> <AppPermissionRequest Scope="http://sharepoint/content/sitecollection" Right="FullControl" ...


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 ...


0

Refer this link: http://spcycle.blogspot.in/2012/01/how-to-create-workflow-to-change-item.html It will show you how to set item permission manually and using workflow.


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 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.


0

You'd need to setup the token timeout expiration. Via PowerShell script it would look like: $sts = Get-SPSecurityTokenServiceConfig $sts.FormsTokenLifetime = (New-TimeSpan -minutes 10) $sts.WindowsTokenLifetime = (New-TimeSpan -minutes 10) $sts.LogonTokenCacheExpirationWindow = (New-TimeSpan -minutes 1) $sts.Update() iisreset Explanation ...


0

Mihail's solution works, but if you really want to make it yourself very easy, I would suggest just giving contributors permission to edit their own items and make all others invisible. You can do that by doing the following: Go to the advanced settings of your list, go to item level permissions and select "Read items that were created by user" + "Create ...


0

I am going to propose a solution that assumes that your list has a person field named Employee and that you have a group called Managers. What you need: A list view called My Employee Info that is filtered to display only the items where the Employee is equal to [Me]. A list workflow that sets unique permissions for each item. The workflow should provide ...


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 ...


0

Use SPWeb.GetUserEffectivePermissions this will return which permissions the user has.


0

You probably need to grant them read access on the top level of the site to have access to the site aspx pages. You could even restrict that access to only the site assets and site pages library if needed. Making them a group owner in no way gives them rights anywhere else.


0

You can choose unique permissions for those two pages. Open pages library, select the page, from ribbon -> Files Tab -> Shared With Choose Advanced -> And From ribbon click on "Stop Inheriting Permission".. Now you can remove whoever you don't want to see the page.


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 ...


0

try this one using (var ctx = new ClientContext(webUri)) { ctx.Credentials = credentials; var groupCreationInfo = new GroupCreationInformation { Title = groupName, Description = groupDesc }; var groupOwner = ctx.Web.SiteGroups.GetByName("Tech Support"); //get an existing group var group = ...


1

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


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 ...


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

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

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 ...


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 ...


0

You can add a column to your list with the account username, and then use a VIEW, that only show items for the current user filtered. i.e. add the Column "user" (user or group type, choose only person), and in your list choose the user using the people picker. The public and default view must filter "when the field user is equal to [me]"


0

You can also do an Approval OOB workflow. Or, more simply, add a Approve/Decline field, create a permissions group for users with only Add permissions and give yourself Contribute or Full Control so that only you can edit the list items.


0

This is what you are looking for: https://support.office.com/en-us/article/Require-approval-of-items-in-a-site-list-or-library-cd0761c4-8c3f-4ea2-9435-13c28aa23d08 Basically content approval let's you keep a buffer state for all items, between when they are added by users and when they are actually visible to everyone else. Any item will be visible to other ...


-1

When talking about permissions and approval, we got many options: 1 - Classical "Item requires approval". Can be achieved through basic list permissions setup. 2 - Customizing forms (via Sharepoint designer or visual studio custom webparts) to show the "approval" column only to some specific group of users. 3 - Customizing forms with Infopath, setting up ...


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 = ...


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 ...


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


0

Commom features/images/scripts/styles should always be set to let NT Authority\Autheticated users read. Imagine that some resources referenced in your masterpage are restricted. Then, everybody will get tons of "Access Denied". About the "Site Pages" issue: Your site pages are referencing something different? Like custom webparts calling CSS/JS or ...


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

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

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!


0

Follow instruction at "Grant full control permissions to the worklow" section of this article. The official doc is here. And yes, you'll need to wrap the action inside an app step.


0

Here's the workaround that I use. Step 1: Add a column to calculate current user Create a Single line of text column called CurrentUser In InfoPath, edit the properties of the column and change the default value to userName() Check the box for Refresh value when formula is recalculated Step 2: Remove the Admin view from the drop down In InfoPath on ...


0

It's stored in a hidden list by the name "Access Requests", if I guess correctly there should be one in each site/sub site where permissions inheritance is broken.


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.


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.


0

Turns out the code works if I set my Add-in to ask for "Tenant, Modify" permissions like so: <AppPermissionRequests AllowAppOnlyPolicy="true"> <AppPermissionRequest Scope="http://sharepoint/content/tenant" Right="Manage" /> </AppPermissionRequests> Credit goes to the kind people over at the "SharePoint 2013 - Development and ...


1

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


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 ...


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...



Top 50 recent answers are included