Hubman User Management

Prerequisites

• Privileges: Use an Operator account with rights to modify cardholders and download updates to controllers.
• Site and controller connectivity: Confirm the site is set up and connected (serial, LAN, modem, or PDA), and that controllers are online so changes can be downloaded after edits.
• Credential details: Have the card/fob number and, if required, the user’s PIN ready.

Add a new user (cardholder)

1. Open the Cards/Cardholders module

   • Action: Launch Hub Manager Professional and navigate to the Cards or Cardholders section within the database/Users area.

2. Create a new cardholder record

   • Action: Click Add/New. Enter the user’s name and optional contact details.

3. Assign credentials

   • Action: Enter the card/fob number in the Card Number field. If your system uses PINs, set the PIN/Access Code for keypad-enabled doors.

4. Define access

   • Action: Assign the appropriate access profile: time zones/schedules, door groups, or site-specific permissions according to your deployment’s configuration.

5. Save the record

   • Action: Click Save to commit the cardholder to the database.

6. Download to controllers

   • Action: Perform an Update/Download to send the new user and credentials to the secured series controllers. Verify the site connection type matches your setup (direct, LAN, modem, PDA) and that the update completes successfully.

7. Test access

   • Action: Present the card at a reader and confirm the door unlocks per the assigned schedule and door group.

This workflow aligns with Hub Manager’s cardholder-centric design, where changes are applied in software and then downloaded to controllers for enforcement.

Remove or disable a user

1. Locate the cardholder

   • Action: Open the Cards/Cardholders module, search by name or card number, and select the user.

2. Disable access (preferred)

   • Action: Set the cardholder or credential status to Inactive/Disabled, or clear the credential assignment. This preserves audit history while immediately blocking door access.

3. Delete the user (if policy allows)

   • Action: Use Delete on the cardholder record to remove it from the database. Confirm any retention or audit requirements before deletion.

4. Download changes to controllers

   • Action: Run Update/Download so the controllers receive the revocation and the user can no longer access doors.

5. Verify revocation

   • Action: Test at a reader to ensure the credential no longer grants access.

Hub Manager requires pushing changes to controllers after edits so the secured series hardware enforces the latest permissions and revocations.

Best practices

• Least privilege: Assign only the doors and schedules the role requires; avoid broad “always access” unless justified.
• Naming and documentation: Use consistent cardholder naming and record changes with ticket references for audits.
• Sync discipline: Always perform an Update/Download after adding, disabling, or deleting users so controllers reflect the current state.

Troubleshooting

• New card not working:
  • Check: Card number format, PIN requirements, assigned schedules/door groups, and that the update to controllers completed.
• Changes not reflected at doors:
  • Check: Site/controller connectivity and re-run Update/Download; confirm you edited the correct site.
• Controller offline:
  • Check: Connection type settings (serial/LAN/modem/PDA) and restore communication before retrying the update.

References

• IEI Hub Manager Professional v8 user manual — software overview, operators, sites, and system setup concepts
• Hub Manager Professional quick start — controller connections and update/download workflow to secured series controllers