Activity Log

The Activity Log is a centralized audit trail that records every meaningful change within your organization. It provides a transparent, chronological history of how your plugins, themes, and site environments are being managed.

Note

Plan Requirement: The full Activity Log is a premium feature. It is currently available exclusively for users on the Enterprise plan.

The Value of Auditing

In a collaborative environment, knowing who changed what and when is critical for maintaining the integrity of your fleet. The Activity Log serves three primary functions:

1. Accountability: Track deployments and configuration changes made by different team members.
2. Troubleshooting: Identify the exact moment an environment was toggled or a URL was updated to correlate with site behavior changes.
3. Governance: Maintain a permanent record of asset imports and deletions for internal compliance or security reviews.

Understanding the Log Entries

Each entry in the log captures a specific “Snapshot” of an action taken within the portal.

Action Types

The Action column categorizes the event. Common categories include:

• Asset Management: Actions like asset.imported, asset.deleted, or asset_version.created.
• Environment Controls: Actions like site_environment.enabled or site_environment.disabled.
• Configuration Updates: Actions like site_environment.url.updated.

Detailed Descriptions

The Description field provides a human-readable summary of the event. For example:

• “Enabled environment ‘Stage’ for site ‘www.example.com’”
• “Updated Dev URL from ‘https://old.test’ to ‘https://new.test’ for site ‘www.example.com’”
• “Imported theme ‘Cafeteria Elementor’ from WordPress Repository”

Metadata and Origins

To provide full context, every log entry includes:

• The Target: The specific Company, Site, or Asset affected by the action.
• The Origin IP: The IP address of the user who performed the action, which is vital for security audits.
• The Timestamp: The exact date and time the event was recorded in the database.

Navigating the History

The Activity Log is designed to handle high volumes of data as your organization grows.

• Chronological Order: The most recent events always appear at the top.
• Pagination: The log uses a paginated interface (e.g., 15 items per page), allowing you to scroll back through weeks or months of history.
• Deep Links: Many log entries include references to the specific sites or assets involved. This allows you to jump from an audit entry directly to the management screen for that resource.

Common Use Cases

• Deployment Verification: Confirm that a developer successfully pushed a new plugin version to the “Production” environment at the scheduled time.
• Connection Audits: See when a site was toggled to “Inactive” to verify when repository access was revoked for a project.
• Public Import Tracking: Monitor which public plugins or themes have been “adopted” into your private vault and by whom.

Best Practices

• Review After Rollouts: Following a major update to your fleet, review the log to ensure all expected environment toggles and site syncs were recorded correctly.
• Correlate with Support: If an internal user reports an issue with a specific site, use the log to see if any environment URLs or status toggles were changed recently for that installation.
• Monitor for Anomalies: Periodically scan the “IP Address” column to ensure all administrative actions are originating from recognized team networks.