Overview
The team activity log is a running record of who signed in and what changed in your team, newest first. It shows changes made by team members, through the API, and by our support team, so you can always see who did what and when. This is useful for tracking down an unexpected change, confirming that a task such as a backup restore completed, reviewing sign-ins and security changes, or keeping a record for your own audits.
The log records actions that change something, such as creating, updating, deleting, or restarting, along with sign-ins. Simply viewing pages or settings in the dashboard is not recorded. Only the team owner, Super Admins, and Administrators can view the log.
In this article, you will find who can view the activity log, how to open it and read an event, what gets recorded, and step-by-step instructions for filtering and exporting the log.
Who can view the activity log
Role | Can view the activity log |
Team owner | Yes |
Super Admin | Yes |
Administrator | Yes |
Billing Manager, Member, Guest | No |
Team members without access do not see the Activity button on the Team page.
Our support team can also see your activity log while you have given them access to your dashboard. See How to give dashboard access to Levamo's support team.
How to open the activity log
Step 1: Open the Team page
Log in to your Levamo dashboard and click Team in the top navigation menu.
Step 2: Click Activity
At the top right of the Team page, click Activity. The activity log opens with the most recent event at the top.
Reading an event
Each row in the log shows:
Column | What it shows |
Date | When the action happened |
User | Who performed the action and their role. Your own actions are marked (you) |
Section | The part of the team the action relates to, such as Account, Team, or Environment. For environment events, the environment's name is shown underneath as a link |
Event | What happened, with its activity category underneath, for example Signed in under Sign-in & security |
Message | A short description of the action, such as which member was invited |
Click the + next to an event to expand it. The Details panel shows:
User: The email address and role or name of the person who performed the action
IP address: The IP address the action came from
Device: The browser and operating system used
Event ID: A unique reference for the event, useful if you contact our support team about it
Depending on the event, the Details panel can also show the Section the action applied to, a Desc field with more context (for example, Manual backup), and a Task number for actions that run in the background.
The Event panel shows the full message and the outcome of the action. For background tasks, it also shows the task number, and where relevant, a link such as Open environment to go straight to what was affected.
Tip:
Names in the log are recorded at the moment the action happened. If a member is later removed or an environment is renamed, past events keep the original names, so your history stays accurate.
Outcomes
Many dashboard actions, such as restoring a backup or changing a plan, start a task that runs in the background. These events first show as Queued, and their outcome changes when the task finishes.
Outcome | Meaning |
Queued | The action was accepted and a background task has started |
Done | The action or task completed successfully |
Failed | The task did not complete |
Cancelled | The task was cancelled before it finished |
Refused | The action was not allowed and did not run |
What gets recorded
Events are grouped into activity categories, which you can also use to filter the log. The main categories and examples of what they record are:
Category | Examples |
Sign-in & security | Sign-ins, sign-outs, failed sign-in attempts, password changes, and two-factor authentication changes |
Account | Profile updates and default team changes |
Team & members | Invites, role and access changes, members joining or leaving, team settings changes, API key changes, and support team access |
Environments | Environments created, deleted, renamed, restarted, or changed plan, plus PHP, cron job, SSL, and staging changes |
Sites | Sites created, cloned, or deleted, and staging pushes and pulls |
Domains & DNS | Domains added, verified, or set as primary, CDN changes, and DNS record changes |
Backups | Backups created, restored, scheduled, or downloaded |
WordPress | Core, plugin, and theme updates, cache clears, and wp-config changes |
Files | Files uploaded, edited, moved, renamed, or deleted |
Firewall & logs | Firewall rule changes and logs cleared |
Billing | Subscription changes, pauses, cancellations, and trial upgrades |
SSH keys | SSH keys added, generated, or deleted |
Migrations | Migration requests created or deleted |
The log also includes categories for background tasks, Platform API activity, and notifications.
Sign-ins
Sign-ins belong to a person rather than a team, so the log shows sign-ins for the current members of your team. If someone belongs to more than one team, their sign-ins appear in each team's log.
When someone from Levamo opens your team, for example to help with a support request or a migration, it is recorded as Levamo agent opened this team under Team & members, with a badge showing which Levamo team they belong to.
How to filter and export the activity log
Filter the log
Use the filters at the top of the activity log to narrow down what you see. You can combine them.
All members: Show only the actions of a specific team member
All activity: Show only one activity category, such as Environments or Billing
Any time: Show only events within a date range
If nothing matches your filters, clear or widen them to see more results.
Tip:
To check what a specific member has done, you can also select View activity from the ⋯ menu on their row on the Team page.
Export the log as a CSV file
Step 1: Apply your filters
Set any member, category, or date filters you want. The export includes only the events that match.
Step 2: Click Export
Click Export. A CSV file with the filtered events downloads to your device.
The CSV includes names as they were recorded at the time of each action.
Important information
Only the team owner, Super Admins, and Administrators can view and export the activity log
The log records changes and sign-ins, not page views
Events are listed newest first
Names in the log reflect the moment each action happened, even if a member or environment is later renamed or removed
Every change to a member's role, access, or status is recorded under Team & members
Visits from Levamo staff are always recorded as Levamo agent opened this team
FAQ
I don't see the Activity button. Why?
Only the team owner, Super Admins, and Administrators can view the activity log. If you need access, ask the team owner or a Super Admin to change your role. See Team roles and permissions.
An event has been Queued for a while. Is something wrong?
Queued means the task is still running in the background. Some tasks, such as large backup restores, take longer than others. Check back later. If an event stays queued for an unusually long time, contact our support team and include the event ID.
Why does an old event show a member who has left, or an environment's old name?
Names are saved at the time of each action, so your history stays accurate even after things change. This is expected.
I viewed a setting, but it is not in the log. Why?
The log records changes and sign-ins only. Viewing pages or settings is not recorded.
Can I see what Levamo's support team did in my team?
Yes. Every time someone from Levamo opens your team, it is recorded as Levamo agent opened this team. Changes they make are recorded like any other action.
Conclusion
The team activity log gives you a clear record of who signed in and what changed across your team, from site and environment changes to role updates and support access. Use the filters to find what you need quickly, and export the log whenever you need a copy for your records.
If you have questions about an event in your log, our support team is available 24/7.