Text & links

Text

You can customize the default user acceptance text: Terms and policy text in Hosted Login

Text customization is easy to do using Registration Builder in the Identity Cloud Console. Follow the general step-by-step instructions for updating text in the Hosted Login guide: Text

Registration screen

For the registration screen, the field to update in Registration Builder is named: textAcceptanceBlurb textAcceptanceBlurb in Console

The same text field is used on the following two screens:

  • traditionalRegistration
  • socialRegistration

This means you can update this text once in Registration Builder, and that update will be reflected in both places.

Updated terms screen

The screen displayed to users when they need to accept a new version of the legal agreement(s) is called the authRule_acceptLegal screen: Re-acceptance screen in Hosted Login

The field to update in Registration Builder for the text on this screen is named: textAuthRuleLegalAcceptanceValue textAuthRuleLegalAcceptanceValue in Console

Additional text you may want to customize on the authRule_acceptLegal screen:

  • textAuthRuleLegalAcceptanceHeading - The heading text. Default value is: We’ve Updated Our Terms of Service
  • textAuthRuleLegalAcceptanceSubmit - The button text. Default value is: Continue

By default, there are two links presented to the user which indicate what legal agreements they are accepting. These links are non-functional by default, and must be updated to point to your current legal text. Your legal text is hosted and maintained by you. Terms and policy text in Hosted Login

As a result, when a user clicks either one of these links, a separate tab will open in their browser and they will be taken to a page on your site to read your legal terms or policy.

To update these two links, follow the general step-by-step instructions in the Hosted Login guide: Links

The same links are used on the following three screens:

  • traditionalRegistration
  • socialRegistration
  • authRule_acceptLegal

This means you can update a link once, and that update will be reflected in all three places.

To remove either of the default links, simply delete it from the text. See the Text section above.

  • For example, here’s the textAcceptanceBlurb value updated to remove one of the two default links:
    By clicking "{* textCreateAccount *}", you agree to accept our {* linkTermsOfService *}.
    

To add a new link, you’ll want to follow a three-step process:

  1. Create a translatable key for the link text (example: “cookie policy”). You can create a new key via the Configuration API /translations endpoint.

    Details

  2. Create a new link, which includes your key from step one. You can create a new link via the Configuration API /links endpoint.

    Details

  3. Add the new link into the screen text using the same format as the existing links. See the Text section above.

    • For example, here’s the textAcceptanceBlurb text updated to include a new link you created called linkCookiePolicy:
      By clicking "{* textCreateAccount *}", you agree to accept our {* linkTermsOfService *}, our {* linkPrivacyPolicy *}, and our {* linkCookiePolicy *}.
      

Adding a link here is only a UI update. This will NOT change what is written to the user record. If you would like an additional object to be written to the user record for the additional policy accepted, see Customize the schema.