Installation
Colocation Installation Access: A Badge Is Only One Approval
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]
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]
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]
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]
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 permissionsChecked 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 visitChecked 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 scopeChecked 2026-10-15. Tenant-side physical work at authorized customer facilities; operator services, hosting and facility access decisions are separate.