Logs And Audit Trails

Use logs when you need to understand what happened, who made a change, or why something looks different now.

Logs are most useful after a staff update, when a member says their profile changed unexpectedly, or when an automation did not behave the way you expected.

Workflow: Review Profile Activity Logs

Prerequisites

• You have a profile open.
• You want to see the history of changes for that person.
• You know roughly when the change happened, if you are trying to find one specific event.

Steps

1. Open a profile detail page.
2. Open the Logs section.
3. Read the entries from top to bottom.
4. Use the page controls if there are many entries.

Expected Result

• You can see a timeline of changes for that person.
• Each entry tells you what changed, who made the change, and when it happened.

What To Look For

• Rank changed means someone updated the person's rank.
• Unit changed means the person was moved to another unit or team.
• Status updated means a profile status was added, changed, or removed.
• Avatar updated or Background updated means the profile picture or banner changed.

Common Issues

• Old entries may be missing a name for a deleted item. The log is still useful because it usually shows the action and the person who made it.
• Logs can be long, so start near the top if you are looking for the latest change.
• If an entry looks strange, check whether the profile was edited by another staff member or by an automated process.

Workflow: Review Automation Execution Logs

Prerequisites

• You want to check an automation run.
• You know which event triggered the automation, or at least the rough time it ran.
• You can open the Automation Logs area.

Steps

1. Open Automation -> Logs.
2. Filter by query, event type, and status.
3. Read the flow name, step name, message, and any extra details.
4. Narrow the list if you are looking for one specific run.

Expected Result

• You can see whether the automation succeeded, failed, or is still running.
• The log helps you understand which step stopped and what the last message was.

What The Fields Mean

• Event type is the thing that triggered the automation, such as a profile update or a form submission.
• Flow is the automation itself.
• Step is one action inside that flow.
• Status shows whether the step completed successfully or hit a problem.
• Message is the short explanation of what happened.
• Details usually contains extra context that helps you or another staff member troubleshoot.

Common Issues

• Too many filters can hide the log you need. Remove one filter at a time.
• A failure message may be brief, so read the details carefully if you need the full story.
• If the log shows repeated failures, the automation itself may need to be adjusted before it can run cleanly again.

Workflow: Verify Role Assignment And Submission Review Trails

Prerequisites

• You are checking a staffing or review decision.
• You have the relevant profile, role, form, or submission page open.

Steps

1. For role assignment, check whether the person was successfully added or removed from the role.
2. For submissions, read the status and comments to see how the review progressed.
3. Look for a trail of actions if you need to explain why the final result was reached.

Expected Result

• You can tell whether a change was completed, rejected, or only partially finished.
• Review comments explain the decision in plain language.

Common Issues

• A bulk role change might partly succeed, so always check the individual results.
• A submission may have no comment yet if the reviewer has not written one.
• If the current status looks unclear, review the history before assuming someone made a mistake.

Related Pages

• Automation Flows
• Personnel Workflows
• Events, Forms, And Applications
• Errors And Troubleshooting