Date: Fri, 29 Mar 2024 04:47:30 +0000 (UTC) Message-ID: <1249994623.7449.1711687650882@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7448_227666034.1711687650880" ------=_Part_7448_227666034.1711687650880 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Untracked Terms and Conditions can be rendered while completing a Petiti= on by placing them in the Petition Conclusion of an Enrollment Flow. There is no enforcement = of T&C (ie: the petitioner does not need to click anything other than t= he normal submit button) and there is no record kept of agreement.
This capability is not currently available (CO-925).
COmanage Registry can track agreement to Terms and Conditions for CO par= ticipants. In order to enable this feature, define Terms and Conditions via= Organizations >> CO >> Configuration >> Terms a= nd Conditions.
When defining Terms and Conditions, note the following fields:
Terms and Conditions at enrollment can be configured in several ways. Th= is configuration is available per-Enrollment Flow.
When an Enrollment Flow is configured for either Explicit Consent or Imp= lied Consent, the following constraints are applied:
T&C must be agreed to as part= of a separate step, suitable for both self-signup and invitation flo= ws.
Registry v= 4.0.0 and later support T&C for anonymous (unauthenticated) enrollments= . The petition's Enrollee Token will be used as the authenticated = identifier to allow for later (database level) audit, and the T&C Agree= ment will be correctly linked to the newly created CO Person record.
When an Enrollment Flow is configured for either Explicit Consent or Imp= lied Consent, the following constraints are applied:
T&C must be agreed to as part of Petitioner Attributes, meaning they= are primarily suitable for self-signup flows.
An already active CO Person can login to Registry and review Terms and C= onditions via the My Identity menu.
In addition, a CO can enforce agreement to Terms and Conditions at login= . This setting is enabled via CO Settings >> Terms and Conditions= Mode. Note that current agreements are retrieved at login but enforce= d when a CO-specific page is retrieved. Therefore, if this setting is chang= ed, currently logged in users will not be required to agree to pending Term= s and Conditions until their next login.
Only login to Registry is affected, not to applications that are integra= ted with COmanage. In a future release, it may be possible to disable acces= s to services until Terms and Conditions are agreed to (CO-928).=
Requiring Terms and Conditions at login applies to CO and COU administra= tors as well, and they will be required to agree to any pending T&C bef= ore accessing most Registry functions.
A CO Admin may agree to Terms and Conditions on behalf of a CO Person by= viewing the appropriate CO Person record and selecting Review Terms an= d Conditions.
The Terms and Conditions agreed to by individual CO People can be viewed= by retrieving the appropriate CO Person record and selecting Review Te= rms and Conditions.
Reporting capabilities are planned (CO-701).
If a tracked Terms and Conditions is edited (changing the URL, the descr= iption, etc), existing T&C Agreements will be considered valid, though = as of Registry v2.0.0 the existing agreements will point to the original de= finition.
To change Terms and Conditions in such a way as to require everyone to a= gree to them, create a new Terms and Conditions entry.