Published at: 2025-10-31

Terminal User Account Setup/Registration/Login Guide (User Binding)


What Are Terminal Users and Guest Users

1.1 Definition of Terminal Users

  • Refers specifically to external terminal users (Interconnection users). When businesses open their services to terminal users (Interconnection users), external users need to register identity data.
  • Existing or newly registered terminal user (Interconnection user) information is stored under Interconnection Enterprises and Interconnection Users, and can be linked to [Account] and [Contact] objects.
  • After assigning Roles to external users, they can access business data such as checking devices or submitting Work Orders.

1.2 Definition of Guest Users

  • A Guest is a special external account that must also be associated with an [Account] and [Contact] record.
  • The “Guest” also functions as a Role, defining all functional permissions for this special account.
  • Guests are not differentiated by individual users—all Guests share a single external account. All business data generated under the Guest identity is consolidated under this single “Guest” account. Use this feature with caution:
    • Guests can only access public data.
    • Guest permissions cannot be modified.

1.3 Prerequisites

  • Terminal user (Interconnection user) accounts require purchasing Terminal User licenses and enabling the Interconnection feature. For details, refer to: Interconnection Platform Setup.
  • Initialization path: Service Connector > System Settings > Overview Settings, then select “Terminal User Service Connector.”
  • For more details, see: Terminal User Purchase and Activation Guide.

Terminal Account Activation Methods

2.1 Manual Activation by Service Connector Admin

Prerequisites:
1. Ensure the “Manual Activation” button is enabled.
2. Ensure the current user has “Create” permissions for [Interconnection Enterprise] and [Interconnection User] objects.
3. Ensure the “Terminal User” menu is visible in the Web view of Service Connector.

Steps:
1. Navigate to Service Connector > Terminal Users.
2. Click “Add Terminal User.”
3. Select the Account(s) to activate (must have at least one associated Contact).
4. Assign relevant Roles to the terminal user and submit.
5. After manual activation, the terminal user (Interconnection user) can log in via SMS verification.

image
image
image

2.2 Special Account: Guest

  • A Guest is a special external account linked to an [Account] and [Contact].
  • The “Guest” Role defines all functional permissions for this account.
  • All Guests share one account. Data generated under this identity is consolidated under a single “Guest” record.
    • Guests can only access public data.
    • Permissions cannot be modified.

Steps:
1. Go to Interconnection App > Terminal User Service Connector > Account Activation, enable “Guest,” and configure parameters.
2. Select an Account record—all Guest-generated data will be linked to it. The system auto-initializes a Guest record; if missing, manually add one.

image

2.3 Self-Registration for Terminal Users

  • Enable self-registration in Service Connector > System Settings > Full Configuration > Terminal User Service Connector > Account Activation.

Steps:
1. Click “Settings.”
2. Select “Interconnection Account Self-Registration,” then enable or create a new self-registration method.
3. Adjust configurations as needed.

image
image
image

Self-Registration Configuration:
- Basic Info:
- Name: Customizable.
- Applicable App: Typically limited to current Interconnection users.

image

Registration Page Parameters:
- Account-Related Settings:
- Record Type: Self-registered Accounts use this type. Enable “Show Only Required Fields” to simplify registration.
- Field Layout: Controls visible fields during registration.
- Owner Assignment: Supports single or round-robin assignment.
- Duplicate Check Logic: Fuzzy or exact matching for Account names.
- New Account Rules: Three modes:
1. User-defined Account names.
2. Select from existing Accounts only.
3. Fetch names from official business registries.

  • Contact-Related Settings:
    • Record Type: Self-registered Contacts use this type.
    • Field Layout: Controls visible fields.
    • Login Mobile: Automatically maps to the Contact’s mobile1 field.

image
image

Self-Registration Methods:
Choose based on business needs. For guidance, see: Recommended Self-Registration Methods.

image

Role Assignment:
Self-registered Interconnection users are assigned Roles. For permissions, refer to: Business Objects and Role Permissions.

image


Scenario 1: WeChat Official Account/Miniprogram Access (No Mandatory Account/Contact Creation)

  1. Self-Registration Method: Allow OpenID-based auto-account generation.
  2. Set [Work Order] or [Service Request] fields (account_id, contact_id) as optional.
    - Different from Guests: Data is isolated per user.

image

Example:
- The system auto-generates [Interconnection Enterprise] and [Interconnection User] upon WeChat OpenID login. Assigned Roles determine access (e.g., submitting Work Orders).

image
image

Scenario 2: WeChat Access with Post-Registration Data Submission

  1. Self-Registration Method: Allow OpenID-based auto-account generation.
  2. Set [Work Order] or [Service Request] fields (account_id, contact_id) as mandatory.

Example:
1. Users access the portal via WeChat; the system creates [Interconnection Enterprise/User].
2. To submit data, users must complete registration, which auto-creates [Account] and [Contact] records.

image
image

Post-Registration:
- Terminal users are linked to Accounts/Contacts and bound to WeChat.

image

Scenario 3: WeChat Access with Mandatory Pre-Registration

  1. Self-Registration Method: Require Account/Contact registration.
  2. Disable “Guest.”

Example:
- Users must register before accessing the portal. The system matches or creates [Account]/[Contact]** records.

image

Post-Registration:
- Terminal users are linked to Accounts/Contacts and bound to WeChat.

image
image

  1. Self-Registration Method: Require Account/Contact registration.
  2. Enable “Guest” and configure a default Account for Guest data.

Example:
- Guests can access public data. Clicking “Login” triggers registration.

image
image

Scenario 5: Manual Activation Only

  • Disable self-registration and “Guest.”
  • Only manually activated users can access the portal.

Example:
Unregistered users are blocked at login.

image
image

For manual activation, refer to: Manual Activation Guide.

Submit Feedback