There is a option in the App Catalog to share an app. We can select Can Edit option and share. But I could not find what actually happens when you do this. Where does this permission get affected?
Since "Apps for SharePoint" is another type of document library which contains your app package. The "Share" menu item should be the same one as the list item or document which provides item level permission management. You can configure the specific apps to be accessed by specific users for specific actions, like edit if you don't want your apps to inherit from default "App for SharePoint" library's permission sets.
Related
So I have a SharePoint site with a few different pages.
I want to add someone to that SharePoint site, but I want them to only be able to see the one library in the site and nothing else.
I know that it can be done but I'm unsure as to how.
Yon need to configure the libraray to have unique permission.
Break permission inheritance in SharePoint Online: Go to library settings-> Permissions for this document library-> click Stop Inheriting Permissions.
Assign unique permissions in SharePoint Online:Go to the Permissions page mentioned above, Click Grant Permissions to give user access.
For more, please refer to this article:
https://support.office.com/en-us/article/customize-permissions-for-a-sharepoint-list-or-library-02d770f3-59eb-4910-a608-5f84cc297782
Navigate to that particular library ->library settings -> Permission for this library -> Break inheritance of that library(stop inheriting permissions)-> Click on Grant Permissions(here you can add that users with permission)
This is how we can add the user to the specific library.
sample screenshot is here
I have a site collection with a subsite. I am storing a roadmap and some other project management documents within a document library in my subsite. I would like to share that document library with an internal user, but I don’t want her to see anything else – just that document library. I don’t want her to see any other parts of the site. Can I do that? How?
Yes,
Go to Site Settings > Site Permissions
Remove the user from all groups (click on Check Permissions to see what permissions she has on your site).
Go to the document library and click on the Library tab in the
ribbon.
Click on Shared With (far to the right)
Click on ADVANCED
Click on Stop Inheriting Permissions, confirm with Ok
Click on Grant
Permissions and give the user the appropriate rights (read, edit
etc.)
EDIT:
This is for a SharePoint 2013 site. Sorry for that. I dont have a SharePoint 2010 site available right now so I cant give you the exact steps, but the concept is still the same:
Remove the users permissions to the site.
Stop inheriting permissions for the document library
Grant the user permissions to the documet library
What are the minimum SharePoint 2010 permissions required to allow a user to personalize a web part page, allowing updates and adding web parts to the page but completely restrict the user modifying the shared version?
I initially copied the built-in “Read” permission level and added the “Manage Personal Views”, “Add/Remove Personal Web Parts” and “Update Personal Web Parts” permissions from the Personal Permissions group. This custom permission level was then applied to a user who then viewed a web part page created by the Administrator, which contained only a very simple prototype SharePoint web part. This web part contained a modifiable label which was edited using the “Miscellaneous” section from the Edit Web Part from the standard SharePoint chrome.
With the custom permission level applied the “Miscellaneous” option it is not available to the user upon personalizing the page and selecting Edit Web Part. The “Miscellaneous” option only becomes available to the user when the permission level is further modified to have the “Edit Items” from the List Permissions group. This has the undesired effect of allowing the user to be able to modify the shared version of the page.
Is what I’m trying to achieve even possible?
Many thanks
Check this out: http://akifkamalsyed.wordpress.com/2011/01/17/personalizable-web-part-custom-property-not-shown-for-users-with-contribute-permission-level/
It's probably because you don't have a safecontrol for the webpart with the attribute SafeAgainstScript
I am developing a sharepoint 2010 visual webpart that will show some sort of ajax content.
I have a property on the webpart for the refresh rate, but I want this property to be set only by an Administrator (or any specific group).
What is the best way to achieve this?
Thank you.
In our organization, everyone by default is granted "Read" permission to our SharePoint sites through an "All Employees" Active Directory group. This allows users to browse the pages, but not edit them; and if you can't edit a page, you can't edit any web parts on the page.
Those who should have elevated privileges are added to other AD groups (you could use SharePoint groups too), and those groups are granted appropriate permissions.
You could create a custom Toolpart. Take a look at this example for a tutorial on how to create one.
Overall, your general steps will be:
Create your custom Toolpart class inheriting from Microsoft.SharePoint.WebPartPages.ToolPart
In your custom Toolpart, override CreateChildControls, write the code to display your textbox as long as the current user has permission (based on whatever rules you choose, ex: SharePoint group).
In your webpart, override GetToolParts and add your custom ToolPart so that it shows up in the right hand side
Can i program custom base permission level? There are many available in SPBasePermissions like
UseRemoteAPIs Use SOAP, WebDAV, or Microsoft Office SharePoint Designer 2007 interfaces to access the Web site.
ViewFormPages View forms, views, and application pages, and enumerate lists.
ViewListItems View items in lists, documents in document libraries, and view Web discussion comments.
However i want to make a custom one, something like:
EditItemsAssignedToMe + ViewItemsAssignedToMe + view/edit items i created.
Still finding my way out to allow users view and edit items created by them or assigned to them.
OOTB you don't have the fine-grained control and can only assign a certain set of permissions as defined on technet and this blog article.
However programmatically you can create a new SPRoleDefinition and assign it the appropriate permissions based on the SPBasePermissions enumeration as per this blog article. You might also want to read this short guide on the basics of SPBasePermissions.
If you want to go even further though and emulate the OOTB behaviour with your own custom permission set try Implementing Custom Security Rights in SharePoint.