Require privacy across your organization's API keys
An organization can require the RN privacy barrier. Understand native API blocking, the 403 error and the protected chat path.
Rota Nacional · Published · Reviewed
When key consent is not enough
A team may need personal data to be processed before it reaches an external model. A connection's transmission consent must not remove that requirement. RN lets the organization record the requirement in its settings.
The choice covers that organization's keys and inference domains. It does not change other companies' settings. Requiring the barrier does not enable conversation storage: processing before transmission and content storage are separate choices.
Enable the organization requirement
Select the organization in the dashboard. Open Settings, then Inference and privacy. Under Privacy barrier, select Edit, choose Require barrier and save. The change requires an organization owner or administrator session.
The management API field is policy.privacy_barrier_required. Updates send the version that was read, so an older edit cannot overwrite another change. Omitting the field preserves its previous value; it does not implicitly authorize disabling protection.
What changes for integrations
When the requirement is enabled, /v1/providers/* returns 403 with code organization_privacy_barrier_required before processing the body or sending it to the provider. This also blocks files, batches and streaming on that path. RN does not attempt to transform a native format that its barrier cannot protect.
Use /v1/chat/completions with a rota/* model and the placeholder, redact or block policy. Monitor mode also returns 403 because it preserves the original content. If an application uses another organization's supplied pool, that pool's requirement also applies. Headers, prompts and key consent cannot remove it.
Frequently asked questions
Does the barrier modify native API bodies?
No. When the organization requires the barrier, native requests are refused. Processing takes place on the protected chat path with the rota/* catalog.
Does this change other organizations' privacy settings?
The change stays with the selected organization. Another organization is affected only when it uses a pool supplied by the organization that imposed the requirement.
Keep reading
Before AI: replace personal data, redact it or block it?
Compare RN personal data policies and choose the right treatment for your workflow. Learn why monitoring is not anonymization.
An AI gateway that preserves your application's model
Centralize AI connections in RN without converting provider request bodies. Understand native endpoints, authorized pools and migration limits.
Manage multiple AI keys with organization isolation
Organize provider connections by company. Learn how pause, weights, consent and file ownership keep customer usage separate.