GitHub Issues

The best channel for bug reports, feature requests, and questions. Issues are public, so other admins benefit from the answer too — chances are someone already reported what you're seeing.

Open a GitHub Issue

Prefer a direct, private conversation? Message Oliver Kieselbach on LinkedIn — for anything that shouldn't go into a public issue, such as tenant-specific details, or just to say hi.

Message on LinkedIn

Something Wrong with an Enrollment?

If your question is about a specific enrollment, the easiest way is the Report Session button right in the portal's session view. It flags that session for analysis, and you can add a problem description and attach screenshots directly in the dialog — everything needed arrives in one place.

For everything else — general questions, portal issues, or feature ideas — a GitHub issue works best. No GitHub account? Use Send feedback in the portal's help menu (?) instead. A short description of what you expected versus what happened, plus a screenshot where helpful, makes it much faster to track down.

GitHub issues are public — leave out anything confidential like tenant names, user identities, or internal hostnames.

Help Yourself First

Many questions are already answered in the documentation — it's the fastest way to a solution.

Documentation →Setup guides, concepts, and reference for every feature.FAQ →Answers to the most common questions.Service Announcements →Known issues and current service status.

Reporting a Security Issue

Please do not report security vulnerabilities in a public issue. Use a private GitHub security advisory instead, so the issue can be assessed and fixed before details become public.