Skip to main content
This page is for Jira and Confluence admins, Neo team admins, and anyone reviewing the Neo app.

​
Who does what

  • Jira or Confluence admin installs the Neo app on your site. This person does not need a Neo account and doesn’t take up a Neo seat.
  • Neo team admin authorizes and manages Jira and Confluence (reconnect, disconnect, switch sites) from Neo’s Settings → Applications. Authorizing does not require Atlassian admin rights.
These are two separate stages and they can be done by two different people. Once the install lands, everyone on the Atlassian site can use Neo, not only the two who set it up. Jira and Confluence are connected separately, so each one is authorized and installed on its own. Neo isn’t distributed through the Atlassian Marketplace. It’s installed with a direct install link, one per product, shown on that product’s entry in Neo’s Applications settings. Atlassian shows its consent screen to whoever opens that link, so that person needs Jira or Confluence admin rights. If the person setting Neo up doesn’t have them, they authorize first and send the install link to an admin, rather than restarting the setup as the admin. See Have your Atlassian admin approve the install.

​
The Neo bot

Neo runs as a native Atlassian app, acting as a bot rather than a user. It doesn’t use a Jira seat or license, you don’t assign issues to it, and it only acts when you direct it, either by mentioning @neo in Jira or asking Neo in a task.

​
Permissions Neo requests

There are two separate steps, each with its own purpose.

​
1. Authorize (sign-in), to identify your site

The one-time Authorize step confirms which Atlassian site to connect, and needs no Atlassian admin rights. Doing it before the install is what lets Neo recognize the site and link it automatically. It requests read-only access:
  • Jira: read:jira-work, read:jira-user
  • Confluence: read:confluence-space.summary
Neo uses this only to find and link the right site, not to read or change your data day to day.

​
2. Install, for what the bot can do

When you install the app, it gets the permissions it needs to do the work:
  • Jira: read issues, projects, and users, and create, update, comment on, and move issues.
  • Confluence: read and search pages and spaces, and create, update, and archive pages.
Neo can create, update, and archive Confluence pages in addition to reading them. Because this adds Confluence write permissions, a Confluence admin must approve the updated install before it takes effect (see When to reconnect or reinstall).

​
One site per product

Each product connects to a single Atlassian site. Installing Neo on a different site switches to it, and the previous one is dropped. This keeps ownership simple, with no multi-site state to manage.

​
When to reconnect or reinstall

  • You disconnected from Neo but the app is still installed: Reconnect by re-authorizing.
  • The app was uninstalled from Atlassian: authorize and install again.
  • A new app version changes permissions: Atlassian marks the install Outdated, and a Jira or Confluence admin approves the update before it takes effect.

​
Reviewer summary

Neo uses Atlassian permissions to:
  • read the issue (and its comments and attachments) it’s asked to work on
  • create, update, comment on, and move Jira issues
  • read, search, create, update, and archive Confluence pages
  • act as a native app bot, brought in by mentioning @neo in Jira or by a request from a Neo task
For recovery and common admin issues, see Troubleshooting.