Describe the feature

Description:

For daily work with Gogs, it would be very helpful if users had the ability to join organizations and their teams on their own, provided that this behavior is explicitly allowed by the respective administrators.

✅ Benefits:

• Reduces administrative overhead in larger organizations
• Encourages self-organization in open development groups
• Enables more flexible team structures for internal project

Describe the solution you'd like

💡 Proposed Implementation:

• Add a setting in the organization and/or team configuration:
  • “Allow self-join” (toggleable by admins)
  • If enabled, users can join the organization or team via the web interface.
  • If disabled, the current behavior remains: only admins can add users manually.

🔐 Security & Control:

• The option is disabled by default
• Only organization owners or team admins can enable it
• Optional: joining could be restricted to specific email domains or LDAP groups.

Describe alternatives you've considered

Currently, the only way to add users to an organization or team is through manual action by an administrator. While this works for small teams, it becomes inefficient in larger or more dynamic environments.

We have considered using external tools or scripts (e.g. LDAP sync via gogs-groupsync) to automate team membership, but these require additional setup and do not offer a user-friendly interface for self-service.

Another workaround is to create public repositories and rely on repository-level access control, but this does not scale well for structured collaboration within organizations and teams.

A built-in self-join feature would be a more elegant and scalable solution.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct