RELATED IDEAS
Non-production Aha! sandbox
I'd like to be able to create a non-production sandbox environment for my Aha! account so I can test account level settings and configurations, like SSO, without impacting my real settings and workspaces. A separate account is not ideal as I'd like to be able to test these changes in a production like environment. Separate workspaces do not work for some of the account level testing that is needed.
The key is the ability to create a duplicate “sandbox” account from an account. The sandbox would contain all of the configuration (workspaces, custom fields, integrations, etc) from the source account, but would not contain the data (features, goals, comments, history, etc).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +5
Thanks for initiating this requirement.
My requirement is similar. Is it possible to create a subdomain for the myinstance.aha.io? I want separate workspaces for my Sandbox and QA environments that should be accessible with different URL than my production URL. For example, myinstance.aha.io is my production environment; can I have sandbox.myinstacne.aha.io as my sandbox environment and https://qa.myinstance.aha.io as my QA environment under myinstacne.aha.io?
Now for Aha!, I can imagine this could be as equal as providing a new instance, and I thought of an interim solution to have logical partitions. Please refer to the attached presentation. Because I do not know Aha! tool's technical architecture, my assumption and conceptual presentation might be wrong, but I tried.