Activity Log
The Activity Log tracks every change made to your RoleLogic configuration. It's your audit trail for understanding who changed what and when.
What Is the Activity Log?
The Activity Log records administrative actions:
- Rule creation, updates, and deletions
- Log/webhook configuration changes
- Server setting modifications
- Quota changes
Unlike webhook logs (which track role changes to members), the activity log tracks changes to RoleLogic itself.
Why Use the Activity Log?
Accountability
Know who made changes to your automation:
- "Who disabled this rule?"
- "When was this rule created?"
- "What changed in this configuration?"
Troubleshooting
Understand when things changed:
- "Did someone modify this rule recently?"
- "What was the previous configuration?"
- "When did this start behaving differently?"
Compliance
Maintain records for server governance:
- Complete audit trail
- Historical record of automation decisions
- Evidence for dispute resolution
Accessing the Activity Log
- Open the RoleLogic Dashboard
- Select your server
- Navigate to the Activity Log or System Logs section
- Browse the chronological list of changes
Understanding Log Entries
Each entry contains:
Timestamp
When the action occurred. Displayed in your local timezone.
User
Who performed the action. Shows the Discord user who made the change.
Action Type
What type of change was made:
| Action | Meaning |
|---|---|
| Create | New item was added |
| Update | Existing item was modified |
| Delete | Item was removed |
| Pause | Rule was temporarily stopped |
| Start | Rule was resumed/enabled |
| Stop | Rule was disabled |
Entity Type
What was changed:
| Entity | Description |
|---|---|
| Rule | A role automation rule |
| Log | A webhook/log configuration |
| Quota | Quota allocation or limit |
| Guild | Server-wide settings |
Details
Specific information about what changed. Depending on the action and entity, this might include:
- Rule name or ID
- What settings were modified
- Before/after values
Filtering the Activity Log
With many entries, filtering helps you find specific information.
Filter by Action Type
Show only certain actions:
- Only "Create" to see new items
- Only "Delete" to see removals
- Only "Update" to see modifications
Filter by Entity Type
Show only certain entity types:
- Only "Rule" to see rule changes
- Only "Log" to see webhook changes
- Only "Guild" to see server settings
Combined Filters
Apply multiple filters together:
- "Update" + "Rule" = All rule modifications
- "Delete" + "Log" = All webhook deletions
Activity Log Channel
You can send activity notifications to a Discord channel, similar to webhook logs but for configuration changes.
Setting Up
- Go to your server settings in the dashboard
- Find the Activity Log Channel option
- Select a Discord channel
- Enable the feature
What Gets Sent
When enabled, the channel receives messages whenever:
- Rules are created, updated, or deleted
- Logs are configured or removed
- Server settings change
This keeps your team informed about configuration changes without checking the dashboard.
Best Practices for Activity Log Channel
- Use a staff-only channel since configuration changes are administrative
- Consider a dedicated channel to avoid mixing with other logs
- Review periodically for unexpected changes
Reading Activity Details
Rule Changes
Rule-related entries show:
- Rule ID: Unique identifier
- Rule Description: The rule's name/description
- Changes: What was modified (conditions, actions, priority, etc.)
Example entry:
Update - Rule - "VIP for Boosters" Changed: Action roles modified, Priority changed from 0 to 1
Log/Webhook Changes
Webhook-related entries show:
- Log ID: Unique identifier
- Log Name: The webhook's name
- Channel: Target channel
- Changes: What was configured
Example entry:
Create - Log - "Staff Notifications" Channel: #staff-logs
Setting Changes
Server setting entries show:
- Setting Name: What setting changed
- Old Value: Previous configuration
- New Value: Current configuration
Navigation
Pagination
The activity log uses pagination for large histories:
- Previous/Next buttons to navigate
- Page X of Y indicator showing position
- Entries sorted newest to oldest (typically)
Sorting
Entries are displayed chronologically, with the most recent changes first. Some interfaces allow reversing this order.
Use Cases
Investigating Unexpected Behavior
If automation starts behaving differently:
- Open the Activity Log
- Filter to "Update" + "Rule"
- Look for recent changes
- Identify what was modified and by whom
Onboarding New Admins
Help new team members understand the automation:
- Review the Activity Log together
- Explain the history of key rules
- Show how changes are tracked
Restoring Previous Configuration
If a change caused problems:
- Find the entry in the Activity Log
- Note the previous configuration
- Manually restore the old settings
- Create a new entry showing the restoration
Security Monitoring
Watch for unauthorized changes:
- Regularly review the Activity Log
- Verify all changes were made by authorized users
- Investigate any unexpected entries
Tips for Activity Log Management
Regular Reviews
Schedule periodic reviews of the Activity Log:
- Weekly for active servers
- Monthly for stable configurations
Document Major Changes
When making significant changes:
- Make the change
- Note it in the Activity Log (automatic)
- Optionally add external documentation explaining why
Investigate Anomalies
If you see changes you don't recognize:
- Contact the user who made the change
- Verify it was intentional
- Revert if necessary
Use Descriptive Rule Names
Good rule descriptions make the Activity Log more useful:
- ✅ "Auto-VIP for Server Boosters" is clear in the log
- ❌ "Rule 7" is meaningless in the log
Comparison: Activity Log vs. Webhook Logs
| Feature | Activity Log | Webhook Logs |
|---|---|---|
| Tracks | Configuration changes | Role changes to members |
| Who | Admins modifying RoleLogic | Members affected by rules |
| What | Rules, settings, quotas | Roles added/removed |
| Where | Dashboard + optional channel | Discord channel |
| Purpose | Audit & troubleshooting | Notifications & records |
Next Steps
- Webhooks & Logging — Track role changes to members
- Troubleshooting — Diagnose issues using logs
- Best Practices — Maintain a well-documented setup