---
## How to configure audit settings
Audit configuration lets you choose which event categories are logged, keeping your audit data focused.
1. Navigate to **Settings** () > **Knowledge base portal** in the left navigation bar.
2. In the left navigation pane, select **Team auditing**.
3. Go to the **Audit configuration** tab.
4. To monitor all project events, turn on the **All events** toggle.
5. To monitor only specific areas, turn on the toggle for one or more of the following event categories:
Tracks events related to the documentation editor, such as:
Tracks events related to Drive actions, such as:
Tracks portal-specific activities, such as:
Covers site-specific activities, such as:
Tracks widget-related actions, such as:
Includes user management activities, such as:
Tracks actions such as:
---
## Best practices
- **Enable selective audit categories** rather than logging all events in large projects. This reduces log noise and makes it easier to find relevant entries.
- **Export and archive CSV reports regularly** if your project has compliance requirements.
- **Filter by user before exporting** when investigating a specific team member's activity, so the CSV contains only the relevant records.
- **Keep the Documentation editor category on if you use archiving.** Archived content is removed from the category tree and from portal search, so the audit log is often the quickest way to establish who archived an item and when.
---
## FAQ
What is team auditing in the knowledge base portal?
Team auditing tracks actions performed by your users within a Document360 project, such as adding or updating articles and changing settings, along with who performed each action and when.
How do I export a specific user's auditing records?
Navigate to Settings > Knowledge base portal > Team auditing. Use the Activity by user dropdown to select the user, apply the Event and Audit date filters as needed, then click Export CSV.
How frequently is the audit data updated?
Audit data is updated in real time. Click Refresh to ensure you are viewing the latest activity.
Can I track when a category is cloned in team auditing?
No. Category cloning is not logged as an audit event. As a workaround, filter by the Clone article created event and look for articles that were inside the cloned category. This provides an indirect indication that a category clone occurred.
How do I find out who moved a category and when?
Navigate to Team auditing and filter the Events by Categories reordered, then click Apply. The log shows who performed the action and when. Note that the category name is only captured if drag-and-drop was used; the Move option does not record the category name.
Can I restrict access to team auditing for certain team members?
Yes. Access to team auditing is controlled by user roles and permissions. Only Owners, Admins, and users with a custom role that includes team auditing access can view or update the feature.
Can I recover deleted articles through team auditing?
No. Team auditing records what happened but does not provide recovery options. To restore deleted content, use the backup and restore or version history features. To restore archived content, use the Archive page.
Why does the article name show incorrectly in the audit log after a Word import?
If an article is renamed during the Word import process, the audit log captures the original Word file name rather than the updated name. To avoid this, complete the import first, then rename the article after import is done.
Can I monitor specific events instead of all project events?
Yes. In the Audit configuration tab, turn on the toggle for specific event categories, such as Documentation editor or Users & security settings, to monitor only those events.