Administration and ownership

Who Signs Off on Door-Permission Changes, and How to Write the Workflow

← All articles

Approval for a door-permission change in a commercial building should rest with a named role on the owner's side, such as the property manager or a designated facility lead. It should not rest with whoever asks or with whoever holds administrator rights. The workflow should split three jobs: someone requests, a named approver decides, and a separate administrator makes the change in the system.

Why the person who decides should not be the person who edits the system

Administrator rights are a technical permission. They let someone add users, assign door groups, and edit schedules. They do not give that person authority to decide who belongs behind a door. When one person both decides and executes, nobody else sees the change until something goes wrong.

A workable approval chain has four roles. The requester asks for access. The approver is a named owner-side person who says yes or no for a given type of door. The administrator makes the change once approval exists. The record keeper holds the request, the decision, and the result in one place. In a small building the approver may also keep the records. The administrator should still be someone else.

What to settle before drafting the workflow

The answers the workflow depends on are usually scattered across leases, management agreements, and old emails. Gather them internally first:

  • Which entity owns the building and signs off on changes to shared doors?
  • Which doors are shared, such as the lobby, stairs, and loading door, and which belong to one tenant?
  • Who holds administrator access today, including former staff, past vendors, or the original installer?
  • What do the lease and management agreement say about authority over suite doors and common doors? Read the documents themselves rather than relying on memory.
  • Who is the backup when the main approver is away?

Admin accounts left over from an installation or a previous manager sit outside any approval chain until someone checks for them.

The request-to-review sequence

  1. Intake through one channel, such as a form or a shared inbox. A hallway conversation does not count as a request.
  2. Identity and need check: who the person is and why they need that door.
  3. Approval by the person assigned to that door's tier.
  4. Execution by the administrator, only after the approval is on record.
  5. Confirmation that the credential works at the door, noted in the record.
  6. Inclusion in the next scheduled permission review.

Tie approval tiers to door sensitivity

A lobby-hours change and a mechanical-room grant should not follow the same path. Common areas such as the lobby and amenity rooms need one owner-side approver, usually the property manager. Tenant suite access can be approved by a named tenant contact if the owner has delegated that authority. Back-of-house doors, including loading areas and storage, always need owner-side approval. IT closets, electrical rooms, and mechanical rooms sit at the top tier. Require two sign-offs for these rooms, and treat each grant as an exception rather than a standing permission.

Urgent grants, temporary access, and removals

Urgent requests are where informal habits creep back in. Name a backup approver for after-hours and weekend requests. Give every urgent grant a short expiry and a retroactive review. On the next business day, the primary approver either confirms the grant through the normal path or removes it.

Vendors and contractors should get temporary permissions with an expiry date set when the access is granted. Limit those permissions to the doors and hours the work needs. If the job runs long, the extension is a new request, not a quiet edit.

Removing access is also a change, and it needs an owner. Make the property manager responsible for tenant move-outs. Make the tenant contact or building supervisor who reports a departure responsible for that person's removal. Then have the administrator confirm the removal back into the record. Without a named owner, removals fall between roles.

What to hand the installer or system administrator

The written policy only helps if the system matches it. Give whoever configures or runs the access control system a handover package. It should include the approver list by tier with backups, door groups that mirror each tier, the request form fields, where records are kept, and the names of the people allowed to request changes. That last item matters. An administrator who acts on a call from anyone undoes the whole chain.

After setup, the policy needs periodic permission reviews. In each one, the approver compares the system's active users against approved records and removes any permission without a match.

Atlas Integrated Security works on access control, commercial smart locks, intercom and buzzer systems, and ADA door operators across New York City. To talk through the access control side of your building, call (347) 357-0985. Emergency service is available 24/7.

Frequently asked questions

Can a tenant approve access changes for their own suite?

A tenant can approve access changes for their own suite when the building owner has delegated that authority in writing to a named tenant contact. The delegation should stop at the suite door. Shared doors, back-of-house spaces, and utility rooms stay with the owner-side approver, who should also receive a copy of each suite-level change.

How often should the list of people with door permissions be reviewed?

A door-permission review should run on a fixed schedule the owner chooses and writes into the policy, for example quarterly. Add an extra review after any tenant move-out, after an approver or administrator leaves, and after any stretch with several urgent grants.

What should a door-permission request record include?

A door-permission request record should name the requester, the person receiving access, the specific doors, the days and hours, and the reason. It should also show who approved the request and when, who made the change, any expiry date, and when the credential was confirmed working at the door.

Who should hold administrator rights if the property manager changes?

Administrator rights for an access control system should belong to owner-side roles, not to one person. Before a property manager leaves, confirm that at least one other owner-side administrator account exists. Transfer the approver list and records, and disable the departing manager's account on their last day. An outside management company's access should end when its agreement ends.

Next step