In a previous lesson, we showed how to create and how to view audit profile data. In order for profile-level actions to be logged to the audit profile we have configured here, we must first enable auditing for each project we want to audit. To do this, let's go to our Designer, where we have a project named Auditing opened. We then go to Project, Properties to open the Project Properties window. Once here, we head to the General project section and we enable auditing in the Auditing Settings. We want to make sure that our project is looking at the correct audit profile, so we select it from the dropdown menu. We only have one audit profile configured, so it is the only one listed. We then click OK to finish the configuration and we save our changes. Once we do this, events from the auditing project will begin to be logged into the audit events database table. Our audit profile is configured to use. To verify it is working, let's use the Database Query Browser to see live audit events as they are logged. First, let's write to a tag. From the Tag Browser, we have a memory tag named Tag1 with a current value of five. If I write a 10 to it and then query for all the entries in the audit events table, we see that the tag write I just performed was caught by the auditing system. Similarly, if I create a window named Main Window, and then save my project, we can query the audit events table once more and we will find entries for both the window creation and the project save event. Since the audit profile is also capable of detecting user login events, if I launch a vision client for my auditing project and simply log in, we see that the login event and the logout event triggered by me closing the vision client are also listed in the audit events table.