Priority support
Your defects and messages handled ahead of the queue. Sensible when an outage in Teampass means your team cannot reach production credentials.
Getting help
Support & services
Community channels for most things, commercial options when Teampass sits on your critical path. Both go to the same place — the person who writes the code.
Start here — it is usually faster
Public channels keep answers searchable for the next person with the same problem, which is why they are the default rather than a fallback.
Documentation
Installation, configuration, administration and the API. Most questions are answered here, and it tracks the current release.
Discussions
Setup questions, advice, feature ideas and shared experience from other administrators. The right place for "how should I…" questions.
Issues
Bug reports. Include your version, PHP version and the steps to reproduce — a report that can be reproduced gets fixed far faster than one that cannot.
Security reports
Vulnerabilities go through the security policy, not the public tracker. Fixes are published as advisories once released.
When you need a commitment rather than a community
Sponsored development
Fund a feature you need. Scope and timeline agreed up front, and the result ships in the open-source release rather than as a private fork you then have to maintain.
Deployment assistance
Help sizing, installing, integrating with your directory or migrating from another manager — particularly useful for the first large rollout.
Sponsorship
Back the project through GitHub Sponsors. It is the least transactional option on this page, and the one that keeps everything else free.
Never send credentials to get support. Nobody working on Teampass will ask for your instance password, a database dump containing secrets, or the contents of an item. Logs, versions and error messages are enough — and if they are not, we will ask for something specific and safe.
Talk to the person who writes the code
Bugs and feature requests belong on GitHub, where they stay public and traceable. Everything else can come straight to the inbox.
-
Found a bug? Open an issue on GitHub — it gets tracked, and other users can see the fix land.
-
Need help or want a feature? GitHub Discussions is the fastest route, and answers stay searchable for everyone.
-
Reporting a vulnerability? Follow the security policy rather than the public tracker.
-
Commercial enquiry? Licences, quotes and sponsored development — [email protected].