Skip to main content

Activity Logs

Track and review records of user activities within the system, providing a detailed log of key actions for auditing and monitoring purposes. Activity Logs capture who did what and when, creating an audit trail of all significant changes made to your Mumara installation.

Navigate to Tools → Logs → Activity Logs to access the activity log.


Activity Logs Table

The main page displays a chronological list of user activities with the most recent actions at the top.

Controls

ControlDescription
Show entriesControl how many activity records are displayed per page - increase this to review more activities at once or keep it low for faster loading
SearchFind specific activities by typing keywords - searches across user names, activity types, and descriptions to quickly locate particular actions

Table Columns

ColumnDescription
IDA unique sequential identifier for each logged activity - useful for referencing specific events in support requests or internal discussions
NameThe name of the user who performed the action - helps identify who made specific changes, which is essential for accountability in multi-user environments
ActivityThe type of action performed: Created, Updated, or Deleted - allows you to quickly identify the nature of the change at a glance
DescriptionA detailed explanation of what was done, including the name of the affected item (shown as a clickable link when the item still exists) and who performed the action
Created onThe exact date and time when the activity occurred - essential for correlating activities with reported issues or tracking when specific changes were made

Activity Types

Actions are categorized into three types:

Activity TypeDescription
CreatedA new item was added to the system - this includes creating lists, segments, custom fields, broadcasts, triggers, sending domains, and other configurable elements
UpdatedAn existing item was modified - this captures changes to settings, configurations, or properties of existing items, showing when and who made the modification
DeletedAn item was removed from the system - this logs when users delete lists, contacts, custom fields, or other items, providing an audit trail even after the item no longer exists

What Gets Tracked

Activity Logs capture virtually all significant actions performed within the system. Any time a user creates, modifies, or deletes something in Mumara, it gets recorded in the Activity Log. This provides a comprehensive audit trail across the entire application.

Common Tracked Activities

While the logging covers all areas of the application, here are some of the most commonly tracked items:

  • Lists and Segments - Creating, editing, and deleting contact lists and segments
  • Custom Fields - Adding, modifying, or removing custom contact fields
  • Sending Domains - Configuring and updating domain authentication settings
  • Broadcasts and Campaigns - Creating, scheduling, modifying, and deleting email campaigns
  • Evergreen Campaigns - Setting up and modifying recurring campaigns
  • Triggers and Automations - Creating and managing automation rules
  • Drip Groups - Setting up drip sequences
  • Sending Nodes - Adding and configuring SMTP servers
  • Bounce and FBL Addresses - Configuring bounce handling and feedback loops
  • Users and Permissions - Creating user accounts, changing roles, and modifying access
  • Packages - Assigning and modifying user package allocations
  • API Keys - Creating and revoking API access tokens
  • Web Forms - Creating and editing subscription forms
  • Suppression Lists - Adding and removing suppression entries
  • Application Settings - Changing system configurations

This is not an exhaustive list - essentially any configuration change, content modification, or administrative action gets logged for accountability and troubleshooting purposes


Reading Activity Descriptions

The Description column provides context about each action:

Description Format

Descriptions follow a consistent pattern that includes:

  • What was affected - The type of item (Custom field, Sending Domain, Segment, etc.)
  • Item name - A clickable link to the affected item (if it still exists)
  • Action taken - What happened (has been created, has been deleted, has been edited)
  • Who did it - The user who performed the action (shown as a clickable link)

Examples

DescriptionMeaning
"Custom field Phone Number has been deleted"A custom field named "Phone Number" was removed from the system
"Custom field Company Name has been added"A new custom field named "Company Name" was created
"Sending Domain mail.example.com has been edited by John"User John modified the sending domain configuration
"Segment Engaged Users has been created"A new segment with that name was created
"List Newsletter Subscribers has been deleted by Sarah"User Sarah deleted a contact list

Item names and user names in descriptions are displayed as clickable links (shown in teal/cyan color). Clicking these links navigates directly to:

  • The item's detail or edit page (if the item still exists)
  • The user's profile page

For deleted items, the link may no longer work since the item no longer exists, but the name is preserved in the log for reference.


Using Activity Logs

Auditing Changes

Activity Logs serve as an audit trail showing who made changes and when:

  • Track configuration changes - See when sending domains, custom fields, or other settings were modified
  • Monitor user actions - Review what specific users have been doing in the system
  • Investigate issues - If something stopped working, check what was recently changed that might have caused it

Security Monitoring

Use Activity Logs alongside Authentication Logs for comprehensive security monitoring:

  • Detect unauthorized changes - If an item was modified unexpectedly, the Activity Log shows who did it
  • Review user behavior - Monitor if users are performing actions outside their normal scope
  • Mass operations - Identify if someone is bulk-deleting items or making unusual numbers of changes

Troubleshooting

When something goes wrong:

  1. Note the timeframe - When did the problem start?
  2. Search Activity Logs - Look for changes around that time
  3. Identify recent modifications - See what was created, updated, or deleted
  4. Correlate with the issue - Determine if a recent change caused the problem
  5. Revert if necessary - Undo the problematic change

Best Practices

Regular Review

  • Check periodically - Review Activity Logs weekly to stay aware of changes being made in your system
  • After issues - When problems occur, Activity Logs are often the first place to check for recent changes
  • Before updates - Review recent activities before applying system updates to ensure the system is in a known state

Multi-User Environments

  • Establish accountability - Activity Logs make it clear who made each change, encouraging responsible behavior
  • Train users - Ensure users know their actions are logged for security and accountability
  • Review unusual patterns - Watch for users making unexpected types of changes

Documentation

  • Document major changes - Use Activity Logs to create records of when significant configurations were modified
  • Export for compliance - If your organization requires audit trails, Activity Logs provide the necessary history
  • Reference in support requests - When contacting support, Activity Log entries can help explain what was changed and when

Troubleshooting

Activities Not Being Logged

Possible causes:

  • Logging may be disabled in settings
  • Database write issues
  • The specific action type isn't tracked

Solutions:

  • Verify activity logging is enabled in Application Settings
  • Check database connectivity and permissions
  • Note that not every action in Mumara generates an Activity Log entry - only significant changes are tracked

Cannot Find Specific Activity

Possible causes:

  • Activity is outside the retention period
  • Wrong search terms
  • Activity wasn't logged (minor actions may not be tracked)

Solutions:

  • Use the Search box with different keywords
  • Check the date range - older activities may have been purged
  • Try searching by user name instead of item name

This is expected behavior. When an item is deleted, the Activity Log preserves the record showing what was deleted, but the link to the item no longer works because the item no longer exists. The log entry itself remains as a historical record.


Next Steps