> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://support.atomicwork.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://support.atomicwork.com/_mcp/server.

# Asset actions

Asset actions allow you to perform remote actions without requiring physical access to your assets. They are particularly useful in scenarios such as securing a lost or stolen device or when a user reports an incident that requires a restart.

For example, imagine an employee loses their company-issued laptop while traveling. With asset actions in incidents, you can quickly lock the device to prevent unauthorized access, safeguarding sensitive company data. Or you may need to force a restart for network configuration changes to be fully applied.
​
Asset actions are supported for assets synced from connected device management sources, such as Microsoft Intune and JumpCloud. Actions from every connected source sit in one **Actions** menu on the asset, with source-specific actions grouped by source.

Asset actions can be performed when you open an asset from **Directory > Assets** or when you're viewing it after linking it to an incident.

## Remote lock

The **Remote lock** action allows you to secure an asset remotely by locking it down. This is particularly useful if a device has been lost or stolen, as it prevents unauthorized access and protects sensitive information stored on the device. [Read more about how remote lock works in Microsoft Intune](https://learn.microsoft.com/en-us/mem/intune/remote-actions/device-remote-lock).

## Restart

The **Restart** action allows you to reboot a device remotely. This is useful when you troubleshoot issues, applying updates, or refreshing the system without needing physical access to the device.

## JumpCloud actions

For assets synced from JumpCloud, you can run these remote actions from the asset:

* **Lock**

* **Restart**

* **Shutdown**

* **Erase**

* **Enable Lost Mode**