---
title: "vision.face.consent.manage · OpenVibe.Services"
canonical: "https://openvibe.services/docs/capabilities/vision.face.consent.manage"
updated: null
---

# vision.face.consent.manage · OpenVibe.Services

HTML: [vision.face.consent.manage · OpenVibe.Services](https://openvibe.services/docs/capabilities/vision.face.consent.manage)

# `vision.face.consent.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 (active, first-party).

Read, grant and revoke purpose-scoped face or voice consent on OpenVibe.Vision: GET /api/v1/faces/consents and /consents/text, POST /consents/:feature with the signed current text, and DELETE /consents/:feature, which revokes and erases the template and derived data in one transaction. A person manages only their own record; the record says whose face or voice, the scope, expiry and how it was revoked (vision.consent@1).

- Owner: vision (token audience `openvibe.vision`)
- Version: 1.0
- Status: active
- Visibility: first-party
- Resource constraints: owner
- Quota class: vision-face
- Permissions: vision:face:consent
- Input: [vision.consent-request@1](/docs/contracts/vision.consent-request)
- Output: vision.consent@1
- Events: —
- Implemented by: - `GET /api/v1/faces/consents`
- `GET /api/v1/faces/consents/text`
- `POST /api/v1/faces/consents/:feature`
- `DELETE /api/v1/faces/consents/:feature`

[These routes in the API explorer](/docs/api/vision#cap-vision.face.consent.manage)