Skip to main content

Knowledge Base

Back to support overview

Session Recording for Agentless Access

Last Modified: Sep 30, 2026

Session Recording for Agentless Access enables organizations to maintain a clear record of incoming remote sessions across all access endpoints. Administrators can centrally manage recording behaviors, allowing the review of remote activity and maintenance of audit trails, which helps to further the support of organizational compliance needs, all through TeamViewer Policies. This article explains how to enable recording, assign the recording policy, access stored recordings, and change the recording location.

This article applies to all TeamViewer Tensor license holders who purchased the Agentless Access add-on.

Prerequisites

Please ensure that your organization has completed the following:

If you want endpoints to inherit the recording policy from a device group:

How session recording works

Session Recording for Agentless Access utilizes the Recording incoming remote session policy setting to control the recording of these sessions. This feature automatically records incoming sessions to selected access endpoints, and stores the recordings in the access gateway. When a user initiates an incoming remote session, TeamViewer Tensor will automatically start the recording. TeamViewer completes the recording when the user ends the session.

By default, the gateway stores recordings in the following folder:

/var/lib/teamviewer-iot-agent/session-recordings

Note: The gateway creates a separate subfolder for each endpoint. The name of each subfolder matches the endpoint’s TeamViewer ID.

How to configure Session Recording for Agentless Access

In order to ensure proper implementation and function of Session Recording for Agentless Access, the feature must be activated via policy and applied to the access endpoints or the device group where they reside:

  1.  Create a new policy or select a current policy to edit.
  2. Add the Recording incoming remote session setting to the policy
  3. Ensure the switch for Enable session recording is set to ON.
  4. Set the switch for Enable confirmation by supporter to the desired setting.
    1. If enabled, the supporter must approve recording before the session begins. 

Note: If the supporter rejects the recording, TeamViewer terminates the session.

  1. If a custom recording location is required, enter the path in the Session recording directory section. If nothing is entered, the default location will be used.
  2. Toggle the switch for Enforce to ON to ensure that the setting cannot be altered locally on any access endpoints.

Troubleshooting

The following section covers common issues encountered with Session Recording for Agentless Access.

Session recordings do not start

  • Confirm that the policy assigned to the access endpoint includes Record incoming remote control sessions and that Enable session recording is turned on.
  • If Enable confirmation by supporter was enabled, the supporter must approve the recording when the session starts, otherwise the session is terminated. Ensure that the supporter did make a successful connection.
  • Confirm that you assigned the policy directly to the endpoint or configured the endpoint to inherit the policy from its device group.

Session recordings do not appear in the expected folder

By default, TeamViewer stores Agentless Access session recordings in the following directory:

/var/lib/teamviewer-iot-agent/session-recordings
  • If you configured a custom location under Session recording directory, confirm that you entered an absolute path. TeamViewer does not support relative paths for the recording directory.
  • Confirm that the parent directory in the configured path exists. TeamViewer cannot create the recording directory when a parent directory is missing.
  • Confirm that the path under Session recording directory does not contain an invalid or unavailable location. An invalid path or a missing parent directory prevents TeamViewer from creating the recording folder and can place the affected access endpoints in an error state.

Correct the configured path before starting or creating the affected endpoints again.