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

​
Who does what

  • Atlassian site admin installs the Neo app on your Jira and Confluence site.
  • Neo team admin connects and manages Jira and Confluence (reconnect, disconnect, switch sites) from Neo’s Settings → Applications.
Jira and Confluence are connected separately, so each one is authorized and installed on its own.

​
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. 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 only.
Neo requests no Confluence write permissions. Confluence access is strictly read-only, so the app can’t create or edit pages.

​
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 site 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 and search Confluence for context (never write)
  • 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.