Getting help
Stuck, found a bug, or have an idea? This page tells you where to go for each, and what to include so you get an answer quickly.
Start here
- Search these docs. The search box at the top covers every page. The FAQ and Troubleshooting answer the most common questions.
- Ask your workspace admin. Many problems, such as a missing project, an invitation or a plan limit, are settings an owner or admin can change.
- Ask whoever runs your server for problems with sign-in providers, email, AI or the desktop tracker download. They have the Admin guide.
Where to ask
| You want to | Go to |
|---|---|
| Ask how to do something | GitHub Discussions, Q&A |
| Share an idea | GitHub Discussions, Ideas |
| Show what you built | GitHub Discussions, Show and tell |
| Report a bug | Open a bug report |
| Request a feature | Open a feature request |
| Fix or improve these docs | Open a documentation issue, or use Edit this page on GitHub at the bottom of any page |
| Report a security problem | GitHub Security Advisory. See below |
| Get paid support, hosting or custom work | Email support@aliansoftware.net |
| Try AlianHub without installing it | The live demo |
Before opening an issue, search the open and closed issues and Discussions. Your problem may already be answered or fixed.
What to put in a bug report
The bug report form asks for these. The more you give, the faster it can be fixed.
| Item | Example |
|---|---|
| Version | The AlianHub version. Your admin can find it; see Changelog |
| Where it runs | Your browser, and, if you run the server, its system, database version and where files are stored |
| Steps | What you did, in order |
| Expected | What should have happened |
| Actual | What happened instead: the exact message, a screenshot |
| Smallest example | The fewest steps that still show the problem |
Keep secrets out
Never paste passwords, keys, tokens or customer data into an issue or discussion. They are public.
Report a security problem
Do not open a public issue for a security problem. Report it privately through a GitHub Security Advisory.
Include:
- A clear summary of the problem.
- What it can reach or affect.
- A proof of concept with code that shows real impact, such as access to data you should not see. A video is welcome but optional.
- Who is affected, and how.
What happens next:
- You can expect a first reply within 72 hours, on a best-effort basis.
- The maintainers check the report, judge how serious it is, and work on a fix.
- Details stay private until a fix is out and people have had time to upgrade. Please agree any public write-up with the maintainers first.
- Fixes go into the latest version. Older versions are not guaranteed a fix, so keep your server up to date.
- There is no bug bounty.
How fast you can expect an answer
AlianHub is maintained mainly by Alian Software, with help from the community. The aims are:
| What | Aim |
|---|---|
| New issues acknowledged | Within 3 to 5 working days |
| Security reports acknowledged | Within 72 hours |
| Pull requests reviewed | Within 5 to 10 working days |
| Fixes and new features | No promised date |
If a problem is urgent for a live deployment, consider paid support.
Paid support
Alian Software offers, for organisations that need it:
- Priority fixes with agreed response times.
- Help with compliance, audits, and other licence terms.
- Custom features built on your timeline.
- Onboarding and training.
- Fully managed hosting.
Email support@aliansoftware.net.
Be kind
Everyone in the AlianHub community follows the project's Code of Conduct. Be patient, and assume good intent.