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 patchAttributes or assignToOrganization.
  • 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).

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.

How to...

 

Revision Date

Initial release.

11/5/26