Introduction

The Member Usage Compliance feature allows communities to ask members, as they sign into the product, a question that must be answered before proceeding into the community. This feature is intended to support communities that have policies around when members are allowed to access the platform. 

For example, a company could decide that members of a certain target, such as hourly workers, should only access the platform when they are "on the clock". To enforce this policy, the company could set up a Member Usage Compliance flow where members who have been assigned to certain targets get asked, upon sign in, whether they are currently working on company time or not. If they say "no", then they cannot use the application. If they say "yes", then they can proceed to the rest of the application. 

The steps to enable Member Usage Compliance are:

1. Talk to your Customer Success Manager to see if Member Usage Compliance is a good solution to your compliance needs. If so, they can help to enable and configure it.
2. Decide the parameters of your compliance policy, such as which members need to have this type of messaging, and what the messaging should say.
3. Collaborate with your Customer Success Manager to enter the information into the Member Usage Compliance page in the manager app, and turn it on.

Configuring Member Usage Compliance

This feature is not enabled by default. If you are thinking of using this feature, make sure to contact your Customer Success Manager so that you can run through how you plan on using this feature. 

Once this feature is enabled, a link will show up in the manager app under Admin→Internal→Member Compliance which will be visible to internal Admins such as Customer Success however it will not be visible to customers. On this page, there are four sections.

Screenshot of Member Usage Compliance Settings Page, with the first two sections

First, there is a checkbox control to enable this feature. It defaults to unchecked. Once all the settings are correct, the Customer Success Manager can check this box, and the Member Usage Compliance feature will start controlling access immediately. 

Second, there are settings for the "Gate Page". The role of the Gate is that members, if they are in the target that this feature is controlling, has a gate (in the form of a dialog box) in front of their access to the platform, and that they must answer a question correctly in order to pass through the gate. As a member, this appears as a dialog box with a title, body text, and two buttons - one for agreeing (and passing on to the platform) and one for declining (at which point the member would see another dialog, as configured in the decline section). 

Example Gate Dialog Box as it appears to a member

The settings available for the Gate dialog are:

• Gate Title: Sets the title of the Gate dialog box
• Gate Body: Sets the text in the dialog box. This should explain what the company's policy is, and ask whether the member is complying with the policy when they are trying to use the DySi platform. This text can include a link, and the link can be used to link to more detailed policy information, such as an employee handbook.
• Agree button: Sets the title of the button that, when clicked or taps, indicates that the member is complying with the policy. If a member clicks or taps this button, then they proceed to the member app.
• Decline button: Sets the title of the button that, when clicked or taps, indicates that the member is not complying with the policy. If a member clicks or taps this button, then they proceed to the Decline dialog, and cannot use the platform.

Screenshot of Member Usage Compliance Settings Page, with the final two sections

Third, there are settings for the "Decline Page". A member would see this page if they clicked or tapped on the decline button from the Gate dialog. 

The settings for the "Decline Page" are:

• Decline Title: Sets the title of Decline page. 
• Decline Body: Sets the body text of the decline page, and should be used as an explanation as to why they are not permitted to access the member app.
• Try Again Button: Sets the text of a button, which if tapped, brings the member back to the Gate dialog. The intention is that a member may have misread the instructions and tapped the wrong button. If so, that member can go back and answer a different way. 

Example Decline Dialog Box as it appears to a member

Fourth, there is a settings section which defines which members are subject to this compliance feature, and for how long their agreement lasts:

• Session Length: Defines the interval for which their agreement is valid. For example, if the session length is set for thirty minutes, then the member will be asked about compliance the first time they open the app, and then every thirty minutes thereafter.
• Access: Defines the audience to which this compliance feature applies. If Everyone is selected, then all users will receive the message, regardless of any grouping. If Targets is selected, members that meet the target requirements will receive the message. The logic for targets works the same as it does when creating posts: OR-Logic within a Target and AND-logic across Targets. 

Notes

• For migrated customers, if there are no Targets enabled for a community, then the compliance message will default to “Everyone” when enabled.  
• This feature is translatable - after the English version is set up, click on the globe icon in the upper right corner to translate the applicable fields to different languages 
• This feature works on the member apps: Web, iOS, and Android, but does not impact access to the manager app
• All interactions are recorded in an audit log