Audiences and Users in the Compliance Interface

• You must create new audiences and create new users in Percipio. You cannot create an audience or user in the Compliance admin interface.
• All audiences and users available in Percipio are also available in the Compliance admin interface except for those created via team automation.
• User attributes, user accounts and audience data between Percipio and the Compliance admin interface is synchronized nightly. near real time. See Sync Percipio Data for more information about data sync timing.
• Newly created users are available in the Compliance admin interface after the nightly sync or when the user logs into Percipio.
• The UserID in the Compliance admin interface is populated based on what is in the login name field in Percipio. If nothing is in login name, it uses what is in the external user ID, and if nothing in the external user ID, then is uses the Percipio ID.
• In the Compliance admin interface, audiences are referred to as Demographic Groups and appear under the Demographic Groups tab.
• User attributes for users are visible in the Compliance admin interface. Changes to user attributes appear in the Compliance admin interface after the nightly sync.
• You can delete audiences created for Compliance content as long as no content is entitled or assigned to the audience.
• Your users can only access the Percipio Compliance page if they have pending assignments, or if they have a history of Compliance content.
• Learners with access to only Compliance content will see only the Percipio Compliance page.
• By default, Percipio user roles align to Compliance security levels. If you make changes to a user's role after the initial creation, the Compliance admin interface does not automatically update the security level to reflect the change. You can manually update the security level for that user within the Compliance interface.
• If you create one or more custom roles, Percipio aligns each custom role to the security level given to the learning admin role.
• Users who are not associated with a license pool, and only have access to Compliance, are not prompted to specify security questions.
• If a change in user attributes causes a learner to be removed from an audience that has a course assignment, and that learner has started but not completed the course, the learner's progress will be lost. This is true even if the user gets added to a different audience with that same course assignment.
• If a change in user attributes causes a learner to be removed from an audience that has a Learning Program assignment, and that learner has not completed the entire Learning Program, the learner loses all progress for all courses within the Learning Program. This is true even if the user gets added to a different audience with that same Learning Program assignment. Before making changes that impact compliance audiences, run the Learning Program report so you have a record of learner progress.
• When using a custom user attribute in Percipio that is allowed to store multiple values and that attribute is mapped into the supervisor email or user-specific data fields in compliance:
• If multiple values are stored in a custom user attribute on the Percipio side, the mapping only takes the first one in the list.
• If you are updating an existing user, and the current value in the Compliance admin interface matches one of the values in Percipio, the current value is retained.
• If you are updating an existing user, and the current value in the Compliance admin interface doesn't match any one of the values in Percipio, the existing Compliance value is overwritten with the first value sent from Percipio.

See the Compliance Knowledge Base for more information.