> For the complete documentation index, see [llms.txt](https://cifer.gitbook.io/cifer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/web2-integration/permits-and-delegation.md).

# Permits and delegation

Delegates and permits let an owner authorize another principal without transferring ownership.

## Delegation

A delegate receives ongoing access according to the secret's authorization state. Use it when a stable service or collaborator needs decryption capability. Removing the delegate stops future authorization but cannot recall plaintext already revealed.

## Permits

A permit represents more explicit delegated authorization and can support narrower application workflows. The public Web2 API exposes a dedicated `web2.permit` namespace for creating, inspecting, and using permit-based access.

## Design checklist

* Identify the grantor, grantee, secret, environment, and intended action.
* Prefer the minimum scope and duration supported by the integration.
* Record when and why access was granted.
* Make revocation visible and auditable.
* Revalidate authorization when a long-running job completes.
* Never imply that revocation deletes copies previously made by a recipient.

{% hint style="info" %}
The source SDK site publishes a permits page but omits it from its sidebar. It is included here because permits are part of the public Web2 SDK surface.
{% endhint %}

For exact functions and types, use the [generated permit namespace](https://sdk.cifer-security.com/docs/api/namespaces/web2.namespaces/permit).


---

# 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, and the optional `goal` query parameter:

```
GET https://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/web2-integration/permits-and-delegation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.