Access Credential Management in Fresno, TX 77545

Credential management is a lifecycle, not an install

Readers and locks are hardware. A credential is the permission riding on a card, a key fob, a phone or a PIN, and managing it means controlling five moments: issue, scope, change, expiry and revocation.

Most Fort Bend systems we are called to were installed correctly and then left alone. What has drifted is the list behind the hardware: fobs issued to households that moved out two leases ago, a PIN the whole staff has known since opening day, a contractor card with no end date, and an administrator login that belonged to someone no longer involved. None of that lights a fault LED; it surfaces when you need to know who opened a door at 11:40 p.m. and the answer is a fob assigned to nobody.

• Issue – each credential tied to one named person, recorded when it is handed over.
• Scope – which doors or gates it opens, and during which hours.
• Change – what happens when a role, a lease or a membership changes.
• Expiry – an end date on anything temporary: vendors, seasonal help, short leases.
• Revocation and audit – switching it off the day it should stop, and proving it did.

Pool gates and clubhouses in the newer subdivisions

Master-planned neighborhoods on the Fresno side of Fort Bend, Teal Run among them, usually control the pool, fitness room or clubhouse with a fob reader on a gate or door. The problem is rarely the reader. The fob list was built one household at a time, often under more than one management company, and never reconciled against the current roll.

What we usually find

• Fobs recorded against a lot number or street address with no resident name, so a move-out never triggers a deactivation.
• More active fobs than homes, because 125 kHz fobs can be duplicated in seconds at kiosk-style copy machines and some households have copied theirs.
• Pool-hour schedules that were never updated after the board changed the hours, or that slip an hour at each daylight-saving change because the controller clock does not adjust itself.
• No record of which fobs the board suspended, or why.

How we straighten it out

We export the list, match every active fob to a resident on the roll your management company provides, and flag the leftovers for the board. Suspension rules, such as what happens when an account falls behind, come from your governing documents and your board, not from us; we configure what the board adopts and make sure each suspension is logged with a reason. If copying is the root cause, the durable fix is a credential that cannot be cloned at a kiosk: a 13.56 MHz card or fob using a secured format such as DESFire EV2/EV3, or a phone credential. That normally means new readers, so it is priced as an option.

Rented homes: codes that should turn over with the lease

Plenty of houses in Fresno’s newer sections are leased, and keypad deadbolts or smart locks are common on them. A rental lock typically carries three kinds of code at once: the tenant’s, the property manager’s and each vendor’s. The failure is predictable. At move-out the tenant’s code is deleted, but the pest-control code from two years ago, and the code the previous tenant gave a relative, keep working.

1. Give every occupant their own code, never a shared family code, so the lock history shows who entered.
2. Put vendor codes on a weekday daytime schedule, or make them expire when the job is done.
3. At turnover, wipe every code except the manager’s and issue fresh ones; changing only the tenant’s code is not a reset.
4. Confirm the lock received the change. Wi-Fi and hub-connected locks apply edits when they next sync, and a lock with weak signal on a garage entry can sit on stale codes for days.

If the tenant also holds an HOA amenity fob, the lease end date should drive both lists; that landlord-to-HOA hand-off is where rental credentials leak.

Daycares, churches and storage lots along Hwy 6 and FM 521

Each of Fresno’s small commercial site types uses credentials differently.

• Childcare centers often want staff on individual badges or PINs and families on codes limited to drop-off and pickup hours. What your licensing and policies require about entry and sign-in is your decision; our job is to make the door enforce it and keep a record. Family codes need a clean way to expire when a child leaves the program.
• Churches run on volunteers: a long, changing list with office staff on weekdays, worship teams on set evenings and facilities crews on Saturdays. Access levels per ministry, each with its own time window, keep a Tuesday-night code from opening the building at 3 a.m.
• Self-storage gate codes are usually issued by the facility’s management software with each rental, and that software can lock out a delinquent unit. When the keypad and the software stop talking, through a failed interface or a replaced keypad that was never re-linked, codes stop matching accounts. We check the link end to end with a live code, an expired one and a locked-out one.
• Contractor yards and shops tend to share one gate code with every driver and sub. Individual codes for regulars and expiring codes for one-off deliveries make that gate accountable.

Card formats, facility codes, and why reordering ‘standard’ fobs backfires

Most card and fob systems around here still use the 26-bit Wiegand format known as H10301: an 8-bit facility code with values from 0 to 255, and a 16-bit card number from 0 to 65,535. The industry shares that small number space, so reordering generic 26-bit fobs without naming your facility code and next free range can deliver duplicates of numbers already enrolled.

One more trap: the number printed on a fob is not always the number the reader sends. Enrolling from the printed number, or picking the wrong format in the software, produces a fob that beeps and is refused. We enroll by presenting each credential to a reader and confirming the decoded facility code and number match the record.

When you can handle it yourself, and when to call

With a working admin login on a supported platform, adding or removing a few people is a do-it-yourself job. Bring us in when:

• nobody has the admin password, or it belongs to a former manager or a previous management company;
• there are more active credentials than people and nobody can say who holds the extras;
• new fobs are refused even though they look identical to the old ones;
• schedules are an hour off, or a door unlocks on a holiday nobody scheduled;
• you want to change credential technology, add doors, or put a gate on the same list.

What an EVOTECH visit in 77545 looks like

We cover Fresno from our Katy/Houston base, as part of the Fort Bend area that includes Sugar Land and Richmond. Before booking, phone (832) 359-2425 with your street address so we can confirm a slot that works.

1. Inventory. Every reader, controller, keypad and gate interface, with make, model and firmware where it can be read. A sample of your credentials is read to identify technology and format.
2. Export and reconcile. The user list is compared against your roster or resident roll. Unmatched credentials go on a list for your decision; nothing is deleted without your approval.
3. Structure. A naming convention, access levels, schedules, a holiday table, and end dates on everything temporary.
4. Administration. Individual admin logins at the right permission level, so every change is attributable to a person.
5. Test. Each door or gate is tried with a valid fob, an expired one and a revoked one, and the event log is checked for all three.
6. Hand-over. A written summary of what is configured, who holds admin rights, and how to add or remove someone.

What changes the scope of the quote

You receive an itemized quote after the on-site estimate. What moves it: the number of doors, gates and keypads; how many credentials need reconciling; whether the current software and controllers can be kept or are too old to do what you need; whether new credentials are being issued and in which technology; any platform licensing or subscription; whether a storage-software or other integration needs repair; and whether reader, lock or wiring changes are part of the work.

The mistakes that bring us back out

• Removing a person in the software while a battery lock stays unsynced, so the credential still opens that one door.
• One shared administrator login, which leaves no way to tell who changed what.
• An empty holiday table, so a scheduled unlock opens the clubhouse on Thanksgiving with nobody there.
• Readers fixed straight to steel gate frames without a spacer; metal detunes the antenna and read range collapses.
• Reordering fobs with no facility code or number range specified.
• Nobody keeping a copy of the user database, so a dead controller turns into re-enrolling every resident by hand.

Related services

Frequently asked questions