> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/cerby-mobile-app/accounts/managing-your-accounts/view-the-activity-log-for-an-account.md).

# View the activity log for an account

{% hint style="info" %}
**Who can use this feature?**

* Workspace **Owners**, **Super Admins**, **Admins**, **Users**, **Login-Only**, and **Guest Users**
* Account **Owners** and **Collaborators**
* Only supported using the Cerby mobile app
  {% endhint %}

Every account in Cerby keeps a record of login events, credential changes, automation runs, and access changes. As an account **Owner** or **Collaborator**, you can view this activity log from the account's detail screen to see when the account was accessed, which actions Cerby performed automatically, and when access was granted or revoked.

Admins can use the activity log to investigate unexpected logins or verify that scheduled automations completed successfully.

To view the activity log for an account, complete the following steps:

1. Open the Cerby mobile app on your mobile phone.
2. Log in to your Cerby workspace.
3. Tap **Accounts** at the bottom of the screen. The **Accounts** screen is displayed.
4. Tap the account whose activity you want to review. The account details screen is displayed.
5. Scroll down to the **Activity** section. The activity log is displayed, with the most recent events at the top.

Each entry in the activity log shows the following information:

* The event type:
  * **Login:** A successful login to the account, either manually or through Cerby Autofill.
  * **Login failed:** A login attempt that did not succeed.
  * **Password rotated:** Cerby automatically changed the account password.
  * **Password rotation failed:** An automated password rotation did not complete.
  * **MFA enabled:** Cerby-managed multi-factor authentication (MFA) was turned on for the account.
  * **MFA disabled:** Cerby-managed MFA was turned off for the account.
  * **Access shared:** Another user or team was granted access to the account.
  * **Access removed:** A user or team's access to the account was revoked.
  * **Credentials updated:** The username, password, or other credentials were changed manually.
* The date and time of the event
* The actor that triggered the event (a user name, or "Cerby" for automated actions)

{% hint style="info" %}
**NOTE:** Events older than 90 days may not appear in the mobile activity log. To review the full history, open the account in the Cerby web app.
{% endhint %}

## Related articles

* [Use the Notification Center in the Cerby mobile app](/cerby-mobile-app/app-customization/use-the-notification-center.md)
* [View the details of an account](/cerby-mobile-app/accounts/managing-your-accounts/view-the-details-of-an-account.md)
* [Log in to an account](/cerby-mobile-app/accounts/accessing-your-accounts/log-in-to-an-account.md)


---

# 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://help.cerby.com/cerby-mobile-app/accounts/managing-your-accounts/view-the-activity-log-for-an-account.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.
