# Remote Access
Remote accesses can be stored for each project, which can be checked into the memory on a project-specific basis and used by all computers and users. For some project types, you then have the choice of whether to use the internal IP addresses or the external path for integrated functions such as QC starters.
# Overview
[](https://wiki.smarthometools.de/uploads/images/gallery/2025-01/eV5image.png)
- "**Project settings (#1)"** This button takes you to the project-specific settings, e.g. to store the connection data and test the connection.
- "**Access type (#2)**" Choose between "Local" and "Remote" so that the online functions (debug page, QuadClient) use the correct connection. The S1/RA functions are only available with "Remote".
- "**Connect/Disconnect (#2)**" If the access data is stored, the connection is established and disconnected here.
[](https://wiki.smarthometools.de/uploads/images/gallery/2025-01/uOmimage.png)
# Connection via Gira S1 or ISE Remote Access
It is possible to establish direct connections to the system via a Gira S1 or ISE Remote Access. The KNX interfaces for ETS, for example, are automatically integrated and any TCP ports are forwarded to the customer's network participants.
If the project type is "Expert", the Expert project is automatically scanned and common ports are set when remote access is activated. This applies to the classic standard ports of the visualization, logic debugger and DCS-IP gateway. Once the ports have been created automatically, they must be updated manually if changes are made.
# OvenVPN
An OpenVPN configuration file can be added via the project settings. After selecting the project, you can establish a connection by setting the project to “Local” and pressing the connection button.
Requirement:
OpenVPN GUI at least version 10.50.0.0.
A parallel installation next to e.g. “OpenVPN Connect” is possible.
See - [https://openvpn.net/community-downloads/](https://openvpn.net/community-downloads/)