Wiki source code of Release 2020-04-27
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | This release brings many new features and some bug fixes to the Collaboratory 2. | ||
| 2 | |||
| 3 | New features: | ||
| 4 | |||
| 5 | * SGA3 unit structure: | ||
| 6 | ** get accredited for SGA3 by requesting membership unit corresponding to the tasks you work in. | ||
| 7 | ** users are also automatically added to the unit of their institution according to their email address. | ||
| 8 | * Group app: | ||
| 9 | ** 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). | ||
| 10 | ** Group creation is limited to users with a need for group management. Contact [[support>>mailto:support@ebrains.eu]] to request the ability to create groups. | ||
| 11 | * User registration directly in Collaboratory 2: | ||
| 12 | ** activation of this feature is pending approval of the EBRAINS Access Policy by the HBP Directorate. | ||
| 13 | ** external users can create their own account directly in the Collaboratory 2, which will spawn a creation of account in Collaboratory 1 too | ||
| 14 | ** external users with a valid institutional email address will have their account in Collaboratory 2 created automatically at first login. | ||
| 15 | ** invitations to external users to create an account in the Collaboratory 1 will be deactivated. | ||
| 16 | ** 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). | ||
| 17 | * Notification banners: | ||
| 18 | ** the banners warning users of important status information are available through all the Collaboratory 2. | ||
| 19 | |||
| 20 | Bug fixes: | ||
| 21 | |||
| 22 | * Notification settings are available again. | ||
| 23 | |||
| 24 | Policy changes: | ||
| 25 | |||
| 26 | * User registration: new users can register directly on the Collaboratory 2. | ||
| 27 | * Institutional email addresses: users must register with their institutional email or follow the EBRAINS Access Policy procedure. | ||
| 28 | * Email validation: the email will be validated periodically at time of login (currently set at every 3 months). | ||
| 29 | * Username policy: usernames must consist of letters and numbers only. | ||
| 30 | |||
| 31 |