Creating the Field
Once you've created articles for each of your fields, it's time to create the fields themselves. If you have a lot of terms, you may want to consider the organization of terms as they are displayed to users. If you don't create field groups, you may end up with all of your terms fields bunched together in an automatic field group named "Fields", which might be confusing to users.
Before creating the field, create the group where your related TOS fields will be displayed together (otherwise they end up in an automatic group called "Fields" which doesn't look very good). On this site, the terms are all children of the "Terms" group - it's simple, but effective and clear. For the purposes of this instruction, I will assume that you took that advice and want to create a "Terms" field group, so that is where we will begin. The name of the group isn't set in stone - you can name it anything you like, and you can have as many as you need to organize your terms logically.
Browse to Users > Field Groups
Create a new Group, name it "Terms"
Browse to Users > Fields
Create a new field. The label should be (as described on a previous page, and in Citation 42 of the GDPR) a simple description of the consent you wish to receive. If it's longer than a sentence, it is too long. Keep it simple, use the terms document to explain further if necessary. I like to make my title and labels match, so they are easily identifiable in the fields listing.
Select "Terms of Service" as the type. When the page refreshes, change the "Required" setting to "Yes" - this is important for configuration of the System - Required Fields plugin.
At the bottom, select the terms article you created previously.
To the right, choose the appropriate "Field Group" - if you're following this guide closely, that group will be named "Terms"
When finished, it should look like this:
Click "Save" (do not close it, we aren't done yet)
After saving, the "Name" field should auto-populate. Our last configuration is on the "Permissions" tab.
In Permissions, change the Public > Edit Custom Field Value setting to "Allow". Your screen should look like this:
Now you can "Save and Close" this field.
This is not quite the end of our configuration for this field. This field will be displayed and required for users at registration, but if you add new terms - the user will not be required to agree unless they edit their profile. To resolve this issue, the configuration of this field continues with the installation and configuration of the System - Required Fields plugin.
* One of the first GDPR Bundle subscribers pointed out that the "Public - Edit Custom Field Value" permissions can be set on the field group. If you make this setting on the field group, any field in that group inherits the permission. If you choose to go this route, you can skip the permission step on the creation of each field. - Thanks for the tip Michele!