Administration/Membership/Achievements:

- Possibility of assigning one achievement to many age groups - As a system administrator I am be able to assign few age groups to one achievement to avoid duplicated achievements.

 

Public registration link:

- Each unit can generate a unique URL which will allow to register to this unit without adding any data to the system by admin earlier

Administration/Membership/Units/Edit action

- a new checkbox: Registration via public registration link

Administration/Settings/Unit data:

 - Registration requests tab - possible to ticked/unticked checkbox  (ticked checkbox - Pending members (Read only) - displayed for all members (without permission))

Administration/Settings/User roles:

- new permissions related to Public registration links & approval processes

Administration/Settings/Email/new email type (Sending to requester)

                - Confirmation of registration

                - Information about account approval

                - Information about account rejection

Administration/Settings/Notifications: new notifications

                - A new membership request is pending approval.

New form for registrations via public URL

User Profile (user with account and role)/Notifications tab:

                -  added a new notification 'New Registration requests''

                - Preserved the logic as it exists for the existing notification

                - Notifications are sending by a frequency

Unit Profile/Settings tab:

                - Added a new section under Settings tabs (available by the permissions and general settings in the administration)

                - Switch button for enable/disable registration link --> Confirmation popup windows

                - Enabled: option to view & copy the link

 

Settings are unique for each Unit in the system separately

Unit Profile/Registration requests:

                - List of all members registered by using the link (successfully send form)

                - Shows only members from current unit - not including subunits

                - all member data listed in pending member details

                - option to accept or decline the member (bulk or individual)

                               - Accept action:

                              a confirmation window if the user is sure that he wants to approve registrations

                                               If an admin approve the pending member/s (who sent the form without creating a teepee account:

                                                               - pending member is no more displayed in the Pending members tab,

                                                               - but will be displayed in the list of members (Members tab)

                                                               - the correct email is sent (Information about account approval)

                                               If an admin approve the pending member/s (who sent the form with creating a tipi account):

                                                               - pending member is no more displayed in the Pending members tab,

                                                               - but will be displayed in the list of members (Members tab), and Users (Users tab)

                                                               - The correct emails are sent (Information about account approval + activation teepee account link)

                               - Decline action:

                                               a confirmation window if the user is sure that he wants to reject registrations.

                                               warning, that declined members are permanently deleted

                                               optional reason field for declining operation (with warning that this message will be visible in the notification email)

-----------------------------------

 

Person Profile:

- possibility to invite members only to agree on GDPR consents and fill data after member creation - a new Resend form action

 

Person Profile:

  • - GDPR:
    • Consents divided: Consents & Declarations
    • A new Section: Declarations:
      • implemented the same logic as for consents (e.g. person with age < min. system age)
      • Declarations set for NS persons - implemented the same logic as for consents
      • Person Declarations – list of all read Declarations
        • Information: Read by, Read date
        • not possible to uncheck checkbox
      • Available Declarations – list of all unread Declarations (active only)
      • Deleted declarations – no more displayed
    • GDPR tab/Export – added information about read declarations

Reports Module/Persons:

  • ‘’Person Activity’’ columns:
    • o a new column: Read Declarations – list of the all read declarations + dates (active & also inactive)
    • o a new column: Unread Declarations – list of the all unread declarations (active only)
    • o Note: Deleted declarations – no more displayed
  • Membership colum divided to: Membership and Primary memberchip columns

Forms:

  • - Declarations –
    • implemented the same logic as for consents (e.g. person with age < min. system age, NS status, type of form, Required Declarations). Example:
    • Only Active Declarations (or already active read declarations) are available in the form
    • Declaration info from the form: Read by & Dates are saved in the person profile/GDPR section successfully

Login:

  • not possible to continue to the system without read (granding) required declarations:
    • implemented the same logic as for consents (list of all active required unread declarations will be displayed - by the person type (e.g. NS, age), Person with age < min. system age are not allowed to read declarations..)

 

Administration:

  • Administration/ Settings /Consents:
    • Consents section – two types: Consents  (preserved) &   Declarations
    • Declarations type:
      • possible to add a new declaration, edit existing
      • possible to delete declaration in used (displayed dialog window with info)
      • implemented the same logic as for consents ( possible to set Active/Inactive > = < min.syst. age, For NS, Required/Optional, define text).

Inactive Declarations are marked grey in the list