Label User and Group items that are for system use

[cbunicef]

As an ADMINISTRATOR I want to have a full understanding of my platform.

Typically Users correspond to individual people logging in and using the platform, and Groups correspond to Groups of people with certain permissions on the platform.

IoGT is now using the User/Group model to facilitate new functions:

• connection of RapidPro to IoGT
• notifications for users

These new use cases aren't related to actual people's permissions on the platforms, so it would be good to label them separately.

Can we please label User and Groups we're creating for purely system functions, eg RapidPro, as "SYSTEM_[name]"? No need to fix this on current platforms as a priority, but let's discuss the necessary steps to get there. And let's implement new features in this way.

And can we please label any Group automatically created for notifications as "NOTIFICATIONS_[name]"? Understanding that we also expect administrators to create Groups themselves for notifications this can also be a best practice for the admins. To help this along, can we add this in text in the "add user to Group" content block:

This content block will add or remove any User that arrives on this Page from the Group selected. This can be used for many purposes, for example:

• adding a User to the "Health Workers" Group after they enter a password and arrive on a protected Page
• adding a User to the "NOTIFICATIONS_Health Workers" Group after they click a link on another Page indicating their interest in subscribing

Notifications Groups should always be separate from Groups used for permissions, in this example "Health Workers" and "NOTIFICATIONS_Health Workers". This will allow Users to unsubscribe from Notifications without leaving the Group that you use to manage their access.

[cbunicef]

@ChrisMarsh82 @istride as we work through the current features let's keep this in mind. No need to urgently change the RapidPro connection behavior.