---
title: "Managing Subtenants"
canonical: "https://docs.infoblox.com/space/BloxOneInfrastructure/327778306/Managing%20Subtenants"
format: markdown
---
You may purchase the Infoblox SANDBOX license for subtenant deployment. The Infoblox [SANDBOX license](https://www.infoblox.com/company/legal/bloxone-sandbox-supplemental-terms-and-conditions/) enables the deployment and use of subtenants for non-production purposes, such as configuration and testing.

Subtenants provisioned through the SANDBOX license are commonly used to:

- Explore new features
- Validate configuration changes
- Test security policies
- Perform other pre-production evaluations

These environments help ensure that changes are thoroughly tested before being implemented in a production environment.

# About the Infoblox Subtenant

- Per the *[Infoblox terms and conditions](https://www.infoblox.com/company/legal/bloxone-sandbox-supplemental-terms-and-conditions/)*, an Infoblox subtenant is a temporary, non-production account that includes the same features and capabilities as its parent account.
- Each Sandbox license allows for one non-production subtenant per Infoblox account.
- Each subtenant has a defined maximum consumption rate. A subtenant is considered a production instance if its consumption rate exceeds the maximum, which constitutes a violation of *[the terms of service](https://www.infoblox.com/company/legal/bloxone-sandbox-supplemental-terms-and-conditions/)*.
- The consumption rate and usage within a subtenant account do not affect the subscription guardrails of the parent account.
- The Infoblox Platform does not create subtenants automatically, even if SANDBOX licenses are available. You must manually create and enable subtenant accounts before use. For details, see *[Creating subtenants](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/327811082)*.
- Only admin users have permission to create subtenants. After creating a subtenant, an admin can add users and configure settings, just as they would in a production environment. Admins in the parent account also have the ability to delete subtenants. However, admin privileges are not transferable between parent and subtenant accounts.
- All newly created subtenants are enabled by default. When enabled, your subtenants support all Infoblox Platform features and capabilities of the parent account.
- You must renew your SANDBOX license before it expires. Failure to renew the license will terminate access to the subtenant account, even if the parent subscription is still valid.

# Subtenants and NIOS-X Servers

- You can deploy NIOS-X servers and connect them to your subtenants, but you cannot reassign servers from one subtenant to another. You must create new servers for each subtenant.
- A subtenant is not a virtual machine. Therefore, you cannot install and test malware on it.
- For information about deploying a server, see *[Deploying NIOS-X Servers](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/204800163)*.

# Subtenant Data

- In the Infoblox Portal, all subtenants are separate accounts associated with the parent account. There is no data synchronization between a subtenant account and the production account. You can use the subtenant environment for non-production purposes.
- Data remains in the parent account and is not automatically copied to a subtenant. If you have multiple subtenants, each of them works independently of the others, based on its individual configurations.
- Data related to policies, configurations, and Infoblox Platform operations cannot be copied between the subtenant accounts.
- All newly created subtenants are enabled by default. You can disable a subtenant if you no longer need it.
- To retain the data of a subtenant you are about to delete, you must export the data as a CSV file and save the file for future importing purposes. For information about the import/export feature, see *[Importing and Exporting Data](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneCloud/pages/35396990)*.

For more information, see the following:

> Macro (children)