Municipal Building Access: Give Every Badge a Clear Purpose

Start with the work behind the badge

Imagine a contractor arriving at a township hall for an approved repair. The badge opens the intended entrance, but it also allows access to offices the contractor does not need. Elsewhere, a staff member preparing an evening meeting discovers that their credential only works during daytime hours. Both situations begin with a permission decision that needed a more specific conversation.

For Michigan townships, villages, and cities, electronic building access should reflect the person, place, and task. Begin with one building and ask who needs to enter which areas, at what times, and for how long. The municipality decides what is appropriate; the installer or system administrator configures and checks that decision. A working reader alone does not answer those questions.

Name the people who approve and administer access

Identify a municipal owner who can authorize new access and a backup for absences. Separately, name the person or provider who changes the system. Staff should know how to request a badge and who can approve a change to its permissions. Keep administrator access limited to the people responsible for that work, with an approved way to contact them.

NIST's physical access authorization control, PE-2, provides useful planning ideas: maintain an approved access list, review it, and remove people when their access is no longer needed. Use those ideas to make your own review understandable. For each credential, record its holder, approving contact, intended doors, and review or end date. Keep this information in an approved location available to the responsible staff.

Write down the doors and hours before configuring them

Use recognizable door names, such as the public works staff entrance or the hall's east entrance. Give the administrator a short permission description tied to the job. A custodian's needs may differ from a clerk's, and neither should automatically inherit every exception accumulated by another employee. Ask the owner to review the proposed access before a credential is issued.

Axis's Secure Entry documentation illustrates how access rules combine people or groups, doors or zones, and schedules. Ask your installer how the equivalent pieces work in your system. Review the full result, including group memberships and individual permissions. In a hypothetical village hall, approving a cleaner's evening entry does not automatically approve access to a records room or unrestricted entry throughout the week.

Check badge hours and public opening hours separately

The times when a staff badge works and the times when an entrance is unlocked for residents are different decisions. Axis documents scheduled door unlocking separately from access-rule schedules. Have the building owner and installer explain both settings for your entrances. Include observed holidays, evening public meetings, and temporary closures in the review rather than assuming the ordinary weekday plan covers them.

For an evening township meeting, decide which entrance residents should use, who prepares it, and who confirms the approved closing arrangement afterward. Review any temporary schedule change before the event and record when it ends. Have the installer handle hardware and safety-related configuration under the building's approved requirements. The office's job is to describe the intended use and check that staff know their responsibilities.

Give temporary access an end point

When a vendor needs access for a project, record the approved work period, relevant entrances, and municipal contact. Issue credentials through the agreed process so the owner can identify who received them. Avoid casually lending another employee's badge, which makes the assignment harder to manage. Decide how extensions are requested before the original work period finishes.

Axis documents credential start and expiration settings. Ask whether your system supports an appropriate end date and how the administrator verifies it. For a hypothetical two-day repair, test the approved credential during the planned work window and confirm how its access will end. Keep a completion step for returning issued items and closing the permission record, even when an automatic expiration is configured.

Make lost badges and role changes easy to report

Give staff a clear contact method for a missing badge and explain what details to provide: holder, building, credential identifier if available, and when the loss was noticed. Have an authorized administrator apply the approved restriction and confirm completion. A replacement badge should be linked to a deliberate permission review, with the old credential handled explicitly.

Review building access when a role changes or a project ends, alongside the office's staff transition process. Ask the administrator how blocking access differs from deleting a record and what happens to information the municipality needs to preserve. Keep preservation decisions with the responsible municipal owner. Record the result so collecting a badge or sending an email is followed by confirmation that the intended access change occurred.

Test one badge against its approved purpose

Arrange an approved test with the building owner and installer that preserves normal operations. Check permitted entry and an expected denial where appropriate, with someone available to assist. Useful IT support for municipalities connects the configuration with the building's daily work. Bring the results to your next Michigan IT services review using this checklist.

• Identify the badge holder, municipal approver, and administrator.
• Confirm the intended doors, hours, and any group-based permissions.
• Review public unlocking schedules and special-event changes separately.
• Verify the start and end arrangements for temporary access.
• Check the lost-badge contact and access-change completion process.
• Record the test results, unresolved issues, and the next access review.