SecureAccess Web Client – FAQ - Documentation Center

Access the SecureAccess platform for the first time via www.gdms.cloud and locate the “Register” entry on the login page. Click it to enter the registration process, follow the on-screen instructions to fill in the relevant information, and complete the creation of the super administrator account.

If you encounter this situation, please check the following steps one by one:

Verify basic information: Please carefully check whether the entered MAC address and the device’s initial password match exactly.
Confirm binding status: Verify whether the device’s MAC address has already been registered or bound by another account.
Reset and try again: If both items above are confirmed correct, it is recommended to restore the device to factory settings and try again.

If you do not receive an email after registration, first check the “Spam” or “Junk mail” folder of your email. Also, confirm that the email address entered during registration is accurate. If you still have not received it, try going back to the registration page to resubmit your application.

For account security reasons, activation links have strict time limits. Please carefully read the validity period stated in the email body (e.g., “Valid for 3 days”). If the link is clicked after this time frame, it will be invalid automatically. You will need to return to the platform to re-register and obtain a new link.

You can log in normally after successful activation. Please use the account and password you filled in during registration to log in.

After the administrator account is created, it will be in a “pending activation” state. The system will automatically send an activation email to the administrator’s email address. The account can only be used normally after the activation link in the email is clicked.

Administrators with different roles have significantly different creation permissions and jurisdictions:

Super Administrators and Platform Administrators: Have identical permissions. Both support creating administrator accounts and, by default, possess full management permissions for all organizations and devices within the system.
Organization Administrators: Restricted permissions. Cannot create administrator accounts or new organizations. Must be associated with an organization before gaining management permission for that organization and its devices.

The list will display administrators for other subsystems by default. You can directly reconfigure administrator privileges (such as platform administrator or organization administrator) for these accounts.

When an administrator’s associated organization is in an “Inactive” status, the system cannot add users under that organization. You need to wait for the organization to be activated. Once activation is successful, the administrator’s information will be automatically synchronized and created in the organization’s user management system; there is no need to re-assign it.

Yes, assignment is still possible. Even if the selected organization has reached its cloud user limit, the system still allows assigning an administrator to that organization and creating user information normally, without consuming additional organization quota.

When the number of “APP Users” for an organization reaches its limit, newly created administrators will not be able to use the APP to open doors by default, but they can still log in to the APP and perform other management operations normally. Once there are remaining APP users in the organization, you can manually enable APP open door permissions for them in the user management module.

Once an administrator account is successfully activated, it supports dual-terminal login. Users can log in to the SecureAccess Web portal or the mobile APP using their account and password.

No, not supported. Regular users cannot log into the Web management backend; their accounts are solely used for business scenarios such as access control.

When creating or editing a regular user account, you need to manually enable “APP User Permissions.” After the account is activated, the user can log into the APP, which supports Bluetooth and NFC door unlock by default. For functions such as remote door unlock and temporary password creation, further adjustments in permission configuration are required.

You need to enable “APP User Permissions” and the “Monitor” function. Once enabled, users can call the access control, receive incoming calls, and preview live video feeds from the access control in their mobile APP.

After confirming the user status is “Enabled,” check whether the user is associated with the access group of this access control device and whether the current time is within the allowed access period.

The platform supports importing based on organization type. Please make sure to download the import template that exactly matches your current organization type from the import interface, fill it out, and then upload it; otherwise, data validation will fail. If the template is correct, please check whether the filled content conforms to the format constraints.

Currently, the web application does not support the card-swiping registration function. Please download the mobile APP from the application center or https://fw.gdms.cloud/gds/download/. Administrators can quickly register new users via card swiping within the APP.

You can create a new access group in ‘Access Group Management,’ specify the access control devices and time periods during which access is permitted, and then add the user to this access group.

You can go to “Parameter Settings – Door Opening Settings” in the “Device Management” module, enable IC card door opening, check the “Normal Encryption” option, and enable compatibility with unencrypted IC cards.

You can add a new visitor in “Visitor Management,” set an access password, and define a valid access period. To further enhance security, you can also limit the number of times the visitor can unlock the door. Once the preset limit or valid time period is exceeded, the visitor will no longer be able to unlock the door.

A visitor’s specific permissions (including accessible access control devices, valid time periods, and unlocking methods) depend on the authorization scope of the creator. Visitors can only be assigned corresponding access control devices, time periods, and unlock methods within the scope of the creator’s own permissions.

This usually occurs when the visitor’s or creator’s permissions have changed, or when the creator’s account has been deleted (which would invalidate visitor’s permissions). It is recommended to contact the administrator to verify the relevant permission settings and account status.

Visitors can unlock doors using three methods:

Access Password: Administrators can set up a unique temporary access password for visitors, which they can enter on the access control device to unlock the door.
Dynamic QR Code: Administrators can share a dynamic QR code with visitors via the system. Verification information for obtaining the QR code can also be configured to enhance security. Visitors simply scan the code with their mobile phone to gain access.
Static QR Code: In certain scenarios, administrators may also share a static QR code for visitors to use for access.

You can go to the “Visitor Management” module, locate the corresponding “Sharing Method” setting, and click “Reset QR Code.” After completing this operation, the old QR code will immediately become invalid, and the visitor will no longer be able to unlock the door.

You can add a new visitor in “Visitor Management,” set an access password, and define a valid access period. To further enhance security, you can also limit the number of times the visitor can unlock the door. Once the preset limit or valid time period is exceeded, the visitor will no longer be able to unlock the door.

A visitor’s specific permissions (including accessible access control devices, valid time periods, and unlocking methods) depend on the authorization scope of the creator. Visitors can only be assigned corresponding access control devices, time periods, and unlock methods within the scope of the creator’s own permissions.

This usually occurs when the visitor’s or creator’s permissions have changed, or when the creator’s account has been deleted (which would invalidate visitor’s permissions). It is recommended to contact the administrator to verify the relevant permission settings and account status.

Visitors can unlock doors using three methods:

Access Password: Administrators can set up a unique temporary access password for visitors, which they can enter on the access control device to unlock the door.
Dynamic QR Code: Administrators can share a dynamic QR code with visitors via the system. Verification information for obtaining the QR code can also be configured to enhance security. Visitors simply scan the code with their mobile phone to gain access.
Static QR Code: In certain scenarios, administrators may also share a static QR code for visitors to use for access.

You can go to the “Visitor Management” module, locate the corresponding “Sharing Method” setting, and click “Reset QR Code.” After completing this operation, the old QR code will immediately become invalid, and the visitor will no longer be able to unlock the door.

In the “Device Management” module, you can select “Add via MAC/SN,” enter the device’s MAC address or serial number, and complete the addition.

In the “Device Management” module, go to “Parameter Settings – Alarm Settings,” check to enable alarm notifications, and set the alarm call numbers. Once configured, the system will automatically call the specified numbers in sequence when alarm triggers.

In the “Device Management” module, go to “Parameter Settings – Door Unlock Settings” and configure the door unlock method as needed, such as password, card, or APP.

In the “Device Management” module, go to “Parameter Settings – Access Control Settings” and configure the type that snapshot triggered, snapshot number, and snapshot storage method as needed.

In the “Device Management” module, go to “Parameter Settings – Alarm Settings” and set the detection range to “Full Area” or “Custom.”

When there are devices pending import on the GDMS UC platform, the system will display a prompt in the device list or on the addition page. Simply click the “Import” button in the prompt, specify the devices to import, and execute the operation. Upon successful import, the devices will be automatically added to the access group of your currently selected organization.

When operated device is offline, the system marks it as “Deleting.” The system will wait for the device to come online to successfully push the data cleanup command to the device and complete the final deletion.

Yes. While in the “Deleting” status, you can choose to force delete. Once selected, the device will be immediately removed from the list, but the system will no longer automatically clean up user data and other information on the device. You will need to restore the device to factory settings manually to complete the data cleanup.

Yes. After a device is deleted, its historical access logs and alarm records will be retained, and you can still view them normally.

You need to first create an access schedule or set a holiday in the “Schedule Management” module. Then, when configuring the access group, associate it with the created schedule or holidays. After completing the setup, users in that access group will only have device access permissions during the specified time period.