Considerations for administering access to ACDs

Last Updated : Aug 12, 2024 |

Consider the following when working with ACD access permissions:

  • By default, a newly-created user is granted Read, Write, and Exceptions permissions for all ACDs.

  • When you create a tenant user, they only have access to selected login ACD by default. As an administrator, you can give the tenant user access to another ACD if required.

  • User permissions for ACD access are stored separately from the user ID created on the User Data page. Therefore, ACD permissions can be deleted and modified without affecting the state of the user ID.

  • If the ACD permissions for a user are changed, the change does not take effect until the user logs out and logs back in again.

  • Users can only access features on an ACD for which they have permissions. If you disable a user's Read and Write permissions, then the user cannot access any splits/skills, trunk groups, vectors, or VDNs in that ACD. If Read is enabled and Write is disabled, the user can view but cannot modify splits/skills, trunk groups, vectors, or VDNs in that ACD.

  • In some instances, you might need to restrict a user from viewing information on an ACD. You can modify the user's ACD permissions or delete the user's ACD permissions definition. Deleting the permissions definition does not restrict the permissions for the user, but actually deletes the user from the specified ACD.

  • If the permissions for a user's default login ACD are removed, the user must have another login ACD assigned.