feat: create support portal (support.serviceradar.cloud) #864

Closed
opened 2026-03-28 04:29:20 +00:00 by mfreeman451 · 1 comment
Owner

Imported from GitHub.

Original GitHub issue: #2506
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2506
Original created: 2026-01-25T08:29:18Z


Is your feature request related to a problem?

  • Registered Users can open new case
  • Sign-up for paid support offering
  • Stripe integration

When we build the control-plane for the SaaS, this is where users would signup and get into our SaaS/platform level DB and into an internal/non-existent CRM.

This is the database we should auth/verify people from when they're trying to sign-in to the support portal to create a new case, etc. None of that really exists yet, but we could start on the control-plane and get it up to the point where users can signup/register and then we could at least leverage that functionality in the support portal. This allows us to start accepting support contracts for customers before the SaaS is complete if we wanted.

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

Imported from GitHub. Original GitHub issue: #2506 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2506 Original created: 2026-01-25T08:29:18Z --- **Is your feature request related to a problem?** - [ ] Registered Users can open new case - [ ] Sign-up for paid support offering - [ ] Stripe integration When we build the control-plane for the SaaS, this is where users would signup and get into our SaaS/platform level DB and into an internal/non-existent CRM. This is the database we should auth/verify people from when they're trying to sign-in to the support portal to create a new case, etc. None of that really exists yet, but we could start on the control-plane and get it up to the point where users can signup/register and then we could at least leverage that functionality in the support portal. This allows us to start accepting support contracts for customers before the SaaS is complete if we wanted. **Describe the solution you'd like** A clear and concise description of what you want to happen. **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. **Additional context** Add any other context or screenshots about the feature request here.
Author
Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2506#issuecomment-4145573269
Original created: 2026-03-27T21:55:59Z


closing, tracking elsewhere

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2506#issuecomment-4145573269 Original created: 2026-03-27T21:55:59Z --- closing, tracking elsewhere
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
carverauto/serviceradar#864
No description provided.