Failed to execute template. Cause: [Access denied when checking [script] access to [xwiki:Collaboratory.UX.HbpSkin.WebHome] for user [xwiki:XWiki.Admin]]. Click on this message for details.

Release 2020-04-27 - HBP Wiki

IAM21 instance, do not create collab nor modify a team, your changes will be lost


Release 2020-04-27

Last modified by hbpadmin on 2023/05/15 15:08

This release brings many new features and some bug fixes to the Collaboratory 2.

New features:

  • SGA3 unit structure:
    • get accredited for SGA3 by requesting membership unit corresponding to the tasks you work in.
    • users are also automatically added to the unit of their institution according to their email address.
  • Group app:
    • manage groups of users for granting permissions, e.g. to a collab 's team (if you're a collab admin) or to a service (if you're a service developer).
    • Group creation is limited to users with a need for group management. Contact support to request the ability to create groups.
  • User registration directly in Collaboratory 2:
    • activation of this feature is pending approval of the EBRAINS Access Policy by the HBP Directorate.
    • external users can create their own account directly in the Collaboratory 2, which will spawn a creation of account in Collaboratory 1 too
    • external users with a valid institutional email address will have their account in Collaboratory 2 created automatically at first login.
    • invitations to external users to create an account in the Collaboratory 1 will be deactivated.
    • HBP members who don't yet have an account will go through the same flow as external users, and will then need to request SGA3 accreditation (see above).
  • Notification banners:
    • the banners warning users of important status information are available through all the Collaboratory 2.

Bug fixes:

  • Notification settings are available again.

Policy changes:

  • User registration: new users can register directly on the Collaboratory 2.
  • Institutional email addresses: users must register with their institutional email or follow the EBRAINS Access Policy procedure.
  • Email validation: the email will be validated periodically at time of login (currently set at every 3 months).
  • Username policy: usernames must consist of letters and numbers only.