The Experience Portal web console displays the Roles page in the User Management tab. On the Roles page, you can add the roles specific to Avaya Proactive Outreach Manager (POM) and change or delete a custom role. You can use the Experience Portal Management System (EPM) interface to add, change, and delete user accounts. You can assign various roles and privileges to different users and specify the security options for all users. EPM can optionally gain access to the user accounts in your corporate directory, with the parameters you configure from the Lightweight Directory Access Protocol (LDAP) settings. For more information about EPM, see Administering Avaya Experience Portal.
On the Roles page, you can view the following POM-specific roles:
POM Administration: User accounts with POM Administration access can administer the functioning of POM through Experience Portal.
POM Campaign Manager: User accounts with POM Campaign Manager access can manage the different campaigns created. With this user role, you can create, edit, and delete campaigns in POM.
POM Supervisor: By default, a user with a supervisor role has access to Supervisor Dashboard. The supervisors can see and manage only the agents that are assigned to them if you enable the Agent and supervisor configuration on the Global Configurations page. The supervisors can also see and manage the campaigns of the organization to which they belong if multitenancy Organizations is enabled on Experience Portal.
POM Contact Attributes Unmask: A user with this role can unmask contact attributes.
For information about the fields on the Roles page, see Avaya Experience Portal Documentation library or use the context sensitive Help button at the top-right corner of the screen.
Note:
Org POM Campaign Manager and Org POM Supervisor roles are visible only if you enable multitenancy.
Important:
If you have a global administration role, ensure that you do not make changes to any other elements such as campaigns, contact lists, campaign strategies, and agent scripts that belong to an organization.
Important:
As POM uses the name default for its internal usage, an administrator should not create an organization in the Experience Portal with the name default.