Resolves issue #542 — Now, centers who want to have a more thorough process for users on allocations whose resources have a 'eula' attribute can set the config variable EULA_AGREEMENT to True. With this, when a user is added to an allocation with a EULA resource, any user that is added (who is not an admin or a PI) has a status of Pending instead of Active. When this user goes to access the resource, they must either accept or decline the EULA. If they accept, they become an Active user on the allocation. However, if they decline, their status is set to Declined.
In addition, when a user is added to an allocation with a EULA resource, they receive an email asking them to complete the EULA. When a user agrees to the EULA, an email is sent to the user and their manager to confirm this process. If the config variable EMAIL_EULA_REMINDERS is set to True, users are emailed weekly to remind them to complete their EULA process.
Resolves issue #542 — Now, centers who want to have a more thorough process for users on allocations whose resources have a 'eula' attribute can set the config variable
EULA_AGREEMENT
to True. With this, when a user is added to an allocation with a EULA resource, any user that is added (who is not an admin or a PI) has a status ofPending
instead ofActive
. When this user goes to access the resource, they must either accept or decline the EULA. If they accept, they become anActive
user on the allocation. However, if they decline, their status is set toDeclined
.In addition, when a user is added to an allocation with a EULA resource, they receive an email asking them to complete the EULA. When a user agrees to the EULA, an email is sent to the user and their manager to confirm this process. If the config variable
EMAIL_EULA_REMINDERS
is set to True, users are emailed weekly to remind them to complete their EULA process.