Door Access Credential Setup in Katy, TX 77492

When the same badge has to work at two addresses

The first question on a multi-site credential build is not which badge, it is whether the two buildings are ever going to share one list. That answer changes everything downstream, and it has to be settled before a single credential is ordered.

If your controllers are cloud-managed, both sites can live in one account: one person record, one badge, groups per site, and a leaver removed once. If the software is an application sitting on a back-office computer at the first building, it cannot see the second building unless somebody deliberately connects them across the network. Businesses that grew into a second location usually discover this the hard way – two separate systems, two separate lists, two separate passwords, and a person who exists twice with two different badges.

Running two independent systems is a legitimate choice if the sites are genuinely unrelated, with different staff and different managers. It stops being legitimate the moment one person works at both, because from that point every joiner, mover and leaver is two jobs, and the second one is the one that gets forgotten.

Naming and numbering: the dull decision that pays for a decade

Access reports are read years after they are configured, usually by somebody who was not there when it was set up, often during an unpleasant week. Names that made sense to the installer on day one – Door 3, Reader 2, Group A – are worthless in that moment, and doubly so when both buildings have a Door 3.

One extra habit is worth building: the printed number on a badge and the number the panel actually stores are often not the same figure, because of how the credential was encoded at the factory. Recording both against the person means a badge found in a car park can be traced to a record in seconds instead of being tested against a reader by trial and error.

Keeping one building’s badge out of the other building by design

The safe default is that a new credential opens nothing at all until a group is added to it. Systems configured the other way – where a badge inherits a broad default and doors are then subtracted – produce access nobody intended and nobody can see, because a negative permission is invisible on a summary screen.

Order credential stock in ranges, one range per site

Ask for contiguous, non-overlapping number ranges when credentials are ordered, keep one range per building, and write the range on the handover sheet. Then never let leftover stock migrate between sites in somebody’s glovebox. Where two buildings are on separate systems, duplicated badge numbers are the most common cause of a record that looks correct and behaves wrongly – and if the two systems are later merged onto one platform, duplicates have to be reconciled by hand before the merge can proceed.

Cross-site access should be dated, not permanent

When a driver, a manager or a technician genuinely needs both buildings, the clean answer is a second group with a start and end date, not a permanent addition that everybody forgets. People who cover another site for a quarter rarely hand that access back, and eight years of quarters is how a company ends up with six people who can open every door it owns.

Seasonal crews and subcontractors: pre-stage the batch, do not improvise it

Businesses working out of Katy with crews that scale up and down – trades, fit-out contractors, event and service work – lose control of credentials at intake, not at exit. Twelve people arrive on a Monday, somebody is handed the drawer of spare fobs, and by Friday nobody can say which fob went to whom.

The fix takes half an hour before the crew arrives. Create the records in advance as a named batch, assign a contiguous block of badge numbers to them, set them inactive with an activation date of the first shift and an expiry date on the last day of the engagement. On the day, names are attached to already-numbered badges and the crew lead signs one sheet for the block.

Two things follow from that. Unreturned badges switch themselves off when the job ends, so the exposure closes even when the paperwork does not. And the reconciliation at the end is a single list compared against a single block, which takes minutes rather than an afternoon of testing fobs at a reader.

The event log is a business record – decide who owns it before you need it

Every controller keeps a log of credential events, and almost nobody reads it until something has gone wrong. Three things about it are worth settling at setup.

Know what it actually proves. The log records that a specific credential was presented at a specific reader at a specific minute. It does not record who was holding it. That is a meaningful distinction if a badge has been lent, lost or left in a shared vehicle, and it is why a credential log should never be treated as a timekeeping system.

Know how long it keeps. Panel and software storage is finite, and most systems overwrite the oldest events once the buffer is full. On a busy site with several doors that can mean weeks rather than years. If an incident has happened, exporting the relevant period immediately matters more than anything else you might do that day.

Know who may pull a report. Reports about staff movement are sensitive, and the ability to run them should sit with named people rather than with anyone who can log in. We set that at the same time we set the administrator accounts, so it is a decision rather than an accident.

Backups, succession, and the week your office manager resigns

The single most disruptive event for a small multi-site access system is not a hardware failure. It is the departure of the one person who knew the login.

We set up two protections. The first is a scheduled export of the cardholder list and the group structure, taken quarterly, stored somewhere the owner controls rather than only on the administrator’s own machine or personal drive. An export nobody has ever opened is not a backup – we open one during handover so you have seen what it contains.

The second is a written resignation-day sequence, because in most systems it is not one action but five: change the administrator password, void that person’s own credential at every site, revoke their access to the management software, revoke any phone credential issued to them, and take them off the alarm contact list if that is separate. Companies routinely do the first and skip the rest, which leaves a former administrator with a working badge and a working login.

What the appointment covers, and what changes the number

A multi-site credential build normally runs as one planning session and one enrolment pass per building. We map the existing structure at both sites, agree the naming standard and the number ranges on paper, build the groups, import or rebuild the person list, enrol staff, test each group at the doors it should and should not open, then train two administrators and hand over the export, the ranges and the resignation-day sequence.

What changes the quote: whether both buildings end up on one platform or stay separate, travel between the sites, how much of an existing list has to be cleaned rather than rebuilt, how many credential batches need pre-staging, licence seats where phone credentials are wanted, and whether enrolment has to happen outside operating hours. The estimate is free, we walk both buildings before quoting, and the quote is itemised so you can stage it across two visits if that suits the budget.

Recurring faults we get called to correct on multi-site systems: badge stock delivered to the mailing box and never collected before enrolment day; the same badge numbers issued at both buildings; a leaver removed at the site they worked at most and left active at the other; and an administrator handover that transferred the password but not the ability to reset it.

Related services

Frequently asked questions