public: Everything is publicly accessible.
restricted: The IDP components use the same authorization scheme as the main LDP component. For example, if the server uses WebACL authorization and the registration endpoint is /idp/register/, access to registration can be restricted by creating a valid /idp/register/.acl resource. WARNING: This setting will write the necessary resources to the .well-known and IDP containers to make this work. Again in the case of WebACL, this means ACL resources allowing full control access. So make sure to update those two containers so only the correct credentials have the correct rights.

Email

Necessary for sending e-mail when using IDP.

default: Disables e-mail functionality.
example: An example of what your e-mail configuration should look like. In that case you should not import anything from this folder but have the settings in your root config.

Handler

Contains everything needed for setting up the Identity Provider.

default: As of writing there is not much customization possible. This contains everything needed.

Which technique to use to determine if a requesting agent owns a WebID.

What to use for pod creation.

dynamic: Every created pod has its own Components.js config for its ResourceStore, which can differ from the others.
static: All pod data is stored in separate containers in the same ResourceStore.

If users should be able to register on the server.