Using AyMINE for a public client

A public client is a special type of account designed for organizations like churches and unions.

• What is a public client
• Data protection within a public client
  • Public client and GDPR
• Technical Recommendation: Settings for public client
  • Settings for communication in accordance with GDPR
  • Setting up a branch / congregation
• Setting up public distribution lists
• Super-Administrator Settings

What is a public client

It is a special type of client where users are not from the same organization and generally do not know each other.

• Associations with separate clubs or branches that operate mostly independently (sports associations, junák, etc.)
• Non-profit organizations with separate district units (like Diaconia, Hope, People in Need)
• Churches where individual churches and groups have their members but personal data outside the churches is not shared

Data protection within a public client

For a public client, the role of administrator is divided into two separate roles.

• Superadministrator who can manage groups and all users
• Administrator of one group who can only manage areas and directories within his group

Public client and GDPR

The public client is prepared to fully comply with GDPR requirements.

Within the system administration for public clients, the following apply:

• Users see only those users with whom they are in a common group.
• Users can't get rights to keep track of all activities
• A public client has separate administrators for separate groups who cannot give themselves rights going beyond their space.

Technical Recommendation: Settings for public client

(The next text is intended for system administrators)

Settings for communication in accordance with GDPR

• Account must have established email address
• The account must have an address set to a page with information on the protection of personal data and its management. You can create the page directly in AyMINE, or link to the organization's website.
• A directory with contacts visible to users of all branches can be created. (It is not necessary, shared contacts can also be in the directories of branches or congregations)

Setting up a branch / congregation

Each branch

• Has its own directory with contacts visible only within the branch
• Has created groups of addressees for internal communication
• May have groups to communicate with the public
• Must have at least 1 internal account manager. This user can see all users and contacts within the branch/congregation directories and can fully manage them. It can open and close user accounts with access within a branch.

Setting up public distribution lists

The public distribution list allows people to manage what information they want to receive independently and in accordance with the GDPR. You can provide different information channels and users choose which ones to subscribe to. Information is always sent along with a link where they can change their settings.
Correct settings

• A specific directory is always used for public communication. It must have completed public data.
• Individual information channels are entered as contact groups. In order to be public, a group must have public data (name and description).
• In addition to public groups, it is possible to have non-public groups - it is not possible to use a mass message, or to subscribe to them publicly or unsubscribe from them
• Each section or congregation may have its own distribution lists. Information seekers see the information channels that are made available to them. They may be from other congregations, headquarters or the seinorate (depending on the type of user).

Super-Administrator Settings

Super public client administrator have rights

• external communications` (to be able to configure email gateways)
• publicCompAdmin to see configured gateways
• CRM plugin administrator - to be able to create directories
• sysAdmin User administrator to be able to create new local administrators

Permissions must be set by the system administrator because within the public client it does not have the ability to grant higher rights than it has.

Caution: The only way to add a role to the system administrator is to do so.

1. Open a client in system administration
2. Find a super client administrator on the users tab and open a detail
3. On the role and group tab, add the necessary role with the privileges.

No other path allows the administrator to add privileges to users of other clients.