Product documentation
Updated March 21, 2026

User Policies

Settings > Licensing & Users > User Policies: registration rules, default role, max users per project, and password requirements.

User Policies

Configure user registration, default roles, and password policies.

Organization-wide rules apply to how users join, which role they receive by default, and password strength and rotation.

Where to find everything: Administration Settings.

Actions

  • Reset to defaults — restore policy fields to product defaults.
  • Save settings — apply changes.

User registration settings

Typical checkboxes:

  • Allow public user registration — when off, only invited or admin-created users join.
  • Require email verification for new users — user must verify email before full access.
  • Require admin approval for new user accounts — recommended for production so every account is reviewed.

Default role settings

  • Default user role — dropdown (for example Reader) assigned to new users unless overridden.
  • Max users per project — numeric cap on members per project (for example 100).

Related: Role Permissions.

Password policy

A security notice states that requirements apply to all users.

Common controls:

  • Minimum length (for example 8).
  • Maximum age (days) — password expiry (0 often means no expiry).
  • Complexity — checkboxes such as: uppercase, lowercase, number, special character.

Best practices

  • Require admin approval in production.
  • Default new users to Reader or another least-privilege role.
  • Review inactive accounts and policy compliance regularly.

Related articles

Next steps

Still stuck?

Tell us what you’re trying to accomplish and we’ll point you to the right setup—installation, auth, or CI/CD wiring.