When a building technology vendor leaves, remove their access from every system they could reach, not just the account you remember. Inventory cameras, access control, networks, cloud portals, and remote support tools; transfer ownership; rotate shared credentials; and test that authorized staff can still operate each system. Record the changes so the next handoff is controlled.
In This Article
- Which building systems should be included in a vendor offboarding?
- How do we remove a former vendor's access safely?
- What should we verify after a vendor's account is removed?
- How can Atlanta property teams keep the next handoff from becoming a scramble?
- When should we bring in help with building technology access?
- Frequently Asked Questions
Which building systems should be included in a vendor offboarding?
Start with the systems that affect daily operations: door access, video surveillance, network equipment, intercoms, building-management interfaces, and any cloud service used to administer them. Include the management accounts and remote connections behind the visible devices.
A camera can keep recording while a former installer still has administrative access to its portal. A door controller can appear local while relying on a vendor-managed account for configuration. Identify the system, its owner, its administrator, and its dependencies before changing anything.
In Atlanta commercial properties, responsibility can be split among the owner, property manager, tenant, facilities team, IT provider, and security contractor. Clarify who is authorized to approve a change, who must be available during testing, and which tenants or building functions could be affected.
Access review should cover every system, account, and remote path associated with the departing vendor.
Map the dependencies before access changes begin. A building technology audit can help property stakeholders make systems, dependencies, ownership, and vendor responsibilities visible.
How do we remove a former vendor's access safely?
First, establish who owns each system and confirm that an authorized internal administrator can sign in. Preserve required records and confirm the operational impact of each change with the people responsible for doors, cameras, networks, and tenant support.
- Inventory access. List named accounts, shared accounts, administrator roles, remote support connections, mobile apps, API integrations, and vendor-managed cloud portals.
- Transfer ownership. Move primary administration to an organization-controlled account and verify recovery methods and billing or subscription ownership where relevant.
- Remove individual access. Disable former vendor user accounts and revoke remote connections, tokens, and integrations that are no longer authorized.
- Rotate shared secrets. Change shared passwords, service credentials, and other secrets the departing vendor knew. Update authorized users and connected equipment through a planned change.
- Test operations. Confirm that an authorized staff member can perform essential tasks, such as reviewing camera status or managing an approved access-control change.
- Document the handoff. Record what changed, who approved it, what was tested, and any unresolved dependency or account recovery issue.
Do not treat a password change as the whole job. If the former vendor owns the cloud tenant, recovery email, or system registration, changing a local credential may not transfer control.
Use a controlled sequence, with the responsible operations and IT contacts available for verification. The goal is to close unnecessary access without interrupting a door, camera, or network function people rely on. Remove access only after ownership and continuity are understood.
What should we verify after a vendor's account is removed?
Test both sides of the handoff: the former vendor can no longer administer the system, and authorized staff still can. Check login access, administrator roles, recovery options, remote connectivity, and the tasks needed to keep the building running.
For access control, verify that the appropriate staff can manage the agreed functions and that doors operate as expected. For surveillance, check that authorized users can reach the management interface and review the expected camera views. For network equipment, confirm that the organization retains administrative access and can identify the person responsible for changes.
Keep IT, facilities, and security responsibilities distinct where they are distinct in practice. An IT administrator may control network connectivity without owning door schedules or camera retention decisions. The responsible system owner should approve tests that affect operational settings.
If a system is undocumented or the only administrator account belongs to the departing vendor, pause before making a change that could lock out the organization. Recover ownership through the vendor or manufacturer's documented process, and capture the result in the handoff record.
Verification is complete when named internal owners can access and operate the systems they are responsible for. A successful password reset alone is not proof of ownership.
How can Atlanta property teams keep the next handoff from becoming a scramble?
Make access ownership part of vendor onboarding, project acceptance, and contract closeout. Require organization-controlled administrator accounts, a current system inventory, and documentation of vendor responsibilities before work begins. At the end of an engagement, use the same record to remove access and confirm operational handoff.
- Keep a current register of building systems, account owners, administrators, and support responsibilities.
- Use named accounts where systems support them, rather than relying on a shared vendor login.
- Store recovery information under organizational control and limit it to authorized people.
- Record remote support paths, integrations, and vendor-managed services alongside physical equipment.
- Set a documented offboarding trigger for contract end, staff change, or scope completion.
- Schedule a joint test with the relevant property, facilities, IT, and security owners.
For properties across Metro Atlanta, including multi-tenant buildings, the handoff should account for tenant workflows as well as ownership boundaries. A technology change that appears administrative can affect entry, monitoring, or support. Keep the operational contact informed and document the approved scope.
A real-world service detail reflects why follow-through matters: Kawal, a professional services client, said, "GDS followed up the next day to make sure the door sensor issue is resolved. That kind of attention shows real customer service." The practical lesson is to verify the result with the person responsible for the affected system, not assume the change worked because the ticket closed.
Make ownership and offboarding routine, not dependent on someone remembering the final checklist.
When should we bring in help with building technology access?
Get a qualified review when nobody can identify the system owner, a vendor controls the only administrator account, access paths are unclear, or a change could affect occupied space. These are signs that the issue is broader than removing one user account.
A building technology audit can map systems, dependencies, ownership, and vendor responsibilities into findings and a priority roadmap. For physical systems, scoped access-control maintenance or video surveillance support can help investigate the equipment and configuration within an agreed scope.
For Atlanta property owners and managers, coordinate the review with the people accountable for building operations and tenant communication. If a system supports an applicable compliance obligation, involve the organization's compliance owner or advisor; technology work alone does not establish compliance.
GDS Technology supports building infrastructure work including riser management, structured cabling, and physical security systems. The right next step is to identify the system, confirm who owns it, and walk the dependencies with operations and IT together.
Ask the operational question first: if this former vendor's access disappears today, who can still keep the building working?
We talked about this on our podcast (Build Wired Secured - Podcast): Expansion Room Test for Building Technology.
Frequently Asked Questions
What should we do first when a building technology vendor leaves?
Identify every system the vendor could access, including cloud portals, remote support tools, cameras, access control, and network equipment. Confirm internal ownership and authorized administrator access before removing accounts. Then revoke the vendor's access, rotate shared credentials, test essential functions, and document the handoff with the responsible operations and IT contacts.
Is changing the shared password enough to remove a former vendor?
Not necessarily. The vendor may still have an individual administrator account, a remote connection, an active token, or ownership of the cloud portal and its recovery methods. Review each access path and integration. Rotate shared credentials where appropriate, remove accounts that are no longer authorized, and verify that internal administrators control recovery.
How can we avoid disrupting doors or cameras during offboarding?
Plan changes with the system owner and the people responsible for building operations. Confirm internal access first, understand dependencies, make changes in a controlled sequence, and test the functions staff rely on. If ownership is unclear or a change could lock out the organization, pause and resolve the ownership issue before altering configuration.
Who should own building technology access after a vendor leaves?
The organization should designate an accountable owner for each system, with named administrators and a clear support path. Responsibility may differ across IT, facilities, security, property management, and tenants. Record those boundaries, keep administrative and recovery access under organizational control, and involve the relevant owner when testing changes.
Follow GDS Technology on Facebook, and subscribe on YouTube for new videos.