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.

2. On the Site Settings page, under Users and Permissions, click Site permissions.
3. In the Manage section of the ribbon, click Permission Levels.
4. In the list of permission levels, click the name of the permission level you want to customize.
5. In the list of permissions, select or clear the check boxes to add permissions to or remove permissions from the permission level.
6. 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

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

Custom Robots.txt

Robots.txt file helps you allow or block the search engine Robots to Crawl/index the pages. Now you can control what content you want to crawl or ignore by search engine. 

 

Not only this now you can use the robots.txt file to block search engines from crawling different parts of your blog like pages, archives, tags.  You can also add sitemap URL to BlogSpot’s robots.txt file for indexing. 

 

You can access the robots.txt file of any blog by visiting this url (http://yourblog.blogspot.com/robot.txt)

Warning!! If you don’t have much knowledge about this, never try to changing or Modifiying this file because it can effect the search engine visibility.

Custom 404 Error Page

This Custom 404 Error Page is one of the most awaited feature by Google and time to say Bye bye to Blogger default Error Page not found page. 

A 404 Not Found Page usually appears when visitor lands on a page that does not exist on your blog or URL mistake.  

Now you can easily add Custom 404 Not Found pages to your Error Pages. Check this picture below how you can set a custom 404 page.

 

Not able to download audit reports

Auditing is an important feature in SharePoint. Auditing maintains a log of the actions performed on content in a site collection. Administrators can retrieve the entire history of actions — from a particular user or date range.

If you want to learn as how to configure audit settings then please refer the following article: http://office.microsoft.com/en-us/sharepoint-server-help/configure-audit-settings-for-a-site-collection-HA010099726.aspx

Coming back to the main point: One of our clients has raised a ticket with us by mentioning: They are not able to download ‘content viewing’ reports.

What exactly is happening as they are not able to download?

·         Open the SharePoint site on which you are working on

·         Site actions

·         Site settings

·         Site collection administration section

·         Audit log reports

·         Whenever we clicks on ‘content viewing report’ to download

·         It prompts for credentials

·         After entering the correct username and password, it keeps the login prompt as it is and finally ‘you are not authorized to view this page’

What is the reason behind this issue / proper explanation?

Audit settings can be configured at the site collection level only. The logs are maintained in the dbo.AuditData table of the respective content database.

You will find an excellent explanation here:

http://blogs.msdn.com/b/subhajitc/archive/2009/05/20/tip-the-untold-story-of-audit-logs-in-sharepoint.aspx

Resolution:

stsadm -o trimauditlog

   -url <URL name>

   -date <YYYYMMDD>

   -databasename <database name>

   [-databaseserver] <database server name>

Important instructions:

·         If you are providing the site collection URL then there is no need to provide database name as well as database server name

·         Let’s assume that your client wants the audit data in between 21 September 2011 to 25 April 2012 then the date parameter will be 20110921, so the data before this will be deleted or u can call it as trimmed.

Note: This operation is available after the Infrastructure Update for Microsoft Office Servers is installed. This functionality is available only by using Stsadm.

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 issuesJ J