---
slug: /capabilities/release-notes/abi-3-7-permission-system
sidebar_position: 0
title: "ABI 3.7: the permission system"
question: What is new in ABI 3.7?

---

# ABI 3.7: the permission system

- **Document Type:** Release note
- **Status:** Released: `naas-abi` 3.7.0, `naas-abi-core` 3.3.0, `naas-abi-cli` 3.3.0, `naas-abi-sdk` 0.3.0, `naas-abi-proto` 0.3.0, and the first `naas-abi-idp` (0.1.0)
- **Date:** 2026-11-07

ABI 3.7 brings a permission system to every part of the platform. One
service, IAM, decides who may do what, denied by default, for people, scripts
and modules alike. People sign in through identity providers, and Nexus has no
login of its own any more. Administrators give access with roles and policies
at the platform, at each organization and at each workspace.

**Upgrading an existing install:** read
[Upgrade to the permission system](/capabilities/upgrade/permission-system),
and upgrade to `naas-abi` 3.7.1 and `naas-abi-core` 3.3.1 (2026-11-09) or
later: 3.7.0 cannot move an install from an earlier version in one start.

## Packages

| Package | Version | What |
|---|---|---|
| `naas-abi-core` | 3.3.0 | IAM, enforced by every kernel service; identity providers; engine tokens, service keys, the broker's auth callout |
| `naas-abi` | 3.7.0 | Nexus on IAM: Roles & permissions, View as, Platform Settings › Users, sign-in through providers |
| `naas-abi-cli` | 3.3.0 | `abi iam`, `abi user migrate`, `abi dev code`; the built-in provider under `abi dev up` and in the Docker stacks |
| `naas-abi-sdk` | 0.3.0 | Modules on service keys, permission manifests, delegations, their own actions and containers |
| `naas-abi-proto` | 0.3.0 | The IAM contract (`abi.iam.v1.*`) |
| `naas-abi-idp` | 0.1.0, new | The built-in identity provider: sign-in with a code it mails |

Upgrade them together, with each module's `naas-abi-sdk`.

## What's new

- **Deny by default, everywhere.** Every kernel service, data services and
  runtime services alike, and every Nexus route checks the caller's policies
  before it acts. Nothing is allowed without an Allow, an explicit Deny wins,
  and no account skips the check, the engine's own and the platform admin
  included. See [Security](/developers/architecture/security).
- **Roles & permissions.** AWS-style policies, built-in roles (viewer, member,
  admin, owner) at each organization and workspace, groups, service accounts,
  sub-policies, a simulator and an audit log, on the same pages at the
  platform, each organization and each workspace. Features and each module's
  agents, apps, workflows and pipelines are granted by policy, one by one. See
  [Roles & permissions](/capabilities/platform/roles-and-permissions).
- **View as.** An administrator sees Nexus as someone they gave access to,
  read-only, for 15 minutes at most. See
  [View as another person](/capabilities/platform/view-as-another-person).
- **Platform Settings › Users.** Invite, rename, deactivate or delete an
  account, and set the platform admin. See
  [Manage platform users](/capabilities/platform/manage-platform-users).
- **Sign-in through identity providers.** People sign in at an OpenID Connect
  provider the engine trusts: the built-in one, which mails a 6-digit code, or
  your own (Okta, Microsoft Entra ID, Zitadel, Keycloak). An invitation can make
  the person exist at the provider, and a provider's groups can carry roles. See
  [Choose an identity provider](/capabilities/platform/choose-an-identity-provider).
- **Personal API keys.** A script calls Nexus as you, never beyond your rights,
  and a key can be narrowed further. See
  [Create a personal API key](/capabilities/platform/create-a-personal-api-key).
- **Engine tokens.** ES256, ten minutes at most, verifiable against the
  engine's published keys; token exchange makes narrower ones.
- **Modules are principals.** Each remote module has its own service account
  and key, submits a permission manifest an administrator approves, narrows or
  rejects, and gets broker subjects from that policy only. A module may declare
  actions of its own. See
  [Approve a module's permissions](/capabilities/build/modules/approve-module-permissions).

## Breaking changes at a glance

- Nexus has no login of its own: password, magic link, reset and signup are
  gone, and everyone signs in again after the upgrade. `abi user migrate`
  moves the old accounts to the built-in provider.
- The role and feature matrix, the per-role feature flags and the workspace
  on/off switches for agents, apps and workflows are replaced by policies. The
  upgrade moves them once and keeps everyone's access, except that the platform
  admin now reaches what a workspace had turned off.
- `NATS_JWT_SECRET`, module keys (`abi module key`, `ABI_MODULE_KEY`),
  `ABI_SERVICE_TOKEN` and the broker users `abi` and `module` are gone: modules
  log in with service keys, and the broker has the users `engine` and `auth`
  and an auth callout. `nats.jwt_secret` is refused.
- `secret_key` signs and encrypts nothing: workspace secrets move to their own
  key, `NEXUS_SECRETS_KEY`.
- A module on an older `naas-abi-sdk` breaks behind the auth callout.

The steps: [Upgrade to the permission system](/capabilities/upgrade/permission-system).
The decisions behind the release:
[Identity and authorization](/developers/adr#identity-and-authorization).
