At mabl we believe that testing is a team sport that requires constant collaboration between QA professionals, developers, product managers, and other business stakeholders. To help keep everyone on the same page, use the activity feed to quickly review historical user activity across the workspace.
This article describes what you can do in the activity feed:
- Filter workspace activity
- See changes made by agents
- Recover deleted entities
- Review company activity
The workspace activity feed is located in Settings > Activity feed, and everyone in the workspace can view it, whatever their role. Activity that isn't owned by any single workspace is recorded separately, in the company activity feed.
mabl API
In addition to reviewing workspace activity in the mabl app, you can also query workspace activity from the mabl API.
Filter workspace activity
Use activity feed filters to find specific events and review workspace activity. Combine the filters to focus on specific actions, such as flows created in the past two weeks or user activity for a given time period.
Tracked entities
The activity feed tracks create, update, and delete actions for the following workspace entities:
- application
- branch
- credentials
- database connection
- datatable
- environment
- file upload
- flow
- link agent
- link tunnel access
- permanent email address
- plan
- query
- resource group
- resource group assignment
- role grant
- snippet
- test
- user role
- workspace
The link agent and link tunnel access entities record mabl Link activity:
- link agent: when a Link Agent registers, connects, disconnects and reconnects, starts or ends maintenance, finishes draining, updates to a new version, or is shut down or removed.
- link tunnel access: when someone accesses a Link tunnel, including with an API key, when a connection is denied, and when mabl support starts a session on a tunnel. See Controlling access to Link tunnels.
For more information on recover actions, see the section on recovering deleted entities.
Event type
Filter by Event type to see one kind of change: Create, Update, Delete, or Recover.
Most update events record who saved the entity and when. Plan and environment updates also describe what changed, for example "Added 2 tests to the Smoke plan" or "Removed 3 variables from the Staging environment." To see the full list of changes, click the icon in the Actions column:
- Plans: View plan changes shows each changed setting with its value before and after, and what was added or removed. It covers the plan's name, description, labels, status, and triggers; its tests, stages, and environments; browsers and devices; credentials and HTTP headers; and run settings.
- Environments: View variable changes shows which variables were added, removed, or had their values changed. When an environment is deleted, its delete event lists the variables it had, so you know which ones to recreate.
Updates whose summary already tells the whole story, such as enabling or disabling a plan, have no icon. To keep secrets safe, the activity feed records the names of environment variables and HTTP headers, never their values. Environment updates saved before November 2, 2026 keep the general "Updated the Staging environment" wording.
Note on flow updates
If you see flow updates that nobody made on purpose, check whether the flow uses variables from the test. When a flow reads test-level variables instead of flow parameters, changing a variable's default value in a test saves a new version of the flow, which appears in the feed as an update. To avoid these updates, use flow parameters.
Event name
The activity feed supports searching by current and historical event names. For example, if a test was initially named "app - validate shipping calculator" and then renamed "checkout - validate shipping rates", you could search for either name in the activity feed and find all activity associated with the test.
See changes made by agents
When an agent makes a change for a person or an API key, the User column shows that person or key on the first line and the agent that made the change on the line below:
- via mabl agent: the mabl agent made the change, for example while building or editing a test.
- via external agent: an AI coding assistant connected to your workspace through the mabl MCP made the change.
Changes a person or API key makes directly show only the person or key. The company activity feed shows agent changes the same way.
Recover deleted entities
Some deleted entities can be recovered using the workspace activity feed. Click on the restore icon to the right of the entity to recover it.
Recovering a deleted test
Requirements for recovering deleted entities
Only workspace owners can recover deleted entities. The entity must have been deleted less than 30 days ago and must be currently deleted.
The following types of entities can be recovered in the activity feed:
- file upload
- flow
- permanent email address
- plan
- resource group
- snippet
- test
Review company activity
Some resources belong to your company rather than to any single workspace. Changes to those resources are recorded in a separate activity feed on the company dashboard, which is available to company admins.
To review company activity, expand the workspace dropdown in the top right corner of the mabl app and click on your company under Manage company. Then click Activity feed in the sidebar.
Tracked company entities
The company activity feed tracks the following changes:
- API keys created at the company level: when a key is created, changed, or revoked. Workspace API keys stay in that workspace's activity feed.
- SSO connections: when your connection is set up or reconfigured.
- Company admin changes: when someone is granted or loses the company admin role. In the feed, these events appear as the company owner role, under the user role entity type.
- Company-scoped Link tunnels: the same Link Agent and tunnel access events as the workspace feed, for tunnels that belong to your company.
Activity on a resource that belongs to a workspace stays in that workspace's activity feed, so the company feed doesn't repeat workspace detail.