Activity Logs
An activity log is a diary of who did what. In everyday life it is the sign-in book at a building desk. In CROForge it answers questions such as who changed an experiment status, who invited or removed a user, and when a metric or segment was updated. There are two views: User activity (one person’s actions) and Workspace activity (broader events for the whole workspace). Owners and Admins use these logs after unexpected pauses and during security reviews.
Words used on this page
| Word | Everyday meaning | Meaning in CROForge |
|---|---|---|
| Activity log | A diary of who did what, and when. | The audit records under Settings. Split into User activity and Workspace activity for the current workspace. |
| User activity | One person’s diary. | Actions attributed to a specific user (invites they sent, experiments they paused, and similar). |
| Workspace activity | The office-wide diary. | Broader workspace events, not limited to a single person you already have in mind. |
| Audit | Checking the record after something happened. | Using these logs to reconstruct access and changes during a security review or an unexpected experiment pause. |
| User | A person on the team. | The account an action is attributed to in User activity. |
| Workspace | A team’s private work area. | Logs are scoped to this workspace. They do not show another workspace’s history. |
| Owner | The person with the master key. | Typically has full view of activity logs and uses them to review access. |
| Admin | A trusted manager. | Typically can view activity logs to investigate invites, removals, and experiment changes. |
| Member | A regular teammate. | May have limited log access. See Roles and permissions for the matrix. |
| Experiment | A controlled A/B test. | Status changes (for example paused) appear in the logs so you can see who changed them. |
| Experiment status | Whether the test is draft, running, paused, and so on. | A common reason to open the log: “Who paused this?” |
| Invitation | A request to join the team. | Invite and remove actions are logged so you can see who added or dropped access. |
| Metric | A success number you defined. | Updates to a metric definition can appear in the log. |
| Segment | A named group of visitors. | Updates to a segment can appear in the log. |
| Settings | The control room. | User activity and Workspace activity live here: Settings → User activity and Settings → Workspace activity. |
| Security review | Checking who had keys, and when. | A client use of logs: reconstruct who had access at a given time. |
Screenshot placeholder for this page: activity-log.png. Replace that file with a real screenshot and keep the same filename.
Why activity logs exist
Workspaces hold live experiments and visitor measurement. When something unexpected happens, you need a written trail rather than memory. Activity logs help Owners and Admins answer:
- Who changed an experiment status (for example paused a running test)?
- Who invited or removed a user?
- When was a metric or segment updated?
The two types of log
| Log | Everyday meaning | Scope in CROForge |
|---|---|---|
| User activity | One person’s diary. | Actions attributed to a specific user. Start here when you already know whose account to inspect. |
| Workspace activity | The office-wide diary. | Broader workspace events. Start here when you know “something changed” but not who. |
Open them from Settings:
- User activity —
/workspace/{id}/settings/user-activity - Workspace activity —
/workspace/{id}/settings/workspace-activity
How to use the logs
- If an experiment paused unexpectedly, open Workspace activity first and look for status changes around that time.
- If you need to know what one person did, open User activity for that account.
- After someone leaves, confirm they were deactivated on Settings → Users, then check the logs for their last invite, edit, or status change.
- During a security review, use both logs to reconstruct who had access when.
Client tips
- Check logs after unexpected experiment pauses before you relaunch.
- Use logs during security reviews (who had access when).
- Keep profile names accurate so diary rows are easy to read.
User activity answers “what did this person do?” Workspace activity answers “what happened in this office?” Use both; they are not duplicates.
Developer notes
These files are frontend code, not screens in the product. They are the programs that load activity data for the Settings pages:
lib/userActivity.ts— services for per-user activity (the User activity view).lib/activityLog.ts— services for workspace-wide activity (the Workspace activity view).
