Activity Log Tab
The Activity Log tab is the complete audit trail for this device. Every action taken on the device - who added it, who edited it, status changes, checkouts, returns, and more - is automatically recorded here.
Think of the activity log as the device's permanent record. It's like a security camera that never stops recording, capturing everything that happens to the device in Manage1to1.
To view the activity log, you need:
- View Devices - Required to access device profiles
- View Activity Log - Required to view this tab
What the Activity Log Records
The activity log automatically captures:
- Device creation: When the device was first added to the system
- Edits: Any changes to device information (status, building, serial number, etc.)
- Checkouts: When the device is assigned to a user or cart
- Returns: When the device is checked back in
- Incidents: Creation of new incident records
- Status changes: Updates to device status (Active, Lost, etc.)
- Note activity: When notes are added or deleted
- Building transfers: When the device is moved to a different location
- Insurance changes: Updates to insurance information
- Case assignments: When protective cases are added or removed
Basically, if someone does something with or to the device in Manage1to1, it's logged.
Understanding the Log Entries
Each entry in the activity log shows:
- Date and Time: Precise timestamp of when the action occurred
- Who: Which administrator performed the action (or "System" for automated actions)
- What: Description of what was done
- Details: Specific changes or additional information about the action
The log is displayed in chronological order, typically with the most recent actions at the top.
Reading Log Entries
Example entries you might see:
03/20/2025 2:45 PM - John Smith
Device checked out to Williams, Sarah
03/20/2025 2:30 PM - John Smith
Device status changed from Available to Active
03/15/2025 10:15 AM - System
Device returned from Johnson, Mike
02/28/2025 9:00 AM - Jane Doe
Device building changed from Lincoln Elementary to Washington Middle
01/15/2025 3:30 PM - Jane Doe
Device added to system
Reading bottom-to-top tells the story: Jane added the device in January, moved it to a different building in February, it was returned by Mike in mid-March, then John checked it out to Sarah later that day.
Common Log Entries Explained
Device Added
01/15/2025 3:30 PM - Jane Doe
Device added to system
Serial: ABC123456, Asset: 12345
This is always the first entry for any device - when it was initially created in Manage1to1. It shows who added it and may include initial details like serial number and asset tag.
Checkout Actions
03/20/2025 2:45 PM - John Smith
Device checked out to Williams, Sarah
Records when a device was assigned to a user. The entry shows who performed the checkout and who received the device.
Return Actions
03/15/2025 10:15 AM - System
Device returned from Johnson, Mike
Logs when a device was checked back in. If it says "System," the return may have been automated (like during a bulk return process).
Device Edited
03/10/2025 1:20 PM - Jane Doe
Device information updated
Changed: Status (Active → In Repair)
Changed: Building (Lincoln Elementary → District Office)
Shows when device details were modified. Good activity logs will list exactly what changed, showing both the old and new values.
Status Changes
02/15/2025 11:00 AM - John Smith
Device status changed to Lost
Tracks when the device status was updated. This is important for accountability - you can see who marked a device as lost, sold, or returned it to active status.
Incident Created
03/05/2025 9:15 AM - Jane Doe
Incident #456 created
Type: Screen Damage
Records when a new incident (repair/problem report) was created for the device.
Note Activity
03/01/2025 4:30 PM - John Smith
Device note added
02/28/2025 2:15 PM - Jane Doe
Device note deleted
Tracks when administrators post or remove notes from the Notes tab. While the content of the note isn't shown here, you can see who added or deleted it and when.
Why the Activity Log Matters
The activity log serves several critical purposes:
Accountability
Every action has a timestamp and username attached. If something goes wrong or there's a question about when something happened, the activity log provides answers.
Example: "Who checked out this device to the student who lost it?"
- Activity log shows exactly who, when, and to whom
Troubleshooting Timeline
When tracking down problems, the activity log helps you build a timeline of events.
Example: A device is damaged, and you need to know when it was last working fine.
- Check the activity log to see when it was last returned in good condition
- See when it was checked out to the current user
- Compare to when incidents were created
Audit Trail
For compliance, billing disputes, or legal purposes, the activity log provides an unalterable record of what happened.
Example: A parent disputes when their child received a damaged device.
- Activity log proves the checkout date
- Shows the device's status at time of checkout
- Documents any incidents created before or after the assignment
Change Tracking
If device information has been modified, the activity log shows what changed and who changed it.
Example: A serial number was updated incorrectly.
- Activity log shows the original value
- Shows who changed it and when
- Helps you restore the correct information
Common Use Cases
Scenario 1: Investigating a Lost Device
A device is marked as lost, and administration wants to know what happened:
- Open the device profile
- Go to Activity Log tab
- Review the timeline:
- When was it last checked in?
- Who checked it out most recently?
- When was it marked as lost?
- Who marked it as lost?
- Use this information to contact the responsible parties
Scenario 2: Verifying Device History for Insurance Claim
You're filing an insurance claim and need to document the device's history:
- Activity Log shows:
- When the device was purchased/added (proves age)
- Checkout history (proves it was in use)
- Incident creation dates (proves when damage occurred)
- Who reported the damage
- Export or screenshot relevant log entries for the claim
Scenario 3: Training a New Staff Member
A new tech coordinator asks "What happened to this device?":
- Pull up the Activity Log
- Walk through the timeline from bottom to top
- Show them the complete history:
- Initial setup
- Assignments
- Repairs
- Status changes
- They now understand the device's full story
Scenario 4: Identifying Who Made an Error
A device's building assignment was changed incorrectly:
- Check Activity Log for "building changed" entries
- See who made the change and when
- Contact that person to understand why
- Correct the error if needed
- Use as a training opportunity if it was a mistake
Scenario 5: Compliance Audit
Your district is being audited and needs to prove device tracking accuracy:
- Auditor asks: "Can you prove this device was assigned to Student X on Date Y?"
- Activity Log provides:
- Checkout timestamp
- Who performed the checkout
- Duration of assignment
- Return date
- Unalterable log satisfies audit requirements
What You Won't See in the Activity Log
The activity log focuses on actions taken on the device record in Manage1to1. You won't find:
- Incident details: What was wrong or how it was fixed (see Incident History tab)
- Note content: What was written in notes (see Notes tab)
- Physical device usage: When the device was actually used by the student
- MDM activity: Mobile device management events (tracked by your MDM system)
- Web/app activity: What the user did on the device
The activity log only tracks what happens to the device record in Manage1to1, not what happens to the physical device in the real world.
System-Generated vs. User Actions
Some log entries show "System" as the actor instead of a specific administrator. This indicates automated actions:
System-generated entries typically include:
- Bulk import operations
- Automated returns
- Integration updates (MDM sync, SIS sync)
- Scheduled maintenance tasks
- API-triggered changes
These are legitimate entries - they just weren't performed manually by a person clicking in the interface.
Retention and Permanence
Activity log entries are permanent and cannot be deleted or edited. This is intentional - the log must be trustworthy as an audit trail.
Key points about log retention:
- Entries are never automatically purged
- Administrators cannot delete log entries
- Entries cannot be modified after creation
- The log goes back to when the device was first added
- Even if a device is deleted, the log is typically archived for compliance
This permanence is what makes the activity log valuable for accountability and compliance purposes.
Privacy and Access Control
The activity log may contain sensitive information:
- Which students were assigned devices
- When devices were marked as lost (potential disciplinary info)
- Who made errors or corrections
Access considerations:
- Only administrators with View Activity Log permission can see this information
- Your district should have policies about who needs this permission
- Log data may be subject to record requests or legal discovery
- Use log information professionally and only for legitimate business purposes
Exporting or Printing the Log
While the activity log is viewable on screen, you might need to export it for:
- Audit documentation
- Incident investigation reports
- Insurance claims
- Legal proceedings
Most browsers allow you to:
- Print the page (File > Print or Ctrl/Cmd+P)
- Save as PDF during the print dialog
- Screenshot specific log entries
For formal exports, check with your system administrator about reporting capabilities.
Tips for Using the Activity Log
✅ Best Practices:
- Review the activity log when something seems wrong - it often explains mysteries
- Cross-reference with other tabs (Checkout History, Incident History) for complete context
- Use the log to train new staff on proper procedures by showing examples
- Check the log before accusing someone of an error - it might have been automated
- Document important log entries (screenshot or note the details) for records
⚠️ Things to Remember:
- The log shows what happened in the system, not necessarily what happened in real life
- Timestamps are based on server time - verify time zone if precision matters
- "System" entries are legitimate automated actions, not errors
- Absence of a log entry doesn't mean something didn't happen - it might have occurred outside Manage1to1
Comparing Activity Log to Other Tabs
It's easy to confuse when to use the activity log versus other device tabs:
| Need to Know | Activity Log | Checkout History | Incident History |
|---|---|---|---|
| Who checked out the device | ✅ Shows checkout action | ✅ Shows complete checkout record | ❌ |
| When device was returned | ✅ Shows return action | ✅ Shows return date | ❌ |
| What repairs were done | ❌ | ❌ | ✅ Complete repair details |
| Who edited the device | ✅ Shows all edits | ❌ | ❌ |
| When status changed | ✅ Shows status changes | ❌ | ❌ |
| Problem descriptions | ❌ | ❌ | ✅ Full incident notes |
| Who added notes | ✅ Note creation logged | ❌ | ❌ |
| Complete chronology | ✅ Everything together | ❌ Just checkouts | ❌ Just incidents |
Use the activity log when you need the "big picture" timeline that includes ALL actions.
Common Questions
Q: Can I delete entries from the activity log? No. The activity log is a permanent audit trail and cannot be edited or pruned. This ensures the log's integrity for accountability purposes.
Q: Why doesn't the log show what was in a deleted note? The activity log tracks that a note was deleted (and who deleted it), but doesn't store the content of deleted items. This is why deleting notes is permanent.
Q: How do I know if an entry is from a person or automation? Entries performed by administrators show the admin's name. Automated actions show "System" or the name of the automated process.
Q: Can I see activity logs for devices that were deleted? This depends on your system configuration. Some districts archive device records and logs when devices are deleted; others don't. Check with your system administrator.
Q: What timezone are the timestamps in? Timestamps are typically in your server's configured timezone. This should match your school's timezone, but verify with your system administrator if precision is critical.
Q: Why are some log entries vague? Older entries or entries from certain automated processes may have less detail than newer manual actions. The level of detail has improved over different versions of Manage1to1.
Q: Can I filter the activity log to show only certain types of actions? This depends on your specific Manage1to1 version. Some implementations allow filtering; others show all entries chronologically. Use your browser's search function (Ctrl/Cmd+F) as a workaround.
Next Steps
The Activity Log gives you the complete chronological record of what's happened to the device. To understand the context behind these actions:
- Device Information - See current device details
- Checkout History - Detailed checkout records
- Incident History - Full repair and incident information
- Notes - Administrator context and communication
Together, these tabs tell the complete story of the device from every angle!