An option to disable registration in self-hosted setup

[thelazyoxymoron]

Would love to have an option to disable user registrations

[Onatcer]

Hi, thank you for the feature request.

That's a good point, we'll look into that. I'm not quite sure how we can best handle the initial user registration, as well as adding new users, in that case.

My initial thoughts: We could either do a setting in the admin panel somewhere, or it would be an environment variable.

If anyone has input feel free to add it in the comments to this issue.

[thelazyoxymoron]

Environment variable should be sufficient in this case

[micalm]

I agree that an env would be enough; this is how Gitea does it.

They do have an registration (or rather user creation) view for the admin, which would require additional consideration for solidtime:

1. Do users get sent a password via email or do they have to set it themselves?
2. Are personal organizations created or are users forced to live in a certain organization?
3. Something else I'm probably missing now

---

Another approach that I think would be similar in effort required is a Slack-like ALLOWED_EMAILS or something, where guests can register, as long as they have an email in a domain allowed by the instance admin. This doesn't require any changes or new flows except a small message that says you can't register from that email address, bye.

[thelazyoxymoron]

Isn't there already a "new user" creation functionality for admins in Solidtime as well? I can see one in /admin/users page. Or am I missing something?

[Onatcer]

@thelazyoxymoron yes you can create users, but I'm pretty sure you can break the application with that right now, as in our regular flow you'll always have a organization as well, and basically everything happens in the organization. Not sure if you can assign users to organizations via the admin panel right now and if email confirmation stuff works correctly in that case.

But the bigger blocker is that you need to register an account to access the admin panel first, so we have to create some flow for that to set up an initial user.

[korridor]

We decided to move feature requests into github discussions, to separate feature requests from bugs and allow for better prioritization. If this feature is important to you, you can upvote it to let us know.

[kosli]

I was also looking into a way to disable the user registration, as I want to use solidtime with my "closed" user group and not have random people (or bots) signing up on the publicly available instance. An env variable would be definitely sufficient, whereas new users could be invited from the organization panel.

[dallyger]

I'm not quite sure how we can best handle the initial user registration

I think, that that is not actually a blocker. A viable work-around would be to create the instance, register as an user and then set the env variable or the option to disable any new registrations.

Of course, having an actual flow for that would be great. Maybe as a cli command like create:user --admin? But my guess is, that most people would be fine with the work-around.