Have something to say?

Tell us how we could make the product more useful to you.

Allow "simple" OIDC setups for self-hosted instances

Hello! Is it possible to change the OIDC setup to be “normal”, as in: No domain restrictions (anyone can login using OIDC) No implicit routing to OIDC providers This would go towards the more common implementation of OIDC sign in, where the security layer is the OIDC provider, and not the application (with domain routing). This would also imply a change in the login screen, because you’d need to have, like most apps do, two login methods side-by-side — email/password and OIDC providers. With the option to disable password login, if the instance admin only wants OIDC login available. I am willing to help with a PR for this, if the team is open to it! :) Thanks!

Filipe Silva Medeiros about 5 hours ago

1

💡 Feature Request

SMTP OAuth Authentication Support for Microsoft 365

I would like to request support for SMTP authentication via OAuth for Microsoft 365 accounts. Microsoft is gradually deprecating basic SMTP authentication (username and password) to improve security and better protect accounts from misuse. As a result, many organizations are required to switch to OAuth-based authentication for sending emails. Currently, I do not see an option to configure OAuth authentication for SMTP. Adding support for OAuth would allow users to continue sending emails from their custom domains through Microsoft 365 while complying with Microsoft's modern authentication requirements. This feature would help ensure long-term compatibility with Microsoft 365 and provide a more secure authentication method for email delivery.

Wedl 14 days ago

1

💡 Feature Request

Consolidate "Scale" input data in Submissions / Custom Column Grouping

Use Case: We use OpnForm as an order form for our local brewery to make ordering easy for our customers. The Problem: When we use the "Scale" input for customers to select product quantities, every single option generates its own separate column in the submissions table. If we have 4 options for one type of beer, it creates 4 separate columns, making the data table very wide and hard to read. Proposed Solution: Quick fix: Make the "Scale" input display its data in a single, grouped column inside the submissions table, exactly how the "Matrix" input currently works. Ideal fix: Allow users to create custom columns in the submissions view, where we can manually map and group answers from the same product type into one unified column. This would make OpnForm incredibly powerful for e-commerce and order management. Thank you for the great tool!

Naročila Pivovarna about 2 months ago

1

💡 Feature Request

Filtered Submission Limit (Count only submissions matching a condition)

Current behavior: "Limit number of submissions" counts all submissions regardless of their content. Once the limit is reached, the form closes. Problem: I use the form as an event sign-up (quiz night). Participants can update their status to "Not coming," but those entries still count toward the submission limit. This means the event appears full even when spots have freed up. Proposed behavior: Allow an optional filter on the submission limit, so only submissions matching a condition count toward the limit. Example configuration: Limit: 30 submissions Count only where: status == "Going" A participant who changes their status to "Not coming" would no longer count, freeing up their spot automatically. Use case: A coffee shop runs weekly quiz nights for 30 people. Sign-ups come through the form. When someone cancels (status → "Not coming"), their spot should reopen without manual intervention. Currently, the organizer must manually increase the limit or reopen the form.

Peter Kizik about 2 months ago

1

💡 Feature Request