Admin Activity log actions reference
NAVIGATION Admin > Activity
PERMISSIONS Datto EDR administrator
Overview
The Activity log records every successful change made in Datto EDR by a signed-in user or API token. This reference article lists the actions that can appear in the log, explains what each one means, and explains what is not recorded. It is written for support engineers and partner admins who need to find out who changed what, and when.
Activity page
The Activity page has two tabs: General (user and API changes) and License (license allocation changes).
General tab
The General tab lists every successful change request made by a signed-in user or API token.
| Column | Description |
|---|---|
| User | The user who made the change, or the user who owns the API token that was used. Click to filter the log to that user. |
| Item | The type of object that was changed (for example Policy, Agent, or User). Some internal names are shown with a friendlier label — see Item name translations. |
| Action | The name of the operation that was performed. Click to open the detail dialog (titled “Request Parameters”) showing the full request data. |
| Item ID | The ID of the object that was changed. For bulk actions this may be blank, because the affected objects are listed in the detail data instead. |
| On | The timestamp of the change, in the browser’s local timezone. |
NOTE Activity entries are kept for 1 year. Older entries are purged automatically.
License tab
The License tab is a separate log of license allocation changes. Each device and license type gets its own row.
| Column | Description |
|---|---|
| Hostname | The device name. Shows <deleted> if the device no longer exists. |
| Device Id | The unique ID of the device. Matches the agentIds field in General tab detail data. |
| Type | The license type: EDR or AV. |
| Action | Added — a license was assigned. Removed — a license was removed. Failed to add — a license could not be assigned. |
| Reason | The cause of the action. See the table below. |
| Created On | The timestamp of the license change. |
The possible values for the Reason column are:
| Reason | When it occurs |
|---|---|
| Manual User Allocation | A user assigned a license to the device (Action = added). |
| Manual User Removal | A user removed a license from the device (Action = removed). |
| New Device Registered | A license was assigned automatically when a new device registered (Action = added). |
| License Count Exceeded | A new device registered but no license was available (Action = failed to add). Note: the misspelling is how the value appears in the product. |
| License Count Increased | The purchased license count went up and waiting devices received licenses (Action = added). |
| License Count Reduced | The purchased license count went down and licenses were removed from devices (Action = removed). |
| Device Was Deleted | The device was deleted, so its license was released (Action = removed). |
| Device Was Marked For Uninstall | The device was set to uninstall, so its license was released (Action = removed). |
How entries are recorded
The Activity log is not a hand-picked list of events. The server records an entry automatically for every successful change request made by a signed-in user or by an API token. The Item column is the type of object that was changed, and the Action column is the name of the operation that changed it.
- Only changes are logged (POST, PUT, PATCH, DELETE requests). Viewing, listing, searching, and exporting via GET are never logged.
- Only successful requests are logged. A request that failed or was denied (HTTP status 300 or higher) does not create an entry.
- The request must be authenticated with a user session or a Personal Access Token (API key). API activity therefore appears under the user who owns the token.
- Some action names are converted to friendlier words (see Standard actions below). Others appear exactly as the internal operation name, such as
patchAttributesorassignToOrganization. - Passwords, tokens, and encrypted fields (for example integration secrets) are removed from the stored details.
Item name translations
Some internal object names are displayed with a friendlier label in the Item column:
| Internal object name | Shown in Item column |
|---|---|
UserIdentity
|
User |
Target
|
Location |
UserTask
|
Task |
FileRep
|
File |
ScheduledJob
|
Job |
Box* objects (for example BoxConnection) |
Prefix removed (for example Connection) |
Scan* objects (for example ScanExtensionInstance) |
Prefix removed (for example ExtensionInstance) |
Reading the detail dialog
Clicking an Action value opens the detail dialog, titled “Request Parameters”. It shows the data that was sent with the change request and has up to three parts:
| Part | What it contains |
|---|---|
| Remote IP | The IP address the request came from, taken from the X-Forwarded-For header. If several comma-separated addresses are listed, the first is the user’s address and the rest are proxies or load balancers. This part is hidden if no address was recorded. |
| <Item> <Action> and an ID | The same Item and Action as the row, followed by the Item ID of the object that was changed. For bulk actions the ID is often blank, because the affected objects are listed in the Data instead. |
| Data | A JSON view of everything that was sent with the request. URL path values, the request body, and query-string values are merged into one object. If the same field name appears in more than one source, only one value is shown (query string wins over body, and body wins over URL path). Passwords, tokens, and encrypted secrets are removed before the entry is saved. |
Common fields in the Data
| Field | Meaning |
|---|---|
policyId, or filter.where.id on Policy actions |
The policy that was acted on. |
organizationId
|
The organization (customer or site) the change was applied to. |
locationId
|
The location the change was applied to. |
deviceGroupId
|
The device group the change was limited to. null means no group: the change applies to the whole organization or location. |
policyAssignmentId, or numbered keys "0", "1" … |
Policy assignment IDs. An assignment is the link between a policy and an organization or location, so it has its own ID, separate from the policy ID. A list of IDs is shown with numbered keys. |
agentIds, or filter.id.inq |
The devices (Device IDs) that were acted on. These match the Device Id column on the License tab. |
where / filter / organizationFilter |
The selection the user had on screen for a bulk action (for example “all devices in location X”). It shows how devices were chosen. Use agentIds for the actual list. |
data (inside a Policy entry) |
Every setting of the policy, as saved. |
name, type, active |
The object’s name, its type (for example edr, av, response), and whether it is enabled. |
userId
|
The user who made the request (the same person as the User column). |
- Backslashes are doubled in JSON:
"C:\\\\Users\\\\bob"meansC:\Users\bob. The prefix\\\\?\\on file paths is the Windows long-path prefix and is part of the path. \u0027is an apostrophe (‘) and\"is a quotation mark.- Times ending in Z are UTC (for example
2026-10-26T12:09:29Zis 12:09 UTC). - Policy schedules are stored as a cron expression: minute, hour, day of month, month, day of week.
"0 12 * * 1,3,5"means 12:00 on Monday, Wednesday, and Friday. Days of the week are numbered 0 = Sunday to 6 = Saturday. Thetimezonefield states which time zone the hour uses. nullmeans “not set / none”. An empty list[]means “no items”.
The IDs below are shortened placeholders. Real entries contain full UUIDs.
Example 1 — A policy’s settings were changed
Row: Item = Policy, Action = patchAttributes, Item ID = <policy-id>
{
"data": {
"rtsEnabled": true,
"rtsScripts": false,
"scheduledScan": true,
"scheduleOptions": {
"expression": "0 12 * * 1,3,5",
"timezone": "America/Toronto",
"weekdays": [null, true, null, true, false, true, null]
},
"tamperProtectionEnabled": true
},
"name": "EDR real time monitor",
"type": "edr",
"active": true,
"hash": "bca17f...",
"updatedOn": "2026-10-26T12:09:29.726Z"
}
How to read it: The EDR policy “EDR real time monitor” was saved. Real-time monitoring is on, script monitoring is off, and tamper protection is on. Scheduled scans run at 12:00 Toronto time on Monday, Wednesday, and Friday. To see what changed in this save, compare this Data with the previous patchAttributes entry for the same Item ID. For example, if the previous entry had "0 12 * * 1,2,3,4,5", this save removed Tuesday and Thursday from the schedule.
Example 2 — A policy was assigned to an organization
Row: Item = Policy, Action = assignToOrganization
{
"filter": { "where": { "id": "<policy-id>" } },
"organizationId": "<org-id>",
"deviceGroupId": null
}
How to read it: Policy <policy-id> was assigned to organization <org-id>. deviceGroupId is null, so the policy applies to the whole organization, not just one device group.
Example 3 — A policy was turned off for one location
Row: Item = Policy, Action = disableForLocation
{
"locationId": "<location-id>",
"policyId": "<policy-id>",
"deviceGroupId": null,
"policyAssignmentId": "<assignment-id>"
}
How to read it: Policy <policy-id> was disabled for location <location-id> (the whole location, because deviceGroupId is null). locationId came from the URL and the rest from the body; they are shown merged together.
Example 4 — Policy assignments were removed
Row: Item = Policy, Action = removePolicyAssignments
{
"0": "<assignment-id-1>",
"1": "<assignment-id-2>"
}
How to read it: Two policy assignments were removed. These are assignment IDs, not policy IDs. To find which policy and organization or location they belonged to, look for earlier assignTo… or enable/disableFor… entries that contain the same assignment ID, or check the policy’s current assignments.
Example 5 — A policy was enabled or disabled
Row: Item = Policy, Action = toggleEnabled
{
"name": "Default Response Policy",
"type": "response",
"active": true
}
How to read it: active is the state after the change. true means the response policy “Default Response Policy” was turned on. false would mean it was turned off.
Example 6 — A device was isolated or released from isolation
Row: Item = Agent, Action = toggleIsolation
{
"action": "restore",
"agentIds": ["<device-id>"],
"userId": "<user-id>"
}
How to read it: action: "isolate" means the device was cut off from the network. "restore" means isolation was removed. agentIds lists the affected devices.
Example 7 — Verbose logging or metrics collection was toggled
Row: Item = Agent, Action = toggleVerboseLogging (or toggleMetricsCollection)
{
"verboseLogging": "2026-10-07T19:55:31.302Z"
}
How to read it: Read this one carefully. The value is the end time the device already had when the user clicked, not the new setting. If that time is after the entry’s timestamp, verbose logging was running and this click turned it off. If the value is empty or in the past, this click turned it on (verbose logging for 7 days, metrics collection for 1 hour).
Example 8 — Licenses were assigned to or removed from devices
Row: Item = Agent, Action = assignLicenses (or unassignLicenses)
{
"where": { "and": [ { "or": [ { "locationId": "<location-id>" } ] } ] },
"filter": { "location": { "id": "<location-id>", "name": "Head Office" } },
"agentIds": ["<device-id-1>", "<device-id-2>", "..."]
}
How to read it: The user was viewing location “Head Office” and changed licenses on the devices in agentIds. This entry does not say whether each device succeeded. The License tab has one row per device and license type with the result (added, removed, or failed to add).
Example 9 — An exclusion was added to a Datto AV policy
Row: Item = Policy, Action = addExclusion
{
"policyId": "<policy-id>",
"exclusionPath": "\\?\C:\Users\jdoe\AppData\Local\App\Updater.exe"
}
How to read it: The path \?\C:\Users\jdoe\AppData\Local\App\Updater.exe was added as an exclusion to policy <policy-id>. Remember that JSON doubles every backslash, so \\?\\ in the raw Data means \?\ in the actual path.
Example 10 — Something was deleted
Row: Item = Policy, Action = deleted, Item ID = <policy-id>
{}
How to read it: The Data is empty, so the Item ID is the only identifier. Filter the log on that Item ID to find earlier entries (for example created or patchAttributes) that show the policy’s name and settings.
Actions by item
The tables below list the actions that appear in the Activity log when users work in the console or call the API. Standard actions (created, patchAttributes, deleted, and others that apply to most objects) are listed first; item-specific actions follow.
Standard actions
Most objects support the following standard operations. When a user performs one of these, the Action column shows one of the values below.
| Action shown | Meaning |
|---|---|
created
|
A new object was created (for example a new policy, organization, location, webhook, or report schedule). |
patchAttributes
|
An existing object was edited and saved. This is the most common entry. For example, saving a policy appears as Item = Policy, Action = patchAttributes. |
updated
|
An existing object was saved through a custom save operation (Rules, Suppression Rules, Rule Overrides, Response Overrides, BMS/PSA configuration) or a user record was edited. |
patchOrCreate
|
An object was saved by “create or update” (an update if it existed, otherwise a create). |
replaceById / replaceOrCreate |
An object was fully replaced (mostly API use). |
upsertWithWhere
|
An object matching a filter was updated or created (mostly API use). |
deleted
|
An object was deleted. |
bulk update
|
Several objects matching a filter were updated in one request. |
destroyAll
|
Several objects matching a filter were deleted in one request (Agents/Devices, Organizations, Locations, Controllers, Agent Keys, Scheduled Admin Notifications). |
flagged <flag name> / removed flag |
A flag (for example Bad, Good, Probably Bad) was set on or removed from a file or application. |
scanned
|
A scan was started on a device, location, or organization. |
login
|
A user signed in. Hidden for customer accounts (see What you will not see). |
logout
|
A user signed out. Hidden for customer accounts. |
Policies page (EDR, Datto AV, Defender, and other policies)
| Action shown | Meaning |
|---|---|
created
|
A new policy was created. |
patchAttributes
|
Policy settings were saved. Open the detail to see the full saved configuration. |
deleted
|
A policy was deleted. |
clone
|
A policy was cloned. |
toggleEnabled
|
A policy was enabled or disabled. |
setDefault
|
A policy was set as the default policy. |
assignToOrganization
|
A policy was assigned to an organization (or a device group within it). |
assignToOrganizations
|
A policy was assigned to several organizations at once. |
removeFromOrganizations
|
A policy was removed from several organizations. |
enableForOrganization / disableForOrganization |
A policy assignment was turned on or off for an organization. |
assignToLocation
|
A policy was assigned to a location. |
enableForLocation / disableForLocation |
A policy assignment was turned on or off for a location. |
removePolicyAssignments
|
One or more policy assignments were removed. |
addExclusion
|
A path exclusion was added to a Datto AV policy (for example from an alert). |
parseCsvFile
|
A CSV of exclusions was uploaded for import into a policy. |
Devices / Hosts pages
| Action shown | Meaning |
|---|---|
approve / deny |
A pending agent registration was approved or denied. |
rename
|
A device was renamed. |
uninstall
|
An uninstall was requested for one or more agents. |
deleted / destroyAll |
One or more devices were deleted from the console. |
assignLicenses / unassignLicenses |
EDR and/or AV licenses were assigned to or removed from devices. The matching per-device entries appear on the License tab. |
assignDeviceGroup / unassignDeviceGroup |
Devices were added to or removed from a device group. |
toggleIsolation
|
A device was isolated from the network, or isolation was reverted. |
scanned
|
A scan was started on one or more devices. |
retrieveLogs
|
Agent logs were requested from a device. |
toggleMetricsCollection
|
Agent metrics collection was started or stopped. |
toggleVerboseLogging
|
Agent verbose logging was started or stopped. |
bulkSave
|
Several device records were updated at once. |
Organizations and Locations pages (the Item column shows “Organization” or “Location”)
| Action shown | Meaning |
|---|---|
created / patchAttributes / deleted |
An organization or location was created, edited, or deleted. |
scanned
|
A scan was started for an organization or location. |
deleteLocations
|
One or more locations were deleted. |
moveLocations
|
Locations were moved to a different organization. |
assignPolicies
|
Policies were assigned to one or more locations. |
bulkSave
|
Several locations were updated at once. |
generateSecurityInsights
|
Security insights generation was triggered manually for a location. |
updateDesktopUi
|
Desktop UI (tray application) settings were changed for an organization. |
Device groups
| Action shown | Meaning |
|---|---|
created / patchAttributes |
A device group was created or edited. |
deleted
|
One or more device groups were deleted. |
Alerts page
| Action shown | Meaning |
|---|---|
archive / unarchive |
Alerts were archived or restored from the archive. |
agentResponse / response |
A response action was run from an alert (for example quarantine, delete, or kill process on Datto AV alerts). |
rollback
|
A ransomware rollback was started from an alert. |
Quarantine page
| Action shown | Meaning |
|---|---|
createRestoreFileJobs
|
A restore of one or more quarantined files was requested. |
createDeleteFileJobs
|
Permanent deletion of one or more quarantined files was requested. |
File and application analysis pages
| Action shown | Meaning |
|---|---|
flagged <flag name> / removed flag |
A flag was set on or removed from a file or application. |
retrieve
|
Retrieval of a file from a device was requested. |
analyze
|
A file was submitted for advanced analysis. |
Admin > Rules (detection rules)
| Action shown | Meaning |
|---|---|
Created: <rule name>
|
A new rule was created. The rule name is included in the action value. |
Modified: <rule name>
|
An existing rule was changed. The rule name is included in the action value. |
updated
|
Recorded alongside the Created/Modified entry for the same save. |
deleted
|
A rule was deleted. |
toggleEnabled
|
A rule was enabled or disabled. |
publish
|
Active rules were published to agents. |
loadFiles
|
Rules were imported from a file. |
getRulesExportPayload
|
Rules were exported. |
Rule severity and response overrides
| Action shown | Meaning |
|---|---|
updated
|
A rule override (severity and/or action) or response override was saved. |
reset
|
A rule override was removed (reset to default). |
addOverrides
|
Response overrides were added. |
bulkUpdate
|
Several response overrides were updated at once. |
Suppression rules
| Action shown | Meaning |
|---|---|
Created: <name> / Modified: <name> / Deleted: <name> |
A suppression rule was created, changed, or deleted (the Item column shows “suppressionRule”). |
updated / deleted |
Recorded alongside the named entry for the same save or delete (the Item column shows “SuppressionRule”). |
toggleEnabled
|
A suppression rule was enabled or disabled. |
publish
|
Active suppression rules were published. |
Extensions (Response / Collection extensions)
| Action shown | Meaning |
|---|---|
Created: <name> / Modified: <name> / Deleted: <name> |
An extension was created, changed, or deleted. Note: other extension operations are not logged (see What you will not see). |
Response actions
| Action shown | Meaning |
|---|---|
execute
|
A response extension was run against one or more devices. |
created / patchAttributes / deleted |
A response action definition was created, edited, or deleted. |
Admin > Users, sign-in, and SSO settings
| Action shown | Meaning |
|---|---|
created / patchOrCreate / deleted |
A user account was created, edited (including roles), or removed. |
changePassword
|
A user changed their password (the password itself is never stored). |
enableLoginWithK1 / removeK1Integration |
Kaseya One (K1) sign-in was enabled or removed. |
setK1GroupsEnabled / setK1GroupMapping / removeK1GroupMapping |
K1 group-based access was turned on or off, or a group-to-role mapping was changed. |
isK1GroupsEnabled
|
The K1 group setting was read. This is a read operation that is recorded because of how the endpoint is defined. |
API keys
| Action shown | Meaning |
|---|---|
generate
|
A new Personal Access Token (API key) was created. |
deleted
|
An API key was revoked. |
filterByUserEmail / countFilteredByUserEmail |
The API key list was searched. These are read operations that are recorded because of how the endpoints are defined. |
Admin > Settings (global instance settings)
| Action shown | Meaning |
|---|---|
patchAttributes / created |
A general setting value was saved. |
updateUninstallProtection
|
Uninstall protection was turned on or off, or its token was changed. |
updateRemoveInactiveAgents
|
The number of days before inactive devices are removed was changed. |
updateAutomaticFileAnalysis
|
Automatic file analysis was turned on or off, or its size limit was changed. |
updateRestrictNonUsPersonnel
|
The “restrict non-US personnel” access setting was changed. |
setEnforceK1Sso
|
Enforcement of Kaseya One SSO was changed. |
updateDesktopUiSettings
|
Global desktop UI (tray application) settings were changed. |
setDeviceOfflineEnabledSetting / setDeviceDisabledSetting / setDeviceIsolatedEnabledSetting |
Device offline, disabled, or isolated notification settings were changed. |
setApiTokenExpiredEnabledSetting
|
The API-token-expired notification setting was changed. |
setAvFileSubmissionEnabledSetting
|
The Datto AV file submission setting was changed. |
setDashboardUpdateStatus
|
The dashboard update status was changed. |
Per-organization uninstall protection
| Action shown | Meaning |
|---|---|
updateUninstallProtection
|
Uninstall protection was changed for an organization. |
generateUninstallToken
|
A new uninstall token was generated for an organization. |
Branding
| Action shown | Meaning |
|---|---|
logoUpload / deleteLogo |
The tenant logo was uploaded or removed. |
patchAttributes
|
Tenant information was edited. |
PSA, BMS, VSA, Pulseway, webhooks, and other integrations
| Action shown | Meaning |
|---|---|
updated (PsaConfiguration / BmsConfiguration) |
PSA or BMS integration settings were saved. |
saveSeverityMappings / saveAlertMappings / saveAccountMappings |
PSA/BMS severity, alert, or account mappings were saved. |
unmap / unmapAccount / refreshAccount |
A PSA/BMS account mapping was removed or refreshed. |
webhookDeactivate
|
The PSA webhook was deactivated. |
connect / setConfigSettings (VsaConfiguration / PulsewayConfiguration) |
A VSA or Pulseway integration was connected or its settings were saved. |
created / patchAttributes / deleted (Webhook, Integration) |
A webhook or other integration was added, edited, or removed. |
Scheduled and system notifications
| Action shown | Meaning |
|---|---|
created / patchAttributes / deleted (ScheduledNotification, ScheduledAdminNotification) |
A notification schedule was added, edited, or removed. |
toggleEnabled (ScheduledAdminNotification) |
An admin notification schedule was enabled or disabled. |
archive / unarchive (SystemNotification) |
In-app notifications were archived or restored. |
Reports, search, and scan history
| Action shown | Meaning |
|---|---|
generate (Report) |
A report was generated. |
created / patchAttributes / deleted (ScheduledReport) |
A scheduled report was added, edited, or removed. |
exportReport (SearchResult / ScanHistoryTracking) |
Search results or Datto AV scan history were exported. |
refreshDashboard (DashboardData) |
Dashboard statistics were refreshed. |
Task list
| Action shown | Meaning |
|---|---|
cancel (UserTaskItem) |
One task item or several matching task items were cancelled. |
Datto AV exclusions and file submissions
| Action shown | Meaning |
|---|---|
upsertAvExclusion / upsertAvExclusions |
One or more Datto AV exclusions were added or updated. |
created / patchAttributes / deleted |
An AV exclusion or submission record was created, edited, or removed. |
Miscellaneous
| Action shown | Meaning |
|---|---|
created / patchAttributes / deleted (UserComment) |
A comment was added to, edited on, or removed from an object such as an alert. |
created / patchAttributes / deleted (Flag) |
A flag definition was created, edited, or removed. |
created / deleted (AgentKey) |
An agent registration key was created or deleted. |
approve / deny / rename (Controller) |
A controller registration was approved, denied, or renamed. |
refresh (Timebox) |
Timebox data was refreshed. |
fetchAnswer / updateQuestions / getPromptsByRequiredFields / getTaskResult (EdrAiAssist) |
EDR AI Assist was used on an alert, or its questions were updated. |
The following are not recorded in the General tab:
- Views, searches, list filters, and GET-based downloads or exports. Read-only activity is not logged.
- Failed or denied requests (for example a user without permission trying to edit a policy). Only successful requests create an entry.
- Activity by the agents themselves (heartbeats, registration, scan uploads, job completion, alerts raised by the agent). Agents do not sign in as a user, so their calls are not logged.
- Entries older than 1 year. Older entries are purged automatically.
How to...
To identify who changed what in an Activity log entry, complete the following steps:
- Start with Item + Action to identify the operation. Use the tables in Actions by item.
- Use the Item ID to identify which object was changed. For a policy, you can open
/policies/policy-list/<Item ID>/editin the console to see the policy as it is now. - Click the Action value to open the detail dialog and read the Data. Match each ID to its object using the field names in Common fields in the Data. Names are often included next to the IDs (for example
name,policyName,location.name), which saves a lookup. - For edits (
patchAttributes,updated,created), the Data is a full copy of what was saved, not a list of what changed. To find the change, open the previous entry for the same Item ID and compare the two Data blocks using a text or JSON comparison tool (for example VS Code “Compare Selected”). IgnorehashandupdatedOn: they change on every save. - For deletes, the Data is usually empty (
{}). Filter the log on the Item ID to find earlier entries (for examplecreatedorpatchAttributes) that show the object’s name and settings.
BEFORE YOU BEGIN Locate two patchAttributes (or updated / created) entries for the same Item ID in the Activity log.
To identify exactly which field changed between two saves of the same object, complete the following steps:
- Click the Action value on the more recent entry to open its detail dialog. Copy the contents of the Data section.
- Click the Action value on the earlier entry. Copy the contents of its Data section.
- Paste both Data blocks into a JSON or text comparison tool (for example VS Code “Compare Selected”, or any online JSON diff tool).
- Ignore
hashandupdatedOnin the diff output: these fields change on every save and do not reflect a user-visible change. - Review the remaining differences to identify what the user changed.
| Revision | Date |
|---|---|
|
Initial release. |
11/5/26 |