> For the complete documentation index, see [llms.txt](https://framework.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://framework.ishare.eu/main-aspects-of-the-ishare-trust-framework/key-functionality/enable-control-over-own-data-through-management-of-consent.md).

# Enable control over own data through management of consent

As described under key functionalities '[facilitate flexible authorisations](/main-aspects-of-the-ishare-trust-framework/key-functionality/facilitate-flexible-authorizations-applicable-in-any-context.md)' and '[enable data exchange based on delegations](/main-aspects-of-the-ishare-trust-framework/key-functionality/enable-data-exchange-based-on-delegations-even-between-unknown-parties.md)', the iSHARE Trust Framework aims to enable parties to grant other parties or persons access to (parts of) their data or services. At least as important is the aim to allow parties to modify or withdraw these access rights to their data or services, whenever they wish. This is called management of consent, and enables full control over own data at any moment in time.

Example:

* In the example described under key functionality '[enable data exchange based on delegations](/main-aspects-of-the-ishare-trust-framework/key-functionality/enable-data-exchange-based-on-delegations-even-between-unknown-parties.md)', Party A hires Trucking Company B to deliver Container X to Party C. Trucking Company B's ERP system asks Party C's ERP system at what time it should deliver the container. Party C's ERP system does not know Trucking Company B, but can check the delegation to Trucking Company B that Party A has registered at Authorisation Registry D. Because this delegation is in order, Party C's ERP system shares a time slot with Trucking Company B's ERP.
  * Now imagine that moments before Trucking Company B's ERP system asks Party C's ERP system for a time slot, Party C revokes Party A's access to requesting a time slot. Consequently, Trucking Company B's request for a time slot gets an access forbidden message; Trucking Company B's request is NOT accepted because Party A, and therewith delegated Trucking Company B, is no longer authorised to ask for a time slot.

Party C, as showcased, remains in full control over its own data and services at any moment in time. This example is detailed under [use cases](/use-cases.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://framework.ishare.eu/main-aspects-of-the-ishare-trust-framework/key-functionality/enable-control-over-own-data-through-management-of-consent.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
