# Custom settings

Although the choice of registration workflow does not necessarily require changes to your Django settings (as registration workflows are selected by including the appropriate URL patterns in your root URLconf), the built-in workflows of django-registration make use of several custom settings.

`django.conf.settings.``ACCOUNT_ACTIVATION_DAYS`

  An `int` indicating how long (in days) after signup an account has in which to activate.

  This setting is required if using one of the built-in two-step workflows:

  - The two-step HMAC activation workflow

  - The model-based activation workflow

`django.conf.settings.``REGISTRATION_OPEN`

  A `bool` indicating whether registration of new accounts is currently permitted.

  A default of `True` is assumed when this setting is not supplied, so specifying it is optional unless you want to temporarily close registration (in which case, set it to `False`).

  Used by:

  - The two-step HMAC activation workflow

  - The simple one-step workflow

  - The model-based activation workflow

  Third-party workflows wishing to use an alternate method of determining whether registration is allowed should subclass `registration.views.RegistrationView` (or a subclass of it from an existing workflow) and override `registration_allowed()`.

`django.conf.settings.``REGISTRATION_SALT`

  A `str` used as an additional “salt” in the process of generating HMAC-signed activation keys.

  This setting is optional, and a default of `"registration"` will be used if not specified. The value of this setting does not need to be kept secret; see the note about this salt value and security for details.

  Used by:

  - The two-step HMAC activation workflow