Access credential imports and bulk actions

Use imports for controlled onboarding and bulk actions for an already-filtered credential set. Both can affect many people and controllers, and neither is transactional across the entire set.

Import credentials

Select Import Credentials on the Physical Access Control card. The action is hidden from Access Control Viewer users.

Before importing, the site must have at least one active controller and at least one access group. Download and populate the provided CSV template; do not reorder or remove its columns.

The importer reads these column positions:

Position	Value
1	Host import identifier, optional.
2	Vendor import identifier, optional and used only when Host is blank.
3	Card-format external ID, or false for no format.
4	Credential number.
5	Credential type label.
6	Start date in M/d/yyyy format.
7	Optional expiration date in M/d/yyyy format.
8	Access-group name, matched exactly.
9	Active value.
10	Alternative association text.
11	Push value.

The first row is always skipped as a header. The parser splits on commas and does not interpret quoted CSV fields, so do not place commas inside any value.

Warning

The dialog says imported credentials do not automatically push and require a manual push. The importer also reads the final Push column and can attempt delivery when it is true. Treat manual verification and a controlled push from Credential Administration as required regardless of that column.

Other important behavior:

• Credential type labels and access-group names must match configured values.
• If both host and vendor IDs are present, the host path takes precedence.
• An invalid optional expiration date is ignored and can produce a credential with no expiration.
• Boolean values that are not recognized as true become false.
• An existing active format-and-number combination is skipped.
• A matching deleted credential can be restored.
• Only one access group is created from each import row.

The import runs in the background, closes the dialog, and emails an attached processing log to the signed-in user's email address. Review every error row in that log, then filter the credential grid to reconcile imported counts and manually verify controller delivery.

Bulk actions

Filter the credential grid, select the intended rows, open Bulk Actions, and confirm the Selected count. The following actions require a selected controller:

• Delete queues removal and logically deletes only credentials whose queue request succeeds.
• Activate clears deleted state, marks active, and queues controller updates.
• De-Activate marks inactive and queues an update; it does not change the expiration date.
• Set Expiration Date updates the selected expiration and queues supported controller changes.
• Push Credential(s) queues only active selected credentials and emails completion notice.
• Modify Access Groups replaces group assignments and can queue removals from controllers that lose coverage.

Modify Credential Type does not require a controller selection. Set Max Use Count can update portal data without requiring the controller selector, although supported integration delivery can still be relevant.

All bulk operations process records individually in the background. A failure does not automatically roll back records that completed earlier. After processing:

1. Refresh the grid and compare expected versus actual state.
2. Review credential history for a representative success and failure.
3. Filter the configuration queue by the chosen controller.
4. Retry only the failed subset.