# Sponsor

Some organisations may support the digital commons without contributing directly to it, for example financially through a donation or grant, or through reputation by promoting the tool's uses.

## Risks addressed by the role

### Lack of means

If the digital commons does not have its own business model, the absence of sponsors can be fatal since the role of [operator](/3-roles/3-operateur.md) is difficult to fulfill without financial remuneration. In the case of contributory commons, the absence of an operator makes the structure extremely fragile since the availability of the service is not guaranteed. This puts at risk the capture of value by the [users](https://github.com/MattiSG/livre-blanc-communs-numeriques/blob/traduction/3-roles/1-communaute/README.md)' contributions, and therefore ultimately the provision of the service itself.

## Legal Form

These organisations can be of different natures:

* [Public stakeholders.](https://github.com/MattiSG/livre-blanc-communs-numeriques/blob/traduction/1-concepts/2-action_publique/README.md)
* Non-profit stakeholders under private law (associations, foundations, etc.).&#x20;
* Profit-making stakeholders under private law.

## Retribution

As with contributors, it is useful for the sustainability of their support that sponsors feel acknowledged for their participation. In all cases, they can be rewarded in terms of reputation by having their name and logo put forward. They can also be rewarded with decision-making power through participation in certain governance bodies. In this case, care must be taken to respect the commons to ensure that the support does not outweigh the contribution.


---

# Agent Instructions: 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://commons.mattischneider.fr/3-roles/5-sponsor.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.
