Root folder where user credential files will be stored. Note that each Host will have a subfolder with the name of Host where the actual credentials are stored.
A credentials file is encrypted using keys that have been generated for each installation as part of the setup (see Creating the First Extension). Each credential file is named after the signed-in user identity which is a formal field/variable named "userName" (not the host userid). This is the user's email address in many identity frameworks such as Google Sign-in or SAML 2.0 for Okta, Salesforce and Active Directory Federation Services, or the fully qualified ID if using Windows Security (Domain/UserID).
For environments where a single userName may have multiple HostID's the connection can specify a "userHostID" FieldName/variable which will add an additional suffix to the base name appended with an underscore. If different text values are to be used than the HostID for a unique credential name, the "userQualifier" FieldName/variable can also be specified.
While the root of the credentials file is the User's Identity [_userHostID], the extension is .cred for credentials.