---
title: "website.domain.manage · OpenVibe.Services"
canonical: "https://openvibe.services/docs/capabilities/website.domain.manage"
updated: null
---

# website.domain.manage · OpenVibe.Services

HTML: [website.domain.manage · OpenVibe.Services](https://openvibe.services/docs/capabilities/website.domain.manage)

# `website.domain.manage`

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, public).

PLANNED for OpenVibe.Website Connect (audience openvibe.website, owner or project scope): attach, verify or remove a custom domain for a share with POST /api/v1/domains from a domains.proposal@1. Connect delegates the DNS change to OpenVibe.Domains — the owner approves it in the Action Center, Domains writes the TXT/CNAME and answers with the applied proposal — and Connect never writes DNS itself or asks for the provider credential. Apex CNAME flattening, Cloudflare for SaaS and the certificate path are CON-2 decisions; the first proof uses a single-label openvibe.website host only.

- Owner: connect (token audience `openvibe.connect`)
- Version: 1.0
- Status: planned
- Visibility: public
- Resource constraints: owner, project
- Quota class: website-domain
- Permissions: website:domains:manage
- Input: [domains.proposal@1](/docs/contracts/domains.proposal)
- Output: domains.proposal@1
- Events: —
- Implemented by: - `POST /api/v1/domains`

[These routes in the API explorer](/docs/api/connect#cap-website.domain.manage)