Panel as frontend app (support tracker)

The CMS Questions
1

Hi there,

I had this idea to create a support/ticket-system for my clients. I’ve been using Notion in the passed, but it just doesn’t work for me. In my opinion Kirby is a more friendly interface :slight_smile:

I had this structure in mind:

  • Kirby-panel served as the frontend app (not the ‘/panel’ slug).
  • client’s get a login (2fa) with the following role-permissions:
access:
    system: false
    users: false
    site: false
    account: true // they can only see there own account-page
  • The client’s account-page would serve as it’s support-tracker. With a section to create drafts (= tickets) which then can be changed by the admin-user who has permission to change the status.
  • A hook that triggers an e-mail notification when a ticket has changed status

The creation of the correct permissions already works. Also the support-tracker and hook seem to be douable. the only thing I’m actually scratching my head about is how to make the Kirby instance a frontend-ish app… Is this possible?

In addition I want to create a panel plugin to redirect them to this support-tracker from their own cms. Or, even better, create tickets right from their cms. (still figuring out the plugin process)

2

We do that with https://lab.getkirby.com (there even with automatic sign-in to a public account). I don’t know any easy way how to not make it run in a subdirectory, but you can customize the slug and add a redirect to the home template that sends any user directly there then.

I assume that the account page here is the account user view. Keep in mind that users cannot have subpages, just fields. If you want to work with subpages, you’d have to allow accessing the site area as well and create there a page per user, where the tickets can be created as subpages.

That would probably be possible with a custom API endpoint.