Skip to Content
DocsDashboardSettingsRegistration Settings

Registration Settings

The Registration Settings page controls how new users join your QuickBox Pro server. Choose an activation mode, set default disk quotas, assign a default group, define username and password policies, and configure the welcome email. The page is organized into six sections, each accessible via sidebar dot-navigation.

Admin only

Registration Settings requires admin privileges (admin.settings.read to view, admin.settings.update to modify). Navigate to Settings > Registration from the sidebar.

Registration feature flag

For the registration page to be accessible to new users, registration must also be enabled via the Registration feature flag in General Settings > Feature Flags.


Sections overview

🔑 Activation

Choose how new registrations are verified — instantly, via email, by admin approval, or disabled entirely

💾 Quotas

Set the default disk quota assigned to every new user when they register

👥 Default Group

Choose which user group new registrations are automatically assigned to

📝 Username Policy

Define allowed characters, length limits, and validation patterns for usernames

🔒 Password Policy

Set minimum length and complexity requirements for user passwords

📧 Welcome Email

Enable or disable the welcome email sent to new users upon registration


Activation

Choose one of four activation modes that determine what happens after a user submits the registration form:

ModeHow it works
No Activation
Users can log in immediately after registering. No verification step
Email Activation
Users receive a verification email and must click the activation link before they can log in. Requires email to be configured
Admin Approval
Registrations are held in a pending queue. An admin must manually approve each user before they can log in
Disabled
Registration is completely blocked. New users can only be created by an admin through the User Admin page

Admin approval workflow

When using Admin Approval mode, pending registrations appear in the User Admin page. Admins can approve or reject each registration individually.


Quotas

Set the default disk quota that is automatically assigned to every new user:

  • Default quota — The disk space limit assigned to new users. Choose a value in MB, GB, or TB, or select Unlimited for no quota
  • Quotas can be changed per-user after registration via the User Admin page or the CLI with qb user quota -u <username> -o <size>

Default group

Select which user group new registrations are automatically assigned to. When a new user registers (or is approved through the registration queue), they are placed into this group, which determines their initial application access.

  • Group selection — A dropdown lists all available groups. Choose the group that matches the level of application access you want new users to start with
  • The Administrator group cannot be selected as the default registration group
  • The default group defaults to the Access group, which provides access to download clients only

Syncs with User Groups

This setting is shared with the User Groups page. Changing the default group here automatically reflects on the User Groups page, and vice versa. Both pages read and write the same underlying configuration.

Group membership after registration

The default group only applies at registration time. After a user is created, their group membership can be changed from the User Admin page. A user can belong to multiple groups, and their effective application access is the union of all their groups’ permissions.


Username policy

Define the rules that usernames must follow when new users register:

  • Character restrictions — Choose from preset validation patterns or create a custom regex pattern:
PresetAllowed Characters
Recommended
Lowercase letters, numbers, hyphens, and underscores. Must start with a letter
Strict
Lowercase letters and numbers only. Must start with a letter
Permissive
Lowercase letters, numbers, dots, hyphens, and underscores. Must start with a letter
Custom
Define your own regex pattern using the visual regex builder
  • Minimum length — The minimum number of characters required
  • Maximum length — The maximum number of characters allowed
  • Lowercase enforcement — When enabled, usernames are automatically converted to lowercase

The visual regex builder provides a graphical interface for constructing custom username validation patterns without writing regex manually. Select character classes, set anchors, and preview matches in real time.

Shared policy

The username policy is enforced consistently across the dashboard and the CLI. Both systems read the same configuration, so users created via qb user create follow the same rules as users who register through the dashboard.


Password policy

Set the requirements that passwords must meet:

  • Minimum length — The minimum number of characters required for a password
  • Complexity requirements — Enforce rules such as requiring uppercase letters, lowercase letters, numbers, or special characters

The registration form includes a strength meter that provides real-time feedback as users type their password, helping them meet the requirements.


Welcome email

Configure whether new users receive an email when their registration is completed:

  • Enable welcome email — Toggle the welcome email on or off
  • The welcome email is sent after the user’s account is fully activated (after email verification or admin approval, depending on the activation mode)

Email provider required

The welcome email requires an email provider to be configured in Email Settings. If no email provider is set up, enabling this option has no effect.


CLI equivalents

Dashboard SettingCLI Command
Set user quota
qb user quota -u <username> -o <size>

Dashboard advantage

Most Registration Settings — including activation modes, username policies, password policies, and welcome email configuration — are available only through the dashboard. The CLI allows setting per-user quotas after registration.


Best practices

Do

  • Use Admin Approval mode for private servers where you want to vet every new user before granting access
  • Use Email Activation for semi-public servers to verify that users have a valid email address
  • Set a reasonable default quota to prevent new users from consuming all available disk space immediately
  • Add common system account names (admin, root, system, operator) to the disallowed username list in <a href='/docs/dashboard/settings/security'>Security Settings</a>
  • Enable the welcome email to give new users a positive onboarding experience with instructions for getting started
  • Create a dedicated group for new users with only the application access they need initially — you can expand access later by moving them to other groups

Don't

  • Don't use No Activation mode on a public-facing server without additional protections — any visitor can create an account immediately
  • Don't set the minimum password length below 8 characters — short passwords are easily compromised
  • Don't forget to configure an email provider before enabling Email Activation mode — users will be stuck in a pending state with no way to verify
  • Don't set quotas to Unlimited for all users unless you have ample disk space — a single user running unchecked downloads can fill the server

FAQ

When using Admin Approval mode, pending users appear in the User Admin page. Click the approve button next to each pending user to activate their account.
Yes. Policy changes apply to new registrations only. Existing usernames that do not match the new policy are not affected — they continue to work normally.
Users who are already in the pending queue remain pending. Changing the activation mode only affects new registrations. You can still approve pending users from the User Admin page regardless of the current mode.
Yes. Both the dashboard and the CLI (qb user create) read the same username policy from the database. This ensures consistent validation regardless of how users are created.
The default group determines which user group new registrations are automatically assigned to. This controls their initial application access — a user can only see and install applications that their group allows. The setting defaults to the Access group (download clients only). You can change it to any group except Administrator.
The Administrator group has full access to all applications and is reserved for admin-level users. Allowing new registrations to be placed in the Administrator group would grant unrestricted application access by default, which is a security risk. Assign users to the Administrator group manually through the User Admin page when appropriate.
Yes. The default group setting is shared between Registration Settings and the User Groups page. Changing it in either location updates the same configuration, so both pages always show the current value.
The welcome email template can be customized in Email Settings on the Templates tab. You can modify the subject, body, and variables used in the email.

Join the Community

Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.

Dedicated Support
Feature Previews
Community Configs
Active Discussions
Join Discord Server