# Squest as a self service portal thughts **URL:** \ **Category:** Get Help\ **Tags:** aap, awx\ **Created:** [March 19, 2025, 6:27pm UTC](https://forum.ansible.com/t/squest-as-a-self-service-portal-thughts/41127 "2025-03-19T18:27:05Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![dsexton18](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dsexton18/32/4952_2.png) [@dsexton18](https://forum.ansible.com/u/dsexton18)\ **Post date:** [March 19, 2025, 6:27pm UTC](https://forum.ansible.com/t/squest-as-a-self-service-portal-thughts/41127/1 "2025-03-19T18:27:05Z")
Curious on others thoughts about [Squest](https://hewlettpackard.github.io/squest/) as a serf service portal for AWX/AAP? Is there a better solution for a self service portal? Preferably to self host. ---
**Author:** ![anon81884396](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@anon81884396](https://forum.ansible.com/u/anon81884396)\ **Post date:** [March 19, 2025, 10:33pm UTC](https://forum.ansible.com/t/squest-as-a-self-service-portal-thughts/41127/2 "2025-03-19T22:33:44Z")
I’m against any portals for the serfs, lest they gain literacy and threaten the landed gentry. ---
**Author:** ![iwt-cmd](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/iwt-cmd/32/9120_2.png) [@iwt-cmd](https://forum.ansible.com/u/iwt-cmd)\ **Post date:** [March 20, 2025, 1:33pm UTC](https://forum.ansible.com/t/squest-as-a-self-service-portal-thughts/41127/3 "2025-03-20T13:33:09Z")
I’ve never used Squest but one thing to consider is if you can integrate AWX/AAP into a system that your users are already familiar with. If you have an IT ticketing system, can you do API calls or use EDA to present automations via forms or a ticket submit? Or do you have another common user interface that has events which can trigger automations? It’s probably more work on the frontend to setup but avoids adding in another interface that users need to be trained on and log into. Not self-hosted but we use Jira for ticketing so we’re working on utilizing Jira forms to allow users to submit a request (VM build, snapshot, etc…) that then kicks off a workflow template and writes the output back as comments in the ticket and updates the status. We don’t need to have everyone log into and be trained on the AAP interface while also getting all of the job details into the same system we use for reporting. Our Jira instance also has an extensive RBAC and approval structure which we can leverage. Squest may be a better option for your scenario but just throwing something out there to consider. Best regards, Joe ---
**Author:** ![dsexton18](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dsexton18/32/4952_2.png) [@dsexton18](https://forum.ansible.com/u/dsexton18)\ **Post date:** [April 22, 2025, 9:14am UTC](https://forum.ansible.com/t/squest-as-a-self-service-portal-thughts/41127/4 "2025-04-22T09:14:14Z")
Fair points. I haven’t used Jira so not familiar with it. I have primarily used gitlab. Gitlab doesn’t have an easy way of getting input from a user unless one is good at parsing Markdown and etc. I was looking for a way to leverage something rebuilt or that wasen’t overly difficult to setup or for users to understand. ---
**Author:** ![iwt-cmd](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/iwt-cmd/32/9120_2.png) [@iwt-cmd](https://forum.ansible.com/u/iwt-cmd)\ **Post date:** [April 22, 2025, 12:53pm UTC](https://forum.ansible.com/t/squest-as-a-self-service-portal-thughts/41127/5 "2025-04-22T12:53:14Z")
I was somewhat surprised that Gitlab didn’t have an issue intake form but it looks like the feature request has been open for about 5 years ( [form for issues (#31575) · Issue · gitlab-org/gitlab](https://gitlab.com/gitlab-org/gitlab/-/issues/31575)).