Working with Groups, IP Domains, and Tenants in CA Performance Center › What are IP Domains? › Using IP Domains as Permission Groups

Using IP Domains as Permission Groups

As a best practice, add IP domains to user accounts to let users see the items in the domains. Permission to see an item in an IP domain automatically grants access to all other items in that domain. You do not need to grant explicit permission for each item in an IP domain. Similarly, do not add the All VoIP Locations domain to user permissions in a multiple-domain environment. Doing so implicitly grants that user access to data from all IP domains.

Another best practice is to grant the administrator permission to see all IP domains. This action simplifies IP domain administration. For example, the administrator can see IP domain identifiers for all collectors, Locations, call servers, and voice gateways. By contrast, individual users only need access to one IP domain.

Avaya trunk groups do not have IP domain identifiers. As a result, they are not included when you add IP domains to user account permissions. Instead, you add Avaya trunk groups as individual permission groups. Locations, media devices, and call servers are managed items, with IP domain identifiers based on your collector configuration. Avaya trunk groups are treated as groups in CA Performance Center, and groups do not have IP domain identifiers.