# API Maker v3.2.0 Release Notes

> What’s new in v3.2.0:- API Maker user tokens shared across admin users

Source: https://docs.apimaker.dev/v1/docs/blog/release-notes/v3.2.0.html

## August 2026

### Changes

- **[FEATURE] :** **Allow API Maker User's Token Across Admin Users** By default an API Maker user's `x-am-authorization` token works only inside the admin user account that issued it. A new root setting lets the same token be reused in your other admin user accounts, so a user who exists in several accounts logs in once instead of once per account.
    - **Where to turn it on :** **Root Settings → Deployment Settings → Security → Allow API Maker User's Token Across Admin Users**. It is a checkbox and it is **off** by default, so nothing changes until you turn it on.
    - **When a token is accepted :** the other admin user account must have an **active** API Maker user with the **same username** *and* the **same password**. If either one differs, the token is rejected as before.
    - **Whose permissions apply :** always the API Maker user of the account **serving the request** — its own groups, roles and permissions. The token only proves who you are; it never carries permissions from one account into another.
    - **Changing a password stops it everywhere :** the token must still be valid in the account that issued it. So rotating that password immediately invalidates the token in **all** accounts at once, in one step.
    - **Nothing else changes :** a token used inside its own admin user account keeps working exactly as it did, whether the setting is on or off.
- **[FEATURE] :** Admin user can change license key of any server from UI directly.