---
title: "Colocation Installation Access: A Badge Is Only One Approval"
description: "Leviathan Systems — Technical content Published 2026-10-15; updated 2026-10-19."
canonical: "https://www.leviathansystems.co/articles/colocation-installation-work-authorization"
last-updated: "2026-10-19"
---

# Colocation Installation Access: A Badge Is Only One Approval

Leviathan Systems — Technical content
Published 2026-10-15; updated 2026-10-19.

A badge establishes only the access granted under the facility’s process. Before releasing installation work, confirm the authorized people, exact space, permitted task, work window and any separate permissions for recording or equipment movement. Keep customer instructions and operator authorization connected, because one cannot be assumed from the other.

## Separate who can enter from what they may do

A technician may be permitted to enter a site while lacking access to a particular customer space or authority for a specific activity. Identify the customer who commissions the work, the facility contact and the person who can resolve an access discrepancy. State the actual work location and boundary.

Equinix’s published IBX permission model distinguishes entry, guest access, cages/cabinets, equipment removal and work-visit capabilities. This is one operator’s example of separate permissions, not a rulebook for every colocation provider. Obtain the current requirements from the actual facility.

References: [E1](https://docs.equinix.com/iam/colocation-access-control/admin-ibx-access-permissions/)

## Give each workfront an authorization record

Use the project’s actual reference numbers and approved contacts. Keep identity documents, private visitor details and access credentials in the operator’s authorized process rather than copying them into a general installation worksheet.

Illustrative tenant work-authorization record
| Boundary | Evidence reference | Unresolved question | Source |
| --- | --- | --- | --- |
| People | Approved visitor/technician list and applicable induction reference | Are the actual assigned people authorized? | Planning analysis |
| Place | Site, tenant space and cabinet/workfront identifiers | Does access cover the location where the task occurs? | Planning analysis |
| Task | Customer-released work package and operator-required approval | Is the described work permitted in that area? | Planning analysis |
| Time | Confirmed site window and relevant restrictions | What happens if the task crosses the permitted window? | Planning analysis |
| Recording | Actual permission for required photographs or alternate evidence | Can the agreed handoff evidence be collected? | Planning analysis |
| Equipment movement | Receiving/removal/custody authorization where applicable | Who can release or accept the specific items? | Planning analysis |
Original illustrative planning record. Identifiers and quantities are hypothetical, not a customer record, engineering design or acceptance standard.

## Resolve recording permission before promising photographs

Equinix’s work-visit guidance requires prior approval for recording equipment. If a project needs installation photographs, confirm the actual site’s permitted process before making them a deliverable. An operator may offer an alternative evidence route; do not assume a personal phone is permitted in every area.

Agree which views the accepting owner needs and whether labels or neighboring customer equipment must be excluded. Use only authorized storage and recipients. This guide does not create a company photo-retention policy or permission to publish a customer’s infrastructure.

References: [E2](https://docs.equinix.com/visiting-an-ibx/ecp-work-visits/)

## Check the boundary around a live neighboring space

Confirm which pathways, panels, shared areas and equipment belong to the released tenant package. An escort into a shared room does not automatically authorize work on its provider-controlled infrastructure. If the task reaches a boundary outside the approved space, obtain the responsible owner’s instructions.

Illustrative example: the customer’s schedule requires a panel-to-cabinet extension, but the team is authorized only inside the cage and the panel lies elsewhere. Record the location and affected link. The customer/operator must resolve who performs the missing segment; the installer should not extend its work area from an assumption.

## Keep access exceptions separate from technical changes

An access issue can block a task without changing the network design. Conversely, approved access does not establish that drawings, materials, handling arrangements or technical instructions are ready. Report each missing prerequisite with its owner and affected workfront.

If the permitted window changes, ask the project coordinator to reassess dependencies and availability. Do not promise a substitute crew, same-day mobilization or a schedule recovery before the actual resources and site requirements are known.

## Reconcile the actual assigned people with each work area

A project can have a recorded work visit and still lack a confirmed permission for the person or cabinet involved in the next task. A changed technician, a different cabinet or a newly requested activity changes what needs to be checked. Relate the actual assigned person and location to the relevant authorization reference; the original crew list is not evidence that a replacement person has been accepted.

Equinix provides a specific example of this distinction: its permissions page says that cage access does not automatically grant cabinet access, or the reverse. It also describes an escort requirement when a user has cabinet permission without cage permission. These are named-operator rules, not a permission model for every facility. Ask the actual operator to confirm the permitted arrangement instead of treating an escort, open door or colleague’s badge as authority to work.

Where the destination requires an induction, security enrollment or other site prerequisite, confirm the applicable record for the actual person and visit. A training record is not automatically a task authorization, and a site authorization does not establish an OEM qualification. Do not invent a universal induction certificate or use a project spreadsheet as a substitute for the operator’s identity process.

References: [E1](https://docs.equinix.com/iam/colocation-access-control/admin-ibx-access-permissions/)

## Worked authorization review: one visit, several open permissions

Consider fictional work package EX-W04 for customer equipment in cabinet EX-C12 within tenant cage EX-T. The customer has released a defined installation task. The visit record EX-V07 names technician EX-A, whose entry and cage access have been confirmed. Cabinet-specific permission is not yet resolved. Before the visit, the assigned crew changes to technician EX-B. The coordinator also requests handoff photographs and asks the installer to deal with a connection at a provider-controlled panel outside the cage.

These facts do not add up to an unrestricted work release. The customer’s approved task, the operator’s people-and-place permissions and the permissions for recording or a shared area remain separate. The matrix identifies the missing decisions rather than diagnosing a technical problem or prescribing how to gain access. It uses no real person, facility, credential, topology or approved work order.

Keep unresolved boundaries attached to the affected task. The responsible customer and facility contacts must decide whether the actual package can be released, narrowed, reassigned or kept on hold. Do not infer permission for the original technician, replacement technician or shared-area work from another row that is already confirmed.

Original EX-W04 example: distinguish evidence from an authorization decision
| Boundary | Evidence currently available | Decision still needed | Effect on the work package | Source |
| --- | --- | --- | --- | --- |
| Assigned person | EX-V07 names EX-A; the proposed crew now uses EX-B. | The authorized customer/facility contact confirms the applicable visitor or enrollment process for EX-B. | EX-A’s confirmed record does not demonstrate permission for EX-B. | Planning analysis |
| Site prerequisite | Only EX-A’s site-required induction reference is in the project record. | Confirm which prerequisites the destination actually requires and whether EX-B’s applicable record is complete. | Do not mark a site prerequisite complete from a different person’s reference or invent a universal certificate. | Planning analysis |
| Cage and cabinet | EX-A’s entry/cage permission is confirmed; EX-C12 permission is unresolved. | The facility confirms the actual assigned person’s cabinet access and any required approved arrangement. | An authorized cage visit does not settle access to every cabinet or transfer to the replacement person. | Planning analysis |
| Provider-controlled location | EX-W04 covers the tenant task; the requested panel is outside the released tenant area. | Customer/facility owners identify who may perform the panel-side activity and which authorization or separate service is required. | Keep that interface outside the installer’s released work until the responsible parties resolve it. | Planning analysis |
| Recording | The requested handoff includes photographs; no applicable recording permission is referenced. | The actual facility confirms its recording route; the accepting owner agrees an authorized evidence method. | A photo deliverable cannot create permission to record. Do not use an unapproved personal device or substitute evidence without agreement. | Planning analysis |
Fictional documentary review only. It is not an access permit, operating instruction, universal operator policy, safety assessment, network design or actual customer authorization.

## Record the specific decision that changes the release

A reply saying access approved can leave the original question unanswered. Record what the authorized decision actually covers: the assigned people, place, task, permitted window, recording or movement limit, reference and issuing owner. A confirmation for EX-B’s visit should not silently close the cabinet question, authorize provider-panel work or approve photography. Keep each remaining restriction linked to its affected task.

For the fictional package, a useful clarification request is: “For EX-W04 and EX-V07, confirm the actual assigned technician, the permitted cage/cabinet, applicable site prerequisites and recording route. Identify the owner and authorization needed for the provider-panel interface. Return the relevant references and limits so the customer can reconcile the work release.” This requests a decision; it does not supply an approval or a method for changing account permissions.

After the authorized parties respond, reconcile the project record with their actual decisions. Retain the changed person/location reference and any remaining restriction so the next coordinator does not reuse a superseded assumption. Store identity documents, QR codes, badge details and personal contact information only in the parties’ authorized channels; the general work-package record can point to the controlled authorization without reproducing those credentials.

A narrowed task still needs its own approved technical inputs and site conditions. Access confirmation does not select an assembly, approve handling or authorize electrical, liquid-side, structural or other specialist work. If the missing interface belongs to a provider order, use the separate cross-connect or facility-service process rather than expanding the tenant installer’s authority.

- Which actual person and organization does the decision cover?
- Which site, cage, cabinet or other area is included?
- Which task, window and restrictions are confirmed?
- Are recording, equipment movement or shared-area permissions separate?
- Who issued the decision, where is its controlled reference, and what remains open?
- Does the current customer work release reflect those exact limits?

## Release only the package the evidence supports

Before the field handoff, reconcile the permitted people, place, activity, window and evidence collection with the customer’s current instructions. Keep any unresolved restriction visible in the work package. Store the operator authorization reference so the next shift can retrieve the actual decision.

Leviathan supports agreed tenant-side physical installation at customer facilities, subject to scope, site requirements and team availability. It does not sell colocation space or replace the operator’s access authority. Share the planned workfront and known restrictions when discussing the installation package.

References: [L4](https://www.leviathansystems.co/services/colocation-installation)

## Common planning questions

### Does a valid badge authorize every installation activity?

No. Check the actual space, task, time and equipment permissions under the facility’s process and the customer’s scope release.

### Can we assume photographs are allowed for the as-built handoff?

No. Confirm the actual site’s recording rules and permission. Agree an authorized evidence method before promising photographs.

### Does a replacement technician inherit the original technician’s confirmed visit or induction record?

Do not assume that. Reconcile the actual assigned person with the facility’s applicable visitor, enrollment and site-prerequisite process. An original crew list or another person’s completed induction reference does not establish permission for the replacement. Use the authorized customer/facility contacts; this article does not create a universal induction requirement.

### Does permission for a cage automatically cover its cabinets?

Check the actual operator’s model. The cited Equinix permissions page explicitly separates cage and cabinet permissions and describes an escort condition for cabinet access without cage access. That named example is not a rule for every facility, and it does not establish a particular person’s entitlement or permission to perform a task.

### Can a customer’s approved task authorize work at a provider-controlled panel?

The customer work package does not replace the facility’s control of restricted areas or provider infrastructure. Identify the permitted work location, responsible provider/customer owners and any separate authorization or service needed. Keep the unresolved interface visible instead of treating a tenant-side release as unrestricted access.

## Primary sources

- [E1 — Equinix IBX access permissions](https://docs.equinix.com/iam/colocation-access-control/admin-ibx-access-permissions/). Checked 2026-10-15. One operator distinguishes entry, cage/cabinet, work-visit and equipment-removal permissions. Actual site policies and authorization control.
- [E2 — Equinix: scheduling a work visit](https://docs.equinix.com/visiting-an-ibx/ecp-work-visits/). Checked 2026-10-15. One operator example, including prior permission for recording equipment. Do not generalize its permissions, duration or service terms to every facility.
- [L4 — Leviathan colocation installation scope](https://www.leviathansystems.co/services/colocation-installation). Checked 2026-10-15. Tenant-side physical work at authorized customer facilities; operator services, hosting and facility access decisions are separate.

## Related Leviathan resources

- [Colocation Cross-Connects vs Tenant Cabling: Close the Handoff Gap](/articles/colocation-cross-connect-vs-tenant-cabling)
- [Receiving and Staging GPU Equipment: A Custody Checklist](/articles/receiving-staging-gpu-equipment)
- [Data Center Installation Daily Report: Count Work Without Hiding Holds](/articles/data-center-installation-daily-report)
- [Colocation installation scope](/services/colocation-installation)

## Prepare the tenant installation workfront

Share the permitted space, current work package, access process, site window and evidence restrictions.

[Discuss the scope](/contact?service=colocation-installation&from=/articles/colocation-installation-work-authorization)