3.2.1. Two binding methods are supported:

1. Account Password Binding

   • Recommended for remote work scenarios

2. Enterprise Deployment Code Binding

   • Recommended for scenarios requiring stricter access control, such as high-security environments or unattended devices

   

3.2.1.1. Enterprise Deployment Code Binding

How to Get Deployment Code?  

1. Bound devices will be automatically associated with the corresponding device group

   

2. Device access permissions are managed by the super administrator (Section 2.2.1.3)

   

3. Device security settings are configured by the super administrator in the console (Section 2.3.1.2)

   

(II) Account Password Binding

1. If a user registers via the User Invite Link and logs in to the Client app, it will be bound automatically to the Default Device Group

   

   
   

2. The bound account establishes one-to-one access permission with the Admin in the Local app who has the relevant permissions.

   

   
   

3. Security settings can be manually configured on the client