Audit Log

Every administrative action in fellos is logged — see who did what, when, and why.

The audit log is your organization's permanent record of all administrative activity. Every time an admin creates, updates, deletes, approves, or declines something in fellos, an entry is recorded with full details: who performed the action, what was changed, when it happened, and what specifically changed. This log cannot be edited or deleted, ensuring a tamper-proof record of all administrative decisions.

The audit log is a governance and accountability tool. Use it to track admin activities, investigate issues, resolve disputes, and maintain a comprehensive record of changes to your organization's data and configuration.

Audit Log Complete record of all administrative actions ENTITY TYPE All entities DATE RANGE 2026-03-01 to 2026-04-06 ACTOR Search by name... Filter DATE ACTOR ACTION ENTITY DETAILS Apr 6, 2026 10:42 AM RT Root update User Alex K. Changed member_type Seedling → Full Member Apr 5, 2026 3:18 PM RT Root create Organization Oakmont Chapter Created new organization Parent: Northeast Region Apr 5, 2026 2:05 PM JD Jake D. approve Membership Maria R. Approved onboarding request Type: Full Member Apr 4, 2026 11:30 AM RT Root update Group Announcements Changed locked false → true Apr 3, 2026 9:15 AM SR Sarah R. decline Membership Tom H. Declined transition request Prospect → Full Member Load More
The Audit Log — filter controls at the top (entity type, date range, actor), with a chronological table of administrative actions showing realistic entries.

Viewing the Log

The audit log displays a chronological list of administrative actions, with the most recent entries at the top. Each log entry contains:

  • Date and time — When the action occurred, displayed with both the date and precise time.
  • Actor — The person who performed the action, shown with their avatar and name. This is always a specific user — system actions are attributed to "System."
  • Action — What was done. Actions include: create (something new was added), update (something was changed), delete (something was removed), approve (a request was approved), and decline (a request was rejected).
  • Entity — What was affected. Entity types include: user, organization, group, event, membership, member_type, attachment, governance_role, and configuration settings.
  • Details — Additional context about the action. For updates, this shows the specific field that changed and the old and new values (e.g., "member_type: Seedling to Full Member"). For creates, it shows what was created. For approvals and declines, it shows the workflow request that was acted on.

Filtering the Log

The filter bar at the top of the audit log lets you narrow down the entries you're viewing. You can filter by:

Entity Type

Use the entity type dropdown to show only actions affecting a specific type of entity. For example, selecting "User" shows only actions related to user accounts — profile updates, type changes, deactivations, etc. Selecting "Organization" shows only org-related actions like creating, renaming, or restructuring organizations.

Available entity types include:

  • User — Member account actions (profile changes, type changes, deactivations)
  • Organization — Organizational unit actions (create, rename, restructure, delete)
  • Group — Discussion group actions (create, update access rules, delete)
  • Event — Event actions (create, update, cancel, delete)
  • Membership — Membership workflow actions (onboarding, transitions, deactivations)
  • Member Type — Member type configuration changes
  • Attachment — Document and file actions
  • Configuration — System settings changes (branding, theme, integrations)

Date Range

Set a start and end date to view actions within a specific time period. This is useful for investigating what happened during a particular week or month, or for generating activity reports for governance meetings.

Actor

Search for a specific administrator by name to see all actions they performed. This is useful for reviewing a specific admin's activity or for accountability purposes.

Tip

You can combine filters. For example, filter by entity type "User" + actor "Root" + date range "last 7 days" to see all user-related actions performed by the Root admin in the past week.

Understanding Log Entries

The details column provides the most valuable information for understanding what happened. Here's how to read different types of entries:

Update entries

For updates, the details show which field was changed and the old and new values. For example:

  • "Changed member_type: Seedling to Full Member" — A user's member type was changed from Seedling to Full Member
  • "Changed locked: false to true" — A group was changed from open to locked
  • "Changed name: Eagles Club to Benevolent Order of Eagles" — An organization was renamed

Create entries

For creates, the details describe what was created and any relevant initial values:

  • "Created new organization, Parent: Northeast Region" — A new org was created under the Northeast Region
  • "Created group: Safety Committee, Section: Committees" — A new discussion group was added

Approval and decline entries

For workflow actions, the details show the request type and relevant context:

  • "Approved onboarding request, Type: Full Member" — A membership application was approved
  • "Declined transition request: Prospect to Full Member" — A type change request was rejected

Pagination

The audit log uses cursor-based pagination. The initial view shows the most recent entries. Click Load More at the bottom to see older entries. Each load fetches the next batch of entries, continuing back in time.

Cursor-based pagination ensures consistent results even as new entries are added while you're browsing. You won't see duplicate or missing entries when loading more pages.

Good to know

The audit log is append-only — entries cannot be edited, deleted, or tampered with by anyone, including site admins. This ensures the log serves as a reliable, trustworthy record of all administrative activity. If an action was taken, it's in the log.

Common Use Cases

Investigating an issue

If a member reports that their profile was changed unexpectedly, filter the audit log by entity type "User" and the member's name. You'll see every administrative action that affected their account, with timestamps and the admin who made each change.

Governance reporting

Before a board meeting, filter the log by the period since the last meeting. This gives leadership a complete overview of all administrative actions taken, including member changes, organizational updates, and configuration modifications.

Tracking admin activity

If you have multiple administrators, use the actor filter to review each admin's actions. This helps ensure that administrative powers are being used appropriately and consistently.

Auditing workflow decisions

Filter by entity type "Membership" to see all onboarding approvals, transition decisions, and deactivations. Each entry shows who made the decision and when, creating a clear paper trail for membership changes.

Configuration change tracking

Filter by entity type "Configuration" to see when and by whom system settings were changed — branding updates, theme changes, integration configurations, and other platform-wide modifications.