Support

Write to support@alidadeapps.com.

A person reads it. Alidade is small, and support is answered by the developer who wrote the code, in English or Portuguese.

What to expect: a first reply within one business day, Monday to Friday, Brazil time (UTC−3).

Before you write, two pages worth checking

Most questions have an answer already written down, because most of them are about a limit rather than a bug:

• Limitations — what the app does not do, and why. If something is not working the way you expected, it is worth a look here first.
• Documentation — getting a specification in, search, the catalog, export, and migrating from another app.

What to include

You do not have to fill in a form. But these four things turn a two-day conversation into a one-reply answer:

1. What you did, and what happened instead.
2. Where the specification came from — pasted, URL, attachment, or a CI push.
3. The specification itself, if you are able to share it. If you are not, the smallest document that shows the same problem is just as good, and often better.
4. A screenshot, if it is about how something looks. Dark mode, PDF export and rendering questions are almost always faster with one.

Please do not send us a credential. Not a repository token, not an API key, not a password — not even redacted. We never need one, and this app is built so that we never hold one.

Reporting a security issue

Write to security@alidadeapps.com.

Security reports are acknowledged within one business day and fixed within the timeframes of Atlassian's Marketplace Security Bug Fix Policy, which this app is bound by as a listed Marketplace app.

Please give us a chance to ship a fix before disclosing publicly. We will tell you when it is out, and credit you if you would like to be credited.

Feature requests and bugs

The same address. Requests are read, and the ones that recur get built — this app exists because a decade of unanswered requests in this category were read carefully.

Two things worth setting expectations on:

• A limit that comes from the Confluence platform cannot be worked around by us. When that is the answer, we will say so plainly and point at the exact reason on the limitations page rather than leaving it vague.
• Anything we learn from a support conversation becomes a documentation page before the ticket is closed, so the next person finds it without writing in.

Billing, licensing and invoices

Billing is handled entirely by Atlassian, not by us. Subscriptions, invoices, refunds, tax documents and licence changes all live in your Atlassian account:

admin.atlassian.com → Billing.

We have no access to your payment details and cannot issue an invoice or a refund. If you are not sure whether a question is ours or Atlassian's, write to us anyway and we will tell you where it goes.