NNaatOps
Start free

Workspace settings

Time zone, teams, workflows, issue types, custom fields, labels, members, bots and chat alerts.

Open Settings at the bottom of the sidebar. Everyone has a My account tab and can read the workspace tabs. Changing workspace settings needs the role shown under each heading.

Workspace (owners and admins)

  • Time zone: decides when sprints start and end and how times read in alerts. New workspaces take the time zone of the browser used to sign up.
  • Export your data: Download export (.zip) gives you every project's issues, comments, test cases and runs, docs, API requests, sprints and releases, as CSV files for Excel and JSON files that keep every field. Passwords, tokens and secret API variables are left out.
  • Archived projects: restore a project archived from its ⋯ menu.
  • Archived issues: restore issues that were archived.

My account (everyone)

  • Password: change the password you sign in with. Your other devices are signed out.
  • Notifications: your email choice, the kinds of updates you want and alerts on this device. See Inbox and notifications.
  • API tokens: personal tokens for scripts and integrations. A token acts as you, with your role, and only in this workspace.

Connect an AI tool (MCP)

NaatOps is an MCP server, so Claude, Cursor, VS Code and other AI tools can look up and change your work without installing anything.

  1. In Settings › My account › API tokens, make a token (name it after the tool, such as Claude).
  2. Open Connect an AI tool (MCP) under the tokens. It shows the address and a ready-made setup for Claude Code, and settings to paste into Cursor, VS Code or another MCP client.
  3. Ask the tool things like "what's left in the current sprint?", "write test cases for PAY-12" or "log 45 minutes on PAY-12".

The tool acts as you: it sees and changes only what your role allows, in this workspace. Revoke the token to cut it off.

Teams (owners, admins, managers)

Create teams, add people and give each a team role: Product Owner, Scrum Master, Tech Lead, Developer, QA, Business Analyst or Designer. Teams filter the board, own sprints and group the capacity view.

Workflows (owners and admins)

The statuses issues move through. By default: Backlog, Ready, In Progress, In Review, QA and Done.

  • Add, rename or remove statuses. Each status belongs to a kind: to do, in progress or done. Reports and automation use the kind.
  • Move statuses up or down to change the order of the board's columns.
  • Transitions: with none set, issues can move between any statuses. Add transitions to allow only those moves, for example so that work must pass QA before Done.

Custom fields (owners and admins)

Add fields your team needs on issues, such as Client ticket, Billable or Module. Types: text, number, single choice, multiple choice, date, person, URL and checkbox. Fields appear in each issue's properties.

Issue types (owners and admins)

Rename issue types, change their colour and description, or turn off types you don't use.

Labels (managers and above can rename or delete)

Labels are added on issues as people type them. Here you can rename, recolour or delete them.

Repositories (owners and admins)

Add Git repositories, get the webhook details to paste into GitHub, make a new webhook secret and set each default branch. See Pipelines and code.

Members

  • Invite someone and Pending invitations (owners and admins).
  • Active members: everyone in the workspace. Owners and admins can change a role or remove someone here. See Roles and permissions.

Audit log (owners and admins)

A record of every important action in the workspace, newest first. Entries can't be edited or removed, and they're kept for as long as the workspace exists. It records:

  • Sign-ins and security: sign-ins, including single sign-on, failed sign-ins with the address and browser, password changes and resets, API tokens and bots.
  • People and access: invitations, joins, role changes and removals.
  • Billing: billing details, checkouts, payments, cancelling and resuming.
  • Workspace settings: time zone, workflow statuses and transitions, issue types, custom fields, labels, automation rules and chat alerts for Slack, Microsoft Teams and Google Chat.
  • Projects and work: new projects and teams, deleted and restored issues, deleted releases and increments, share links, archived projects, and changes to someone else's time.
  • Exports and imports, Code and pipelines (repositories and production environments) and Docs.

Narrow the list with Search (an email, project key or name), What, Who, and From and To dates. Download CSV saves what the filters show, up to 10,000 rows, for an auditor or a client's security questionnaire.

The audit log with its filtersThe audit log with its filters

Rates (owners and admins)

Each person's bill rate and cost rate per hour, used by project budgets. See Project budgets and rates.

Billing (owners and admins)

Only owners and admins see this tab. See Plans, billing and invoices.

Bots (owners and admins)

A bot is a non-human member, such as an editor plugin, with its own id, key and role. Its changes show under the bot's name. Create a bot and copy its key straight away: it's shown only once. You can change a bot's role or rotate its key; after rotating, the old key keeps working for about ten minutes.

Chat alerts (owners and admins)

Settings › Chat alerts posts issue changes into the chat your team already uses: Slack, Microsoft Teams or Google Chat.

Slack

  1. Create the channel in Slack first, such as #naatops-alerts, and invite the NaatOps app to it.
  2. Enter the Channel name and tick Post issue changes to this channel.
  3. Choose Save, then Send test.

Microsoft Teams and Google Chat

You connect a Teams channel or a Google Chat space with an incoming webhook URL, which you make in Teams or Google Chat.

In Microsoft Teams: in the channel, open ••• › Workflows, choose Post to a channel when a webhook request is received, name it NaatOps and finish the steps. Copy the URL it shows.

In Google Chat: open the space name › Apps & integrations › Webhooks, add a webhook called NaatOps and copy its URL. Webhooks need a Google Workspace account.

Then, in NaatOps:

  1. Under Microsoft Teams and Google Chat, choose Add a channel.
  2. Pick Where (Microsoft Teams or Google Chat) and paste the Webhook URL.
  3. Give it a Name you'll recognise, such as Delivery channel.
  4. Pick what to Post: New issues, status moves and comments, or Every issue change (also edits such as priority, assignee and title).
  5. Under Projects, tick the projects it covers. Leave them all unticked for every project, including ones you add later.
  6. Choose Connect, then Send test on the channel to check a post arrives.

Adding a Teams channelAdding a Teams channel

Each post names the issue with a link to it, what changed, who changed it and when. When several changes happen close together, they arrive as one summary instead of a post each, so the channel stays readable. You can connect several channels, for example one per client project.

Teams and Google Chat channels in settingsTeams and Google Chat channels in settings

On each channel:

  • Send test posts a test message.
  • Pause stops posting; Resume starts again from now, without the changes made while it was paused.
  • Edit changes the name, what it posts or its projects. Leave the URL empty to keep the current one.
  • Remove disconnects it.

The webhook URL works like a password, so it's never shown again after you save it; the list shows only its address. Only Teams workflow and Google Chat addresses are accepted.

If someone deletes the webhook in Teams or Google Chat, the channel pauses itself and says so. Make a new webhook, choose Edit, paste the new URL and save. If the chat app is down for a while, NaatOps retries for a few minutes before skipping those changes.

Connecting, changing and removing channels is recorded in Settings › Audit log.

Automation and Import

See Automation rules and Import from Jira or CSV.