starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #2058] Restrict signups to a specific domain #590

New issue

Closed

opened 2026-02-26 18:47:42 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 18:47:42 +03:00

Owner

Originally created by @massimone73 on GitHub (Oct 1, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2058

Feature Description

It would be nice to restrict and/or limit signup to users belonging to specific domain names, rather than open to everyone.

Use Case

I'm using Documenso and can't expose it outside the organization because I don't want outside users to be able to register and possibly access documents that have been uploaded without the appropriate visibility controls.

Proposed Solution

Vaultwarden, for example, has the following variable SIGNUPS_DOMAINS_WHITELIST, which allows you to specify which domains are authorized for registration.

Alternatives (optional)

No response

Additional Context

This feature is essential for correctly and safely managing access to corporate documents.

Please check the boxes that apply to this feature request.

I have searched the existing feature requests to make sure this is not a duplicate.
I have provided a detailed description of the requested feature.
I have explained the use case or scenario for this feature.
I have included any relevant technical details or design suggestions.
I understand that this is a suggestion and that there is no guarantee of implementation.
I want to work on creating a PR for this issue if approved

Originally created by @massimone73 on GitHub (Oct 1, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2058 ### Feature Description It would be nice to restrict and/or limit signup to users belonging to specific domain names, rather than open to everyone. ### Use Case I'm using Documenso and can't expose it outside the organization because I don't want outside users to be able to register and possibly access documents that have been uploaded without the appropriate visibility controls. ### Proposed Solution Vaultwarden, for example, has the following variable SIGNUPS_DOMAINS_WHITELIST, which allows you to specify which domains are authorized for registration. ### Alternatives (optional) _No response_ ### Additional Context This feature is essential for correctly and safely managing access to corporate documents. ### Please check the boxes that apply to this feature request. - [x] I have searched the existing feature requests to make sure this is not a duplicate. - [x] I have provided a detailed description of the requested feature. - [x] I have explained the use case or scenario for this feature. - [x] I have included any relevant technical details or design suggestions. - [x] I understand that this is a suggestion and that there is no guarantee of implementation. - [ ] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:47:42 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:47:42 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 1, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Oct 1, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:47:42 +03:00

Author

Owner

@shochdoerfer commented on GitHub (Oct 7, 2025):

You can disable the sign-up by setting the NEXT_PUBLIC_DISABLE_SIGNUP env var to false. As a downside, you don't seem to be able to invite new users via the Admin UI. At least that did not work the last time I've tried it.

@shochdoerfer commented on GitHub (Oct 7, 2025): You can disable the sign-up by setting the `NEXT_PUBLIC_DISABLE_SIGNUP` env var to false. As a downside, you don't seem to be able to invite new users via the Admin UI. At least that did not work the last time I've tried it.

kerem commented

2026-02-26 18:47:42 +03:00

Author

Owner

@massimone73 commented on GitHub (Oct 13, 2025):

You can disable the sign-up by setting the env var to false. As a downside, you don't seem to be able to invite new users via the Admin UI. At least that did not work the last time I've tried it.NEXT_PUBLIC_DISABLE_SIGNUP

In fact, there's no feature available or visible for sending invitations. And in any case, I believe that restricting the domain names that can register remains the best solution for me.

@massimone73 commented on GitHub (Oct 13, 2025): > You can disable the sign-up by setting the env var to false. As a downside, you don't seem to be able to invite new users via the Admin UI. At least that did not work the last time I've tried it.`NEXT_PUBLIC_DISABLE_SIGNUP` In fact, there's no feature available or visible for sending invitations. And in any case, I believe that restricting the domain names that can register remains the best solution for me.

kerem commented

2026-02-26 18:47:43 +03:00

Author

Owner

@jasoc commented on GitHub (Oct 13, 2025):

As @massimone73 mentioned, it would be great to have something like DOCUMENSO_ALLOWED_DOMAINS="@acme.org,@test.com", without having to disable signups entirely. It could also be nice to make this configurable from the admin UI.

@jasoc commented on GitHub (Oct 13, 2025): As @massimone73 mentioned, it would be great to have something like `DOCUMENSO_ALLOWED_DOMAINS`=`"@acme.org,@test.com"`, without having to disable signups entirely. It could also be nice to make this configurable from the admin UI.

kerem commented

2026-02-26 18:47:43 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Oct 22, 2025):

Closing as duplicate of #1874

@ephraimduncan commented on GitHub (Oct 22, 2025): Closing as duplicate of #1874

kerem referenced this issue

2026-02-26 19:31:41 +03:00

[PR #590] [CLOSED] chore: improve plan subscription user experience #1065

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#590

No description provided.

Rows
Columns