Tag Info

New answers tagged

1

The permission Scope Web will allow you to work with Host web site. Suppose you have a site collection at url http://sitename. And under it you have a sub site http://sitename/subsite. Now you deploy an app in the subsite. So the subsite will be the Host web. Now you want to create a list in subsite so you will need to provide Web Scope. However, if you ...


0

use this javascript to hide it <script type="text/javascript"> var elem = document.getElementById("Ribbon.ListItem.New-LargeLarge"); elem.style.display = "none"; </script>


0

I did the same using an item event receiver. I'll show what i did in c# code, but you'll have to do the same logic in your script. First of all you can try a $folder.SystemUpdate() instead of the .Update(). This solved some issues for me. Next you can write a foreach that will delete all the current permissions, and after this is executed if adds the ...


0

Based upon experimentation, <AppPermissionRequest Scope="http://sharepoint/content/sitecollection" Right="FullControl" /> is required for a subsite to be created within a specific site collection. I was not able to find any link that describes the permission scopes required for various REST api's


1

Based on this answer by PirateEric♦, If it's anything like 2007, the membership aspect of My Sites is worthless. In 2007, it required that you explicitly be entered into the Members group in a site/site collection. Anything higher (like owners or designers) you didn't show up. Anything lower (like Visitors) you did not show up. If you were given ...


1

NotVonKaiser in this case is correct: 1 runs under farm account and all others are under logged in user account! The logged in user account will call the nt/authenticated account on the server that he/she has authentication on the server todo what he is requesting todo! if that makes sense ;) think of nt/authenticated as if you are physically logging on ...


2

1 should always run under the farm account. For 2, 3, 4, and 5, you should be able to ferret this information out by using this code: SPUser user = SPContext.Current.Web.CurrentUser; string userName = user.Name; //you can also call user.Email here Note that this will not work correctly if you have a 'RunWithElevatedPrivileges' delegate block. Rather, if ...


0

Mike OOTB "Full Control" is the only option for modifying permissions. If you don't want to give your user full control, I would suggest maybe creating a custom permission level. I would probably just copy the "Full Control" level and remove the access you don't want them to have.


1

Yes you can set Item level permissions on Document Library.. Click the context menu/List Item Menu and click Permissions.. Here you can Stop Inheriting Permissions from Library and set unique permissions for the Document.. And once you stop the inheritance of the Document, it will say Item has unique permissions, see below:


0

You are looking for auditing. You can use the audit feature of Microsoft SharePoint Server 2013 to track which users have taken what actions on the sites, content types, lists, libraries, list items, and library files of site collections. Knowing who has done what with which information is critical for many business requirements, such as regulatory ...


0

Seems the best way is to place web part pages in their own library (SitePages?) and break inheritance on that, removing the contribute permissions.


0

and the answer to your question ;) To create an application page that uses the JavaScript object model to work with social feeds, you'll need: •SharePoint Server 2013 with My Site configured as public, with personal sites created for the current user and a target user, with the current user following the target user, and with a few posts ...


1

Other option is to create a HideCustomAction to hide the "Delete a site" action. <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <HideCustomAction Id="Customization" GroupId = "SiteTasks" HideActionId = "DeleteWeb" Location = "Microsoft.SharePoint.SiteSettings"> ...


5

A WebDeleting event can be used to prevent users event if they are owners to delete a site collection. Example: public override void WebDeleting(SPWebEventProperties properties) { properties.Status = SPEventReceiverStatus.CancelWithError; properties.ErrorMessage = "This site cannot be deleted."; properties.Cancel = true; } See this for more ...


0

Follow this steps got to Library Permission by default, library inherits permissions from parent. Just click on Stop Inheriting permissions. after that, Delete the users or groups which you don't want. Add the users or groups that you want library to be accessible. and save. library will than have unique permissions


3

The code is correct and is fine! when accessing aspx pages on the server its not running under app pool account its running under nt authenticated account which should be your own! how do i know? i use aspx on layouts page all the time and giving/dening app pool account access would not effect it! a good expample would be two users.. one site collection ...


1

Since the code is on an .aspx page, the code runs on the server and it will run with the credentials of the application pool account under which this application runs and not under the client credentials as e.g. Silverlight or Javascript client side code would do.


1

No code shouldn't throw any exceptions.. since user has Read permissions, and I hope the List is also inheriting permissions from site, that means user has Read permissions on List as well.. Thus if you try to add an item in the List, it should throw exception.. Reading / Querying won't throw any exceptions.. UPDATE Actually the other answer seems to be ...


2

You can use export-spweb / import-spweb which by default will not carry over user security settings. Command reference: http://technet.microsoft.com/en-us/library/ff607895(v=office.15).aspx


0

I used the following to hide the last empty row in datasheet view (where new items are added): //Add jquery reference <script type='text/javascript' src='../../SiteAssets/javascript/jquery-1.10.2.min.js'> </script> <script type='text/javascript'> //Use _spBodyOnLoadFunctionNames.push to prevent any collisions ...


1

SPO does not have Farm Admins (at least not for tenant users). There is a Global Admin, however, that gives a user access to a nerfed version of Central Admin. To determine you are a Global Admin, you can look at the Suite Bar, and if you can see these Admin links, you are a Global Admin.


0

As stated in my last comment: it turned out I didn't publish a certain page layout as a major version. After doing so, the access denied no longer happens.


3

AFAIK.. Web Parts, User Controls and JSOM either on MasterPage or any page uses the current logged in user credentials until you run the code under RunWithElevatedPrivileges which uses Application Pool identity.. However timer jobs run under SharePoint farm account or simply the user which runs OWSTimer service.


2

-Web Part: Code executes as the user logged in. Runs in w3wp.exe (worker process) -User Control: Code executes as the user logged in. Runs in w3wp.exe (worker process) -JSOM: Code executes as the user logged in to the workstation (since it's client side). Runs in the browser process. -Timer job: Code executes as the SharePoint Farm Account or simply the ...


0

If you need to remove permissions programmatically you should first break inheritance: list.BreakRoleInheritance(true); After that you can for example remove all role assignments for list or library and it does not effect for higher levels: SPRoleAssignmentCollection roleAssignmentCollection = list.RoleAssignments; for (int i = ...


0

Go into the List settings and click on the Advanced Settings link. Set the Item Level Permissions to Create items and edit items that were created by the user for the Create and edit portion of the question.


2

You need to go to Document Library Ribbon -> Under Library -> Library Settings -> Permissions for this document library OR simply Document Library Ribbon -> Under Library -> Library Permissions By default the document library will be inheriting permissions from Site, you need to click "Stop Inheriting permissions" ribbon button to stop that.. Than you ...


0

You can generate a detailed report on SharePoint users access on various elements of SharePoint platform, including Web Application/Site Collection/Site/List level with the help of PowerShell. http://www.sharepointdiary.com/2013/01/permission-report-for-specific-user.html


1

Problem solved. It turns out a previous developer who had developed for us a library provisioning tool for some inexplicable reason decided to set the alloweveryoneviewitems property to true in the code. This meant every library we have provisioned in our system had this value set to true. Easy to fix with powershell script changing the value to false - ...


0

For some of the permissions like Search , User Profile Service, Social Capabilities etc, you need to be tenant admin and not just site collection admin. For more details on this topic please check the following msdn articles App Permissions in SP 2013 Search apps in SP 2013 So basically, you need to login from tenant admin account and then "Trust" the ...


0

Setting up user policy on web application is not proper way how to fulfill your requirements. You should set permissions on the site for groups GroupA and GroupB. Then break permission inheritance on Shared Documents. Remove permissions for GroupA and GroupB and set permissions for Admin and Doc Admin groups. Beware how SharePoint handles access check. ...


1

In order for a user to access an application page they must have 'View Application Pages' permission (available in the Read and View Only permission levels). As stated in this link, you can see that application pages are accessed by going to {siteurl}/_layouts/{applicationpage}. The user needs 'View Application Pages' at the site located at {siteurl}. So ...


1

If you've already checked the following my apologies for suggesting it: For the document (or documents) in question, can you verify that they have not had permissions broken off from the library ? If they are in a folder, also check that the folder hasn't had it's permissions broken off. I've seen what you are describing when the document had broken ...


0

I've solved it now. The solution was to first give the user group access to the sub site itself. Before I had given the user group the Permisson Level Read - but then they would be able to see all the links in QuickLaunch and go to the site. However, I found there was already an existing Permission Level with very restricted permissions Restricted ...


2

It is not a bug.Site Templates does not retain the Security settings.Site templates do not include the following items: Customized permissions, running workflow instances, list item version history, workflow tasks associated with running workflows, people or group field values, taxonomy field values, publishing pages and publishing sites, My Sites, and ...


1

Permissions are not included in site templates in SharePoint Server or SharePoint Online. More to read in Reference 1 and Reference 2


1

On premises you can use this: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.speventreceivertype.aspx In Office 365 You can in theory create an app that will handle the administration of those groups for you. However you'd have to hide the original permission management page (master page changes).


0

Believe it or not, I could actually solve this issue by adding the central admin to the list of safe local intranet sites in IE (please note that it didn't work for trusted sites, just intranet sites). I followed the steps in this tutorial (after trying many, many things) and it solved my issue: ...


1

The best way from my point of view is to add the users to an Active Directory Group. Then assign this AD group the requested permissions on the calendar and on the other site collection.


0

Site Templates does not retain the Security settings.Site templates do not include the following items: Customized permissions, running workflow instances, list item version history, workflow tasks associated with running workflows, people or group field values, taxonomy field values, publishing pages and publishing sites, My Sites, and stapled features. ...


0

I solved it by adding a Membership element in the CAML query for the view with the filters.


1

Farm admin rights are needed to write to config DB whereas app pool account can write to content DB. That means running the code inside RunWithElevatedPrevileges should be able to write to content DB.


0

When you run with elevated privileges it will use the application pool identity. The application pool identity has full access to the web application.So you need to be farm admin to access content db. There is other interesting way to look at your question . Below scenario can be considered The property bags are stored under content db. Your current ...


0

I finally figured it out! For some reason I was unable to use xmlDoc.Load(string URL) but I was able to workaround it using xmlDoc.Load(Stream stream) Here's what worked for me: SPList styleLib = site.RootWeb.Lists.TryGetList("Style Library"); SPFolder templatesFolder = styleLib.RootFolder.SubFolders["xml"]; SPQuery query = new SPQuery { Query = ...


3

Please check MSDN: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsecurity.runwithelevatedprivileges(v=office.14).aspx Executes the specified method with Full Control rights even if the user does not otherwise have Full Control. Parameters secureCode Type: Microsoft.SharePoint.SPSecurity.CodeToRunElevated A delegate method that is to run ...


1

It runs under the permissions of the System Account of the WebApplication. The System account is the account with which the App Pool of the Web Application is configured.



Top 50 recent answers are included