Comment on page
In this section you will find Frequently Asked Questions and answers related to the technical aspects of GoodAccess.
Team Name is a unique identifier for a group of users (employees) who share access to the same resources and have common settings, policies, and permissions. A Team Name is chosen by the Team Owner when setting up a new Team.
You may find the Team Name in the email invitation to the Team or you can ask your Team Admin.
Team Owner or Admin can download the OpenVPN configuration file and credentials / CA Certificate / Setup Files in Control Panel > Members > Edit button of the Member. They also have the option to send the OpenVPN configuration file and credentials via email directly to the Member.
GoodAccess is designed to be a hassle-free solution for secure remote access, and it does not require any hardware investments or maintenance, making it a cost-effective option for businesses of all sizes.
Connect your server to GoodAccess as client and enable Port Forwarding on the Gateway to forward traffic to the server. This makes your server accessible via the GoodAccess static IP address and the port.
You may connect to RDP using either a GoodAccess private or public IP address of the Gateway. We recommend using a private IP for higher security.
You may also add RDP into your Systems to ease access for your Members with a shortcut in GoodAccess Client Application.
GoodAccess private IP address:
- Each Team Member is assigned with a unique private IP address while connected to GoodAccess. All Members share same virtual LAN when connected to the same Gateway.
- Connected Members can use the private IP addresses to access another connected Member's device using RDP or other local tools.
GoodAccess public IP address:
You may also connect to GoodAccess Gateway on any device supporting an OpenVPN Client function with the use of manual configuration.
Please note you may only change the location of your Gateway five times per month.
We do keep some logs for security and troubleshooting purposes, but the logs are only kept for a limited period.
The logs that we keep include connection logs, which record when a member connects or disconnects from the VPN service, and session logs, which record the user's IP address, device type, and the amount of data transferred during the session. These logs are used for troubleshooting issues with the service, ensuring the service's performance, and detecting and preventing unauthorized access.
You can benefit from this feature as it ensures compliance with GDPR.
Yes, we offer a high-availability solution for our customers in the form of a backup Gateway.
A single Gateway should be sufficient for most users. However, if you require 100% uptime (an enterprise high availability solution), we recommend using another geographically separated Gateway as a backup in the event of network maintenance or unpredictable network outages.
Choosing a Gateway closer to your Team is also useful to ensure better network latency.
SCIM, or System for Cross-domain Identity Management, is an open standard that enables the automation of user provisioning.
Simply put, if you use a third-party identity provider with SCIM enabled, any action affecting users (add, edit, delete) is automatically synchronized with GoodAccess Members. It allows you to manage all user provisioning on the third-party identity provider side.
Persistent connection allows you to connect a Windows device to the GoodAccess Gateway without dependency on the current Windows User. It means that the device will stay connected even though you are logged out from your Windows account. This is essential in cases like connecting an RDP Server/System as a Member to the GoodAccess Gateway. This feature is available on Windows only.