# API Token configurable to organisation unit

**URL:** <https://community.netwrix.com/t/api-token-configurable-to-organisation-unit/161632>\
**Category:** Password Secure Ideas\
**Created:** [October 22, 2026, 10:31am UTC](https://community.netwrix.com/t/api-token-configurable-to-organisation-unit/161632 "2026-10-22T10:31:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexej](https://avatars.discourse-cdn.com/v4/letter/a/85e7bf/32.png) [@Alexej](https://community.netwrix.com/u/Alexej)\
**Post date:** [October 22, 2026, 10:31am UTC](https://community.netwrix.com/t/api-token-configurable-to-organisation-unit/161632/1 "2026-10-22T10:31:14Z")

</div>

### What is a one sentence summary of your feature request?

Make API Tokens configurable, so that they are only able to work for configured organisations

### Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

Our company consists of different companies, which all use the password manager for automated processes. To minimise the risk, that a company writes, edits, etc. passwords of another company, we would like to configure the API tokens to only be able to work for configured organisation units

### How do you currently solve the challenges you have by not having this feature?

We currently have to check if the passwords are generated in the correct organisation, but we can’t overview if others were changed.