/mcpA P P E N D I X C Tenant Partitioning • Understanding Tenant, on page 335 • Tenant Provisioning using APIs, on page 335 • Working with Tenant Partitioning, on page 336 • Modifying the Objects after Tenant Creation, on page 337 Understanding Tenant Each tenant has its own set of partition, schedule set, schedule, schedule detail, search space, search space member, phone system, class of service, user template, distribution list, distribution list membership, user operator, call handler template, directory handler, interview handler, call handlers (Operator, Opening Greeting, Goodbye), and routing rules. The configuration objects are shared across multiple tenants such as, all the system settings like mailbox store, custom keypad, restriction tables etc. are shared across the multiple tenants. Tenant partitioning also introduces the concept of using the corporate email addresses as their alias, which enables alias uniqueness across tenants. To achieve this, the aliases assigned to the users (in multi-tenancy environment) must be in the form of alias@smtpdomain, which would be the corporate email address of the tenant's user. To login into the Unity Connection Web interfaces like Cisco PCA, Web Inbox, VMREST API, users have to use this alias format. Two different tenants configured on the same Unity Connection can never have the same alias for the users as the smtp domain always differ. There are no changes done for touchtone conversation and voice-recognition users. Note Tenant Provisioning using APIs Cisco Unity Connection Provisioning Interface (CUPI) provides set of APIs for Unity Connection that can be used for tenant provisioning. To support the Tenant Partitioning feature using APIs in Unity Connection, few new APIs have been developed and few existing APIs have been modified. • For more information about provisioning APIs, see the documentation wiki: http://docwiki.cisco.com/ wiki/Cisco_Unity_Connection_Provisioning_Interface_%28CUPI%29_API System Administration Guide 335