remFREE records operational information at different levels because execution history and human-readable activity answer different questions.
Two important views are Jobs and the Activity Wall.
Jobs
Jobs are execution records for actions sent to managed endpoints.
Examples can include:
- inventory collection
- script execution
- command execution
- screenshots
- patch actions
- supported agent operations
A job can contain information such as:
- target device
- job type
- current state
- timestamps
- result information
- error information
Use Jobs when you need to answer:
What happened to this specific task?
Activity Wall
The Activity Wall provides a broader operational view.
It is intended to answer:
What has been happening across this organization?
Activity can include categories such as:
- devices
- operations
- compliance
- inventory
- remote support
- security
- system activity
The Activity Wall translates technical events into a more human-readable operational story.
Why both views exist
One user action may result in several technical operations.
Likewise, a low-level job may matter for troubleshooting without being important enough to dominate the fleet-wide operational feed.
Jobs therefore remain the detailed execution history.
The Activity Wall provides the broader narrative.
Security activity
Security-related events can also appear in Activity.
Examples include:
- successful sign-ins
- failed sign-in attempts
- logout events
- other supported authentication activity
This makes it possible to review operational and security context from the same general timeline.
Audit Logs
Audit Logs serve another related but distinct purpose.
They focus on administrative accountability.
A useful mental model is:
Jobs = What happened to this task?
Activity Wall = What has been happening?
Audit Logs = Who did what?
These records may overlap, but they are designed to answer different operational questions.
Why this matters
Good administration requires more than knowing that a command finished.
Teams often need to reconstruct:
- what changed
- who initiated the change
- which endpoint was affected
- what the endpoint returned
- what happened around the same time
remFREE keeps these layers separate so detailed evidence remains available without making the everyday interface impossible to read.