Cardholders and cards

A cardholder is a person who passes your doors. A card is a credential a reader reads: a Wiegand 26-bit card or an iButton key. A cardholder's cards open the doors of their access groups.

Everyone can see cardholders and cards. Adding, changing and deleting them needs Operator or Tenant admin (Roles and permissions).

Cardholders

Cardholders lists the people of the tenant with their Name, Department, Access groups, number of Cards, Status and validity (Valid: Always, from …, until …). Search by name, e-mail, department or reference, and filter by status (All statuses, Active, Suspended).

Add or edit a cardholder

Choose Add cardholder, or Edit on a cardholder's page:

Field	Meaning
First name	Required, up to 100 characters.
Last name, E-mail, Phone, Department	Optional.
Employee number / reference	Your own reference, e.g. from HR; searchable.
Notes	Up to 2,000 characters.
Status	Active, or Suspended: a suspended cardholder's cards open nothing.
Valid from, Valid until	Optional validity period. Outside this period the cardholder's cards open nothing. Valid until must be after Valid from.
Access groups	The groups the cardholder belongs to.

Choose Save. The cardholder's page shows the Profile, their Cards and their Recent activity (View all opens the history of the live monitor for them).

Validity and status

Status and validity decide whether the cardholder's cards are on the controllers at all. Suspending a cardholder, or a validity period that ends, removes their cards from the controllers; reactivating them or a period that starts puts them back. Edge checks validity periods every minute, so a period takes effect within about a minute plus the time the controller needs to apply its new configuration.

Delete a cardholder

Delete on the cardholder's page removes them. Their cards return to the pool of unassigned cards and stop opening doors. The access log keeps their history.

Cards

Cards lists every card with its Number, Type, Label, Cardholder (or Unassigned) and Status. Search by number, label or cardholder: the 10-digit card number matches with or without its leading zeros (0015592682 or 15592682), and so does 237:60650. Unassigned only shows the pool.

Card types

Type	Number	Shown as
Wiegand 26	The card number printed on the card: up to 10 digits, 0000000000–0016777215. Or its Facility code (0-255) and Card number (0-65535).	0015592682 with 237:60650 beside it
iButton	iButton id (hex): 2–16 hexadecimal digits	01A2B3C4D5E6F708

Wiegand 26 card numbers

The 10-digit number printed on a Wiegand 26 card, such as 0015592682, is the card's 24 data bits as one decimal number, with leading zeros. Its first 8 bits are the facility code and its last 16 the card number:

• facility code = number ÷ 65,536 (whole part): 15592682 ÷ 65536 → 237
• card number = the remainder: 15592682 − 237 × 65536 → 60650

So 0015592682 is facility code 237, card number 60650. Edge stores and sends the two parts (the API keeps facility_code and card_number) and shows the card everywhere as the printed number, with facility code:card number beside it: on Cards, the cardholder's page, the live monitor, the history, the dashboard's recent events and the cardholder's recent activity.

A card number can be registered once per tenant (card_already_registered); iButton ids are compared without regard to case.

Register a card

Choose Register card on Cards, or Add card on a cardholder's page. Pick the Type and enter the number:

• Wiegand 26, Card number (the default): the number printed on the card, up to 10 digits, with or without its leading zeros. The dialog shows what it stands for (Facility code 237, card number 60650). More than 0016777215 or anything but digits is refused (Enter up to 10 digits, at most 0016777215).
• Wiegand 26, Facility code + number: for cards printed with the two parts. Switching between the two keeps a number already entered.
• iButton: the iButton id (hex).

Add an optional Label (e.g. Spare card 3), and under Assign to the cardholder or Nobody (pool). Choose Register.

Card actions

The menu of a card offers:

Action	Effect
Block	Status Suspended: the card opens nothing until reactivated.
Mark lost	Status Lost: the card opens nothing.
Reactivate	Back to Active.
Return to pool	Unassigns the card from its cardholder.
Delete	Removes the card; it stops opening doors. Register it again to use it.

Each of these removes the card from (or puts it back on) the controllers of its cardholder's doors within seconds.

The pool of unassigned cards

A card without a cardholder is in the pool: it is registered but opens nothing. Register a box of new cards into the pool with Nobody (pool) and give them out later. Assigning a pool card to a cardholder is done through the API (PATCH /tenants/{tenantID}/cards/{cardID} with cardholder_id); in the app, register the card for the person instead.

What reaches the controllers

A controller holds only the cards that may pass at least one of its doors, at most 2,000. Cards of people without access there, pool cards, blocked and lost cards are not sent. When more than 2,000 cards would have access through one controller, its configuration is not sent and it shows Failed with controller_capacity_exceeded (Configuration sync).