---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Device action access and approval control

# Device action access and approval control {#ariaid-title1}

Release version: Australia  
Updated May 20, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Approval-based access helps control how sensitive device actions are triggered and supports authorized use of actions that impact device performance or system behavior.  
Device actions that terminate processes, uninstall applications, or use significant system resources can impact device performance or system behavior. To limit unintended use, such resolutions can be configured as catalog items to add an approval step. Routing these actions through an approval step helps prevent users from triggering sensitive actions without authorization and creates an approval record alongside execution details. For information on configuring a remedial action as a catalog item, see [Create a remedial action](https://servicenow-prod.fluidtopics.net/90N3Krt56b2OJ2tzKaH8Qg "Create your custom remedial actions from Check Definitions to resolve end-point related issues using Playbook.").  
Note:  
Device actions are limited to once a calendar day for each device.

Device actions run using the Agent Client Collector (ACC) service account configured on the device --- `_servicenow` on macOS and the configured service account on Windows. End users can't perform actions beyond the permissions granted to this account. The service account is configured at agent installation and can't be modified through device action settings.