Remote access to a club PC
Remote access to a club PC
Section titled “Remote access to a club PC”The Remote Access button in the Control Center opens a remote desktop session for the selected PC directly in your browser. Every click is recorded in the audit log: who connected, when, and from which IP address.
How to open remote access
Section titled “How to open remote access”Where to find it: CRM → Control Center → device card → Remote Access button
Requirement: the MeshCentral agent must be installed on the PC. If it is missing, you will see an Install mesh now button instead — click it, wait for installation to finish, then try again.
Steps:
- Open the Control Center and find the PC you need.
- Click Remote Access. The browser opens a new tab showing Establishing remote access….
- Once the connection is established, the remote desktop appears.
- Close the tab when you are done — the remote session ends with it.
The remote session link is single-use and short-lived: a new one is generated each time you click the button. You cannot reuse a previously opened link — click the button again to start a new session.
Who can open remote access
Section titled “Who can open remote access”Remote access is controlled by the DEVICE_MESH_ACCESS permission. Without it the button is hidden in the Control Center.
You can add this permission to a role under Settings → Roles. See How to configure a role for details.
What the audit log records
Section titled “What the audit log records”Every remote access operation is automatically written to the audit log. An entry is created for every outcome — successful connection and errors alike.
Each entry contains:
| Field | Contents |
|---|---|
| Operation | CreateDeviceMeshLink |
| Club | ID of the club whose device was accessed |
| User | ID of the CRM staff member |
| IP address | Address from which the request originated |
| User-Agent | Browser and OS |
| Input parameters | Device identifier (deviceId) |
| Result | API response (sensitive fields are automatically masked) |
Why this is a mutation, not a query
Section titled “Why this is a mutation, not a query”GraphQL queries are fundamentally not captured by the audit log — only mutations are. Remote desktop access was migrated from a query to a mutation so that every session opening is attributed to a specific staff member. If a CRM client is outdated and still calls the old query, it will receive an error prompting it to update.
How to read audit log entries
Section titled “How to read audit log entries”Remote access entries appear in the organization audit log under the operation name CreateDeviceMeshLink.
For each entry you can determine:
- Who opened the session — the user field contains the CRM staff member’s ID.
- Which device — the input parameters record the
deviceId. - From where — the IP address and browser.
- Whether it succeeded — if the API returned an error (for example, agent not found), it is stored in the result field.
To find out who accessed a specific machine and when, filter the audit log by the operation CreateDeviceMeshLink and the device in question.
What to do about a DeviceRemoteAccessNotFound error
Section titled “What to do about a DeviceRemoteAccessNotFound error”This error means the PC was not found in MeshCentral: the agent is either not installed or has not finished registering after installation.
- Click Install mesh now on the device card.
- Wait for the status to change to Mesh install queued, then wait until the button switches back to Remote Access.
- If installation does not complete within a few minutes, make sure the PC is powered on and has internet access.
For more on installing IZI on a PC, see Installing IZI on a club PC.
Related articles
Section titled “Related articles”- Devices overview — list and management of club devices
- Add a device — how to pair a new PC with the club
- Configure a role — how to grant a staff member the DEVICE_MESH_ACCESS permission
Frequently asked questions
Who can open remote access to a device?
Any staff member whose role includes the DEVICE_MESH_ACCESS permission. Without it, the Remote Access button in the Control Center is hidden.
Is remote access recorded in the audit log?
Yes. Every call to the createDeviceMeshLink mutation is recorded in the audit log: the operation name, club ID, user ID, IP address, and User-Agent are all saved. The entry is created regardless of whether the session opened successfully.
Why is remote access a mutation rather than a query?
GraphQL queries are not captured by the audit log — only mutations are. Remote desktop access was moved from a query to a mutation specifically so that every session opening is attributed to a specific staff member. The audit plugin then guarantees it is always recorded.
What happens if the PC is not found in MeshCentral?
The API returns a DeviceRemoteAccessNotFound error and the Remote Access button disappears. This means the MeshCentral agent is either not installed on that PC or has not registered yet. Install the agent using the Install mesh now button in the Control Center.
Is any setup required beforehand?
Each PC must have the MeshCentral agent installed. You can start the installation directly from the Control Center — use the Install mesh now button. See the article on installing IZI on a club PC for details.
IZI LLC (ООО «ИЗИ»), TIN 7842227686, OGRN 1257800012249, office 1, premises 3-N, lit. A, 15-17 Perekupnoy lane, Saint Petersburg, 191024, Russia, admin@izi.is · Cookie settings