---
title: "connect.policy.write · OpenVibe.Services"
canonical: "https://openvibe.services/docs/capabilities/connect.policy.write"
updated: null
---

# connect.policy.write · OpenVibe.Services

HTML: [connect.policy.write · OpenVibe.Services](https://openvibe.services/docs/capabilities/connect.policy.write)

# `connect.policy.write`

Generated at 2026-11-13 06:25:48 UTC from [`openvibe-contracts v0.419.0`](https://github.com/OpenVibers/OpenVibe.Contracts/tree/v0.419.0) and [`openvibe-sdk v0.161.0`](https://github.com/OpenVibers/OpenVibe.SDK/tree/v0.161.0).

Not grantable to apps (planned, first-party).

PLANNED for OpenVibe.Website Connect (audience openvibe.website, owner or project scope): write one tenant's mesh grants, routes and exit-node setting (PUT /api/v1/connect/policies/:id) from a connect.policy@1. The tenant in the body must be the caller's tenant; a rule or route naming another tenant's device is refused. Exit-node traffic is opened only to this tenant's devices and never to a public share. A write bumps the policy version the devices apply.

- Owner: connect (token audience `openvibe.connect`)
- Version: 1.0
- Status: planned
- Visibility: first-party
- Resource constraints: owner, project
- Quota class: connect-policy
- Permissions: connect:policies:write
- Input: [connect.policy@1](/docs/contracts/connect.policy)
- Output: connect.policy@1
- Events: —
- Implemented by: - `PUT /api/v1/connect/policies/:id`

[These routes in the API explorer](/docs/api/connect#cap-connect.policy.write)