RELATED IDEAS
Private portal self-registration for users that are not employees
THis statement from your documentation is the issue:
"Private ideas portal users
Users can only register for a private portal if they use an email address that belongs to one of the domains included in the Employee portal setting."
THere should be a concept of a private portal (our software is highly competitive and many ideas could be leveeraged against us, making keeping this private vital.) where we have employees (Product team, support, customer success) that need access and the ability to comment privately on ideas before they are shared with the entire portal audience. THe Portal audience would be customers who self register, and we would like that registration to be restricted by customer domain. Right now, if we use the domain restriction, those users are EMPLOYEES and we can use VIsible to employees to hide ideas that arent ready for voting or "public" consumption.
Our only recourse is to turn off registration and import the users directly which seems counter productive and heavy handed given the self serve nature of this portal.
If we could just have a field above USERS which are valid domains (same as the EMployees domain field) that self registering users domains are checked against, this would resolve our issue.
-
ADMIN RESPONSEDec 4, 2025
Save time from manually inviting people to your ideas portal. Instead, let trusted email domains sign themselves up for access.
Go to Portal settings > Users > General. Set the new Self-registration field to include the email domains that are allowed to sign up.
This is separate from the Employees email domain field which allows self-signup and also grants the user employee capabilities.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +2
1
MERGED
Add a trusted organizations idea portal user type
Today users with email addresses using the domains specified for internal portal users can self register for private idea portals. These domains can sometimes be used as a mix of the company domain, and customer domains so customers can self regis...
0
Shipped
6
MERGED
Additional visibility category in Ideas Portal
Currently there are three options: Not visible, Visible to Employees and Partners, Visible to Anyone.
I would like a 4th option - I would like the flexibility to choose whether an idea is displayed just to Employees as there are times when I dont ...
1
Shipped
8
MERGED
Customise the message displayed when a user tries to register for a Private Portal, but has yet to have their domain added.
Can we please have the ability to configure the message displayed in our Private Portal when a user tries to register but has yet to have their domain added. Presently they see a message stating: 'Your email domain doesn't allow you to self regist...
2
Shipped
11
MERGED
Allow users with a specified email domain to self-register as external users
For those of us managing portals that are private (and need to remain so), the ability to allow individuals with email accounts in specified domains to self-register as external users would be a godsend. SSO options won't work for us and our porta...
2
Shipped
© 2025 Aha! Labs Inc.•All rights reserved
With the rapid advancement of AI, exposing ideas in a public domain poses a much greater competitive risk. It has become far easier to develop and launch new capabilities or products, and many executives or boards are understandably cautious about sharing potential gaps publicly. As a result, the idea portal can quickly become a point of friction rather than adoption.
That said, whether an idea portal is public or private shouldn’t be what makes it difficult for Aha! customers to use. Without self-registration, Aha! customers are forced to rely on manual processes that often lead to increased support tickets — which none of us want to create by design. This manual overhead also complicates onboarding, adding minimal value while creating long-term maintenance issues as users change roles or leave their organizations. Ultimately, not enabling self-registration adds unnecessary steps and limits overall utilization, which reduces the value of the feature itself.
Using domains as the “employee” attribute also limits flexibility. It prevents organizations from having internal-only discussions and restricts customers who may want or need to remain anonymous, an important consideration in industries where confidentiality and sensitivity are key.
We would like the ability to add a customer organization with Domain(s), and this be enough to allow customer users to register for a private portal. Having to import them is problematic. A flag at the organization level 'Allow users self registration' or alike would be great.
I would almost fully support the OP idea, but augment that allowing an Aha user to approve self-registered customer users, instead of having to enter all approved domains, would make the feature usable to organizations with thousands of customers. We have simply too many customers to enter all the approved domains, or create users for them, or keep them up to date with spreadsheet imports. So, choosing between two bad options, we're choosing to keep the portal public, which means indexed by search engines, available to competitors...
We have worked around this issue using Google App Script. Our clients register by filling in a Google Form, and our app script then creates the account and sends the user an email to set their password.
It would be great to have this feature OR one that allows us to disable the registration link and add custom text to redirect the user to our Help Center or our Google Form.