> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/knowledge-base/tenants.md). # Tenants Guides for creating and operating tenants in multi-tenant VergeOS environments. * [Allow Root to Tenant Site Connection](/knowledge-base/tenants/allow-root-to-tenant-site-connection.md) — How to configure a network rule on the root system's external network to allow site-to-site connectivity between the root system and a… * [Configuring Proxy](/knowledge-base/tenants/configuring-proxy.md) — How to configure a proxy connection to serve multiple tenant environments using a single IP address mapped to FQDN hostnames. * [Device Passthrough Advanced Configuration](/knowledge-base/tenants/dev-passthrough-advanced.md) — Advanced configuration information for device passthrough including manual creation and editing of resource rules for PCI, USB, SR-IOV, and… * [Provide Layer 2 Access to a Tenant - LEGACY](/knowledge-base/tenants/provide-layer2-to-tenant.md) — Instructions for using Virtual Switch Ports (formerly Virtual Wires) to provide VLAN-based Layer 2 network access to a tenant, including… * [Reset a Tenant's Administrative Password](/knowledge-base/tenants/reset-a-tenants-administrative-password.md) — Step-by-step instructions for resetting the administrative password for a tenant environment in VergeOS. * [Sharing a VM into a Tenant](/knowledge-base/tenants/sharing-a-vm-into-a-tenant.md) — How to share a virtual machine image from a parent environment into a tenant using snapshots and shared objects in VergeOS. * [Sharing Files to Tenants](/knowledge-base/tenants/sharing-files-to-tenants.md) — How to share files such as media images from a Service Provider to Tenants using the VergeOS branch command feature. * [Tenant Crash Cart Guide](/knowledge-base/tenants/tenant-crash-cart-guide.md) — How to deploy and use the Tenant Crash Cart utility VM to gain emergency access to a tenant's VergeOS UI when normal network access is… * [Tenant External IP Quick Start Guide](/knowledge-base/tenants/configuring-tenant-external-ips.md) — Step-by-step guide to configuring external and public IP addresses for tenant VMs, covering single IP, IP block, and NAT-only scenarios. * [Tenant Node Planning Guide](/knowledge-base/tenants/tenant-node-planning-guide.md) — Guide for determining the optimal number of tenant nodes, compute resource allocation, and physical placement strategies for VergeOS tenant… * [Viewing Tenant Consumption Statistics](/knowledge-base/tenants/viewing-tenant-consumption-statistics.md) — How to view tenant RAM and storage consumption statistics using the tenant history dashboard, including 95th percentile calculations. * [VM and Tenant Hot-Plug Capabilities](/knowledge-base/tenants/vm-hotplug-capabilities.md) — Understanding which resources can be modified on running VMs and tenants without requiring a restart, including drives, NICs, RAM, and CPU… --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.verge.io/knowledge-base/tenants.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.