[GH-ISSUE #1244] Option to use custom domain with managed documenso #347

Closed
opened 2026-02-26 18:46:37 +03:00 by kerem · 2 comments
Owner

Originally created by @poeck on GitHub (Jul 23, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1244

Feature Description

I am requesting an option to use a custom domain with Documenso's hosted service. This feature would allow users to brand their document signing platform with their own domain, enhancing professionalism and trust. It could be a premium feature available on the Individual or Team plans, providing added value for paying users.

Use Case

Imagine a small business that uses Documenso for all its contract and document signing needs. Currently, they use the standard Documenso domain, but having the option to use their own custom domain would give a more professional appearance. This feature would make their communications and document signing process feel more seamless and integrated into their brand, improving client trust and satisfaction.

Proposed Solution

To implement this feature, an option could be added in the account or team settings for users to enter and verify their custom domain. This would involve updating DNS settings to point to Documenso's servers. The UI could include a simple form for domain entry and clear instructions for DNS configuration. Technical considerations might include setting up SSL certificates for the custom domains.

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 @poeck on GitHub (Jul 23, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1244 ### Feature Description I am requesting an option to use a custom domain with Documenso's hosted service. This feature would allow users to brand their document signing platform with their own domain, enhancing professionalism and trust. It could be a premium feature available on the Individual or Team plans, providing added value for paying users. ### Use Case Imagine a small business that uses Documenso for all its contract and document signing needs. Currently, they use the standard Documenso domain, but having the option to use their own custom domain would give a more professional appearance. This feature would make their communications and document signing process feel more seamless and integrated into their brand, improving client trust and satisfaction. ### Proposed Solution To implement this feature, an option could be added in the account or team settings for users to enter and verify their custom domain. This would involve updating DNS settings to point to Documenso's servers. The UI could include a simple form for domain entry and clear instructions for DNS configuration. Technical considerations might include setting up SSL certificates for the custom domains. ### 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:46:37 +03:00
Author
Owner

@poeck commented on GitHub (Jul 23, 2024):

Just realized this is a duplicate of #1059. Should I close this one?

<!-- gh-comment-id:2245509790 --> @poeck commented on GitHub (Jul 23, 2024): Just realized this is a duplicate of #1059. Should I close this one?
Author
Owner

@ephraimduncan commented on GitHub (Aug 27, 2025):

Closing this as a duplicate of #1059

<!-- gh-comment-id:3226428717 --> @ephraimduncan commented on GitHub (Aug 27, 2025): Closing this as a duplicate of #1059
Sign in to join this conversation.
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#347
No description provided.