Skip to main content
Neo connects to Jira and Confluence separately. You set each one up the same way in Settings → Applications. Connect one or both, since they’re independent.

Before you start

Connecting happens in two stages, and they need different people. Neither person needs what the other one has.
  • Authorize is done by a Neo user, from Neo’s Applications settings. This stage does not require Atlassian admin rights, so a regular Atlassian user can complete it.
  • Install is done by a Jira or Confluence admin, on the Atlassian side. That person does not need a Neo account, and doesn’t take up a Neo seat.
If one person holds both, they can do the whole thing start to finish. If not, the Neo user runs Authorize and hands the install off, which is the common case. See Have your Atlassian admin approve the install.
Neo isn’t listed on the Atlassian Marketplace, so searching there for “Neo” or “ProjectDiscovery” won’t find it. Neo is installed with a direct install link instead, either by running the connect flow in Settings → Applications or by sending that link to your Jira or Confluence admin.

Connect a product

Open Settings → Applications in Neo and select Jira or Confluence. Repeat for the other one if you want both. Run these in order. Authorizing first lets Neo identify your site before the install arrives, so it can link the two automatically.
1

Authorize with Atlassian

Click Authorize. You’re sent to Atlassian to sign in and approve, then returned to Neo. This links your Atlassian account to your Neo team. No Atlassian admin rights are needed for this step.
2

Choose a site (if asked)

If your Atlassian account has more than one site, Neo asks which one to connect. Pick it. If you only have one site, this step is skipped.
3

Install Neo

Click Install. Atlassian opens in a new tab where the app is approved. This adds Neo to the product you’re connecting, and it’s the step that requires a Jira or Confluence admin.
4

Wait for Connected

Neo shows Connected on its own once the install lands. It can take a minute or two, and the page updates automatically.
Jira and Confluence connect independently, so you’ll authorize and install each one separately.

Have your Atlassian admin approve the install

Only a Jira or Confluence admin can approve the app install, and Atlassian asks whoever is in the browser at the Install step. If that person isn’t an admin, the approval is refused and the connection never reaches Connected. You don’t have to hand the whole setup over, and you shouldn’t. Do the Authorize step yourself first, since it needs no admin rights and it lets Neo recognize your site when the install lands. Then send your admin the install link and let them approve it on their own. Your admin needs no Neo account to do this. The install link is shown on that product’s entry in Settings → Applications once you’ve authorized. It’s specific to the product you’re connecting, so a Jira link installs the Jira app and a Confluence link installs the Confluence app. Copy the one for the product you’re setting up rather than reusing a link from the other. The Jira app link looks like this:
A consent link from your own connect flow also works. Copy the URL of the Atlassian consent screen the flow opens. It carries a context value specific to that attempt, so start the flow again if it stops working:
Either way, once your admin approves, the install lands on your site and Neo switches to Connected on its own. It can take a minute or two. Everyone on the site can then use Neo, not just the two people who set it up.

The Neo bot

Neo installs as a bot. It doesn’t use a Jira seat or license, and you don’t assign issues to it. You bring it in by mentioning @neo.

Reconnect

If you disconnected from Neo but the app is still installed on your Atlassian site, reconnecting only needs the Authorize step again. Just click Reconnect. If the app was fully uninstalled from Atlassian, you’ll authorize and install again.

Disconnect

Use the Disconnect option in Neo’s Applications settings. This drops the link between Neo and that product.
  • The Neo app stays installed in Atlassian after a disconnect.
  • To fully remove it, uninstall the app from your Atlassian site (Atlassian admin → Manage apps).
  • You won’t be able to use @neo for that product until you reconnect.

Switching sites

Each product connects to one site at a time. To move to a different site, just install Neo on the new site. It becomes the connected site and the old one is dropped automatically. There’s no need to disconnect first.

Next