What is the challenge? |
Many teams have account-level SSO set up that provisions all internal users in a large group into Aha! as Reviewers or Viewers when they first log in. These individuals are also often directed to internal private portals to submit feedback. If the portal is their first entry point to Aha! before the internal account, they will either need to manage a separate login or have their portal and internal accounts merged by admins periodically. |
|---|---|
What is the impact? |
Managing multiple SSO pathways for the same group, or having users create email/password logins and later merging them once they are provisioned into the internal account, can be confusing and lead to extra admin overhead. The existing setting to allow Aha! users to log in only accounts for those who have already been provisioned through the main Account SSO, not those who have yet to do so. |
Describe your idea |
A portal setting for private portals that sets all users to redirect to the Account SSO first, as if they were assumed to be Aha! internal users. Users who are valid in the Account SSO group will be provisioned correctly as internal users before being able to access the portal, keeping them at one login. |
A new ideas portal option is available to restrict portal access to only Aha! users in your account. You can find this setting by going to Portal settings > Users > SSO. Check the box "Users must log in with an Aha! account." This will send all people accessing the portal to log in through their Aha! user in your account, including any SSO you may have set up for your account.