Tenant management overview

A tenant in BMC Cloud Lifecycle Management can be a company, organization, or any other group of users. The use of tenants in the cloud allows a company or service provider to segregate companies or organizations in the cloud, and to control the visibility of and permissions to offerings in the Service Catalog.

The cloud administrator must create at least one tenant in the BMC Remedy IT Service Management Application Administration Console. After the tenants have been created, they can be onboarded to BMC Cloud Lifecycle Management, and associated with entitlement packages that determine the set of service offerings available to those tenants. For users at the service-provider company to request services, the service-provider company itself must be onboarded as a tenant.

The cloud administrator can map tenants to network containers, ensuring that some network resources (and the compute resource pools associated to them) are available only to certain tenants.

• Service-provider model — Tenants are individual users or corporate entities that require end-to-end separation. Each tenant gets one or more dedicated networks containers, and each network container has a dedicated set of resources for service hosting. The cloud administrator assigns network containers to tenants when tenants are on-boarded into the cloud.
• Enterprise model — Tenants are organizations or business units within the enterprise. Network containers are shared between one or more tenants, and resources can be shared between multiple network containers.
• Hybrid model — Tenants can share network containers, but segregation between tenants is not required. For example, some service providers might offer shared commodity hosting and dedicated premium hosting based on different service levels. Some enterprises might isolate certain applications in production.

For more information about managing tenants, see Managing tenants. For more information about entitlement packages, see Entitlement packages overview.