Friday, November 30, 2012

How to enable the audit log in SharePoint 2013

To enable the audit log by using Central Administration

·         On the Central Administration home page,
·         In the Application Management section,
·         Click Manage service applications.
·         Select the Secure Store service application.
·         On the ribbon, click Properties.
·         From the Enable Audit section,
·         Click to select the Audit log enabled box.
·         To change the number of days that entries will be purged from the audit log file, specify a number in days in the Days until Purge field.
·         The default value is 30 days.
·         Click OK.

Configure audit settings for a site collection

Please use the following link in which Microsoft has given a very detailed description that references each and every minor point regarding audit settings:

It consists of:
·         Auditing event information
·         Trimming the audit logs (new enhancements in SP2010 and SP2013 as compare to earlier versions)
·         Configure audit log trimming
·         Configure events to audit

View audit log reports
Following link will help you to understand the following points:
·         Events available for audit log reports
·         Available audit log reports
·         View audit log reports

1 comment:

Jhon Drake said...

Nice blog post, it describe step by step to enable the audit log in SharePoint 2013 and set audit settings for a site collection. I tested the automate software from which allows to track which users have taken what actions on the sites, libraries, lists, list items, content types and library files within the site collections and know who has done what with which information.

Popular Posts


The opinions expressed on this blog are the personal views of Pratik's SharePoint Blog, and do not represent or reflect the viewpoints or policies of any past, present, or future employer, colleague, or customer, or any other entity. The posts on this blog are provided ‘as is’ with no warranties, express or implied, and confer no rights. Use of information contained within this blog, including specific technical steps mentioned herein, is at your own risk. References to specific software products, processes, resources, or companies do not imply any endorsement.