Showing posts with label Permissions. Show all posts
Showing posts with label Permissions. Show all posts

25 December, 2012

You cannot switch the user account in SharePoint Designer 2013

SharePoint Designer is a powerful application that enables the rapid creation, editing and deployment of content on the SharePoint platform.

Microsoft has already published a document on this issue and here is the KB article for this:

Additional references:
Please refer the following error messages:

1.      Indexer process doesn’t free up old memory after repartitioning

2.      New-SPEnterpriseSearchIndexComponent checks the existence of RootDirectory in the wrong server

3.      PerformancePoint Dashboard Designer Help doesn’t open as expected

4.      PowerPoint intent isn’t shown

5.      Repair operations on SharePoint Standalone can delete your content database

6.      WSS Sync failed to run in because of a lack of profile database permission

7.      Cannot process argument because the value of argument"implementingType" is null. Change the value of argument "implementingType" to a non-null value.

8.      "Error occurred in deployment step 'Add Solution': Cannot start service SPUserCodeV4 on computer ..."

9.      Unable to retrieve topology component health states. This may be because the admin component is not up and running.

If you are facing any error messages which are listed above then please refer the following Microsoft article for the details workaround information:

If you have any queries/questions regarding the above mentioned information then please let me know. Thank you.

SharePoint Designer permission requirements

SharePoint Designer is a powerful application that enables the rapid creation, editing and deployment of content on the SharePoint platform. As such, certain mandatory permission levels are required.

Detail Information:

After enabling SharePoint Designer at the web application level and site collection level, the next steps are to select the users that will be enabled to access, create, and modify SharePoint content through SharePoint Designer.

SharePoint Designer is designed to request and use SharePoint permissions that grant the rights of managing & designing at the SharePoint site level it is not design to use the permission at a smaller granularity level such as list item level permissions..

Reference Documents:

Conclusion:
To be able to use SharePoint Designer and modify SharePoint content, an user needs to be a member of one of the following groups at the site collection level:
1.      Site Collection Administrators group
2.      The Designers group
3.      Owners group

If you have any queries/questions regarding the above mentioned information then please let me know. Thank you.

30 April, 2012

Customize an existing permission level


If you wants to create custom permission level that is a replica or identical to an existing default permission level and you do not need to use the default permission level, you can customize the default permission level.

To customize an existing permission level
  1. Verify that you have one of the following administrative credentials:
·         You are a member of the Administrators group for the site collection.
·         You are a member of the Owners group for the site.
·         You have the Manage Permissions permission.
  1. On the Site Settings page, under Users and Permissions, click Site permissions.
  2. In the Manage section of the ribbon, click Permission Levels.
  3. In the list of permission levels, click the name of the permission level you want to customize.
  4. In the list of permissions, select or clear the check boxes to add permissions to or remove permissions from the permission level.
  5. Click Submit.
That’s it and you are done J J

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you

29 April, 2012

Folder permission in sharepoint foundation 2010

If your site contains confidential data and you wants to restrict that data only for certain users and groups then this concept comes into the picture. For this, you need break permissions inheritance, and then edit permissions for the content on its own permissions page.
By default, all sub-sites, lists, and libraries within a site inherit permissions settings from whatever is directly above them in the site hierarchy. For example, a sub-site inherits permissions from the site above it. A list item inherits permissions from the list that it is in. A list inherits permissions from the site is on. In each of these cases, the content from which permissions are inherited is called the parent.
Here are the detailed steps:
1.     Open the list that you want to restrict access to.
2.     On the List Tools tab
3.     Click List to open the gallery of commands specific to the list.
4.     On the ribbon
5.     Click the List Permissions button.

The permissions page for the list opens, with a yellow status bar that explains that the list inherits permission from its parent site.
6.     Click the Stop Inheriting Permissions button.
Note: Now the list is disconnected from the parent site.

Two important things to note:
·         The list still has the same permission settings that it did before. But now, instead of inheriting permissions from the parent, it has its own copy of the parent’s permissions.
·         Changes that you make to the permissions settings for the parent site will not be inherited by this list.

Remove groups or users you don’t want
1.     In the Name section of the permissions page, select the checkboxes for the groups or users who should not have access to this list.
2.     Click Remove User Permissions.
The permissions page updates to show that the group or user no longer has permissions to the list.


Grant access to your Team members:
1. On the permissions page for the list, on the Edit tab, click the Grant Permissions button.
2. Type the name of the group or the individual you want to grant access to in the Users/Groups box.
3. Choose the level of permissions you want the group or individuals to have.
4. Click OK


That's it and You are done J J J

12 April, 2012

sites and site collection in SharePoint 2010

Sites, Site collections and sub-sites: Very commonly used terms in SharePoint right from the first version i.e. SharePoint 2001 till new version i.e. SharePoint 2010. Every SharePoint version has some new features, new functionalities, different GUI interface and many more.
Today we are going to concentrate on site collection features, How exactly the GUI change, where exactly we need to check, what options are available, which features are important from day to day perspective.
For site designers: a site collection's galleries and libraries provide a means for creating a unified, branded user experience across all sites in the site collection.
For site collection administrators: a site collection provides a unified mechanism and scope for administration. For example, security, policies, and features can be managed for a whole site collection; Site Collection Web Analytics Reports, audit log reports, and other data can help administrators track site collection security and performance.
For farm administrators: site collections provide scalability for growth based on how much content is stored. Because each site collection can use a unique content database, administrators can easily move them to separate servers.
For site authors: a site collection's shared site columns, content types, Web Parts, authoring resources, workflows, and other features provide a consistent authoring environment.
For site users: a site collection's unified navigation, branding, and search tools provide a unified Web site experience.
The following list includes site features that you can configure uniquely:
Templates: You can make each site have a unique template. For more information, see Site templates included in SharePoint Foundation 2010.
Language: If language packs have been installed on the Web server, you can select a language-specific site template when you create a new site. Text that appears on the site is displayed in the site template’s language. For more information, see Deploy language packs (SharePoint Foundation 2010).
Security: You can define unique user groups and permissions for each site. For more information, see SharePoint 2010 Governance Planning (white paper).
Navigation: You can fine-tune your site's navigation experience by configuring unique navigation links in each part of your site's hierarchy. Site navigation reflects the relationships among the sites in a site collection. Therefore, planning navigation and planning sites structures are closely related activities. For more information, see Site navigation overview (SharePoint Foundation 2010).
Web pages: You can make each site have a unique welcome page and other pages.
Site layouts: You can make unique layouts or master pages available in a site.
Themes: You can change colors and fonts on a site. For more information, see Plan for using themes (SharePoint Foundation 2010).
Regional settings: You can change the regional settings, such as locale, time zone, sort order, time format, and calendar type. For more information, see Regional settings (SharePoint Foundation 2010).
Search: You can make each site have unique search settings. For example, you can specify that a particular site never appears in search results.
Content types: You can make each site have unique content types and site columns. For more information, see Content type and workflow planning (SharePoint Foundation 2010).
Workflows: You can make each site have unique workflows.
I hope the above mentioned information will be helpful to you and provide some insight that you are looking for. In case of any queries/questions then please let me know. I would be more than happy to help you as well as resolves your issues J J