> For the complete documentation index, see [llms.txt](https://docs.alloyaccess.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alloyaccess.com/activity/user-activity-log.md).

# User Activity Log

The purpose of this document is to provide a comprehensive guide on how to use the User Activity Log feature in the Alloy Access Web platform. It aims to help users understand the User Activity Log feature and how it can help them track and monitor activity. This document will also provide step-by-step instructions on how to access and interpret information within the User Activity Log.

## Benefits

The User Activity Log feature in Alloy Access Web provides several benefits for users, including:

* **Enhanced Security**: The User Activity Log allows users to track activity helping to identify potential security threats and prevent unauthorized access.
* **Improved Accountability**: It helps users keep track of what changes have been made, improving accountability and preventing mistakes or intentional misuse.
* **Better Decision-Making**: Information from the User Activity Log can help users make better decisions about managing their accounts by identifying areas for improvement.
* **Time-Saving**: The feature automatically records and stores all activity, saving time and reducing the risk of missing important information.
* **Troubleshooting**: It can be a valuable tool for troubleshooting issues, as users can trace the source of problems and take appropriate action to resolve them.

## Access the User Activity Log

To access the User Activity Log in Alloy Access Web:&#x20;

1. Log in to your account.
2. Navigate to any Alloy Access site on the platform.
3. Click on "Activity" menu option and select the "User Activity" tab in the platform's dashboard. This will take you to a page where you can view a list of all activity

<figure><img src="/files/w831FfeLtZfOTVJB1zt6" alt=""><figcaption></figcaption></figure>

## Understanding the User Activity Log

The User Activity Log consists of several columns providing detailed information about each event:

1. **User**: Displays the name of the person or system that performed the action or triggered the event.
2. **Action**: Shows the action that was taken on the given resource.
3. **Category**: Displays the category of the event (e.g., Schedule).
4. **Details**: Provides a detailed description of the event with a link to the impacted category.
5. **Date**: Displays the date and time when the event occurred.&#x20;

## View Detailed Changes

To view detailed changes select the row in the user activity log which allows you to see more information about a specific log entry.&#x20;

<figure><img src="/files/2K5ARamthHe1N6lmB8qw" alt=""><figcaption></figcaption></figure>

If you have any questions about this feature or requests for new features, please reach out to [Alloy Access Support](mailto:alloyaccesssupport@smartrent.com).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.alloyaccess.com/activity/user-activity-log.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
