> For the complete documentation index, see [llms.txt](https://docs.sail.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sail.money/protocol/guides/register-a-mandate.md).

# Register a mandate & appoint a manager

The manager was appointed when the account was created (the `manager` argument to `createAccount` / `registerAccount`). The mandate — what that manager may do — is set by **registering permissions**, each authorized by the Permission Signer's EIP-712 signature.

## 1. Build the RegisterPermission signature

The type string (note the `deadline` field — current kernels include it):

```
RegisterPermission(address account,address permission,uint256 nonce,uint256 deadline)
```

Construct and sign the digest with the Permission Signer key:

```
structHash = keccak256(abi.encode(
    REGISTER_PERMISSION_TYPEHASH,
    account,
    permission,
    signerNonces[account],   // read from the kernel
    deadline
))
digest = kernel.hashTypedDataV4(structHash)   // applies the SailKernel domain
signerSig = sign(digest, permissionSignerKey) // ECDSA or ERC-1271
```

Read the current nonce from `kernel.signerNonces(account)`. The EIP-712 domain is `{ name: "SailKernel", version: "1", chainId, verifyingContract: kernel }`.

## 2. Submit the registration with the fee

```solidity
uint256 fee = governance.permissionRegistrationFee(); // 0 at launch
kernel.registerPermission{value: fee}(account, permission, deadline, signerSig);
```

Anyone may submit this transaction — authority is the signature, not the sender. Excess `msg.value` is refunded. The permission must be a deployed contract, not already registered, and the account must be below `maxPermissionsPerAccount` (default 20).

## Register several at once

To attach multiple permissions under a single signer nonce, sign `RegisterPermissions(address account,address[] permissions,uint256 nonce,uint256 deadline)` (the `address[]` is hashed per EIP-712 §4 — `keccak256` of the ABI-encoded, zero-padded addresses) and call:

```solidity
kernel.registerPermissions{value: fee * permissions.length}(account, permissions, deadline, signerSig);
```

## If the permission needs configuring

Shared templates must be **configured** for the account in addition to being registered. You can do both in one transaction with the `MandateFactory.attach(...)`, which calls `template.configure(...)` then `kernel.registerPermission(...)`. See [Use a shared template](/protocol/guides/use-a-template.md).

## Changing the mandate later

* **Tighten safely:** prefer `replacePermission` (atomic swap to a freshly-configured permission) over reconfiguring in place.
* **Narrow:** `revokePermission` / `revokePermissions`.
* **Stop everything:** `revokeSession` (then `activateSession` to resume).
* **Rotate the agent:** the Safe calls `setManager(newManager)` — this **clears the whole mandate** and you re-register for the new manager.

Each of these is a signed operation that consumes a `signerNonces` value and (for restrictive ops) invalidates the manager's outstanding pre-signed dispatches. See [the lifecycle](/protocol/permissions/lifecycle.md).

Now the manager can act → [Dispatch a transaction within bounds](/protocol/guides/dispatch.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, and the optional `goal` query parameter:

```
GET https://docs.sail.money/protocol/guides/register-a-mandate.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.