# permission.setRecordAccess

> For the complete documentation index, see [llms.txt](https://ensforge.com/llms.txt).

Lets another account edit a name's records, or takes that access back. Options, result, errors and examples for permission.setRecordAccess.

Source: https://ensforge.com/docs/reference/sdk/permission/set-record-access

<ApiMeta kind="Write" stability="stable" since="1.0.0" source="packages/sdk/src/actions/permission/setRecordAccess/index.ts#L64" />

Lets another account edit a name's records, or takes that access back. Resolves once the transaction is submitted.

## When to use [#when-to-use]

Use to let a teammate, bot or app manage some or all of a profile. Use [`setRecordAccessSync`](/docs/reference/sdk/permission/set-record-access#wait-for-the-receipt-with-setrecordaccesssync) to wait for the receipt.

## Details [#details]

- PermissionedResolver: exact setter roles per record (one text key, coin, data key, ABI
  content type or interface), or every setter role with `records: "all"`.
- Public resolvers: a per-name delegate, which can edit every record of the name.
- `revoke` takes the same access back.

<Callout type="warn" title="Gotchas">
- PermissionedResolver roles cover every name on that resolver. Names share a resolver
  with `resolver: "parent"`; give names their own resolver to keep access per name.
- Delegates and `"all"` need `allowScopeWidening: true`.
</Callout>

## Signature [#signature]

```ts
function setRecordAccess(
  client: Like,
  options: setRecordAccess.Options & Write.Options,
): Promise<setRecordAccess.ReturnType>
```

Call it as `ens.permission.setRecordAccess(options)` on a client, or `Actions.permission.setRecordAccess(client, options)`.

## Parameters [#parameters]

| Option | Type | Default | Description |
| --- | --- | --- | --- |
| `name` (required) | `string` |  | ENS name. Normalized automatically. |
| `grantee` (required) | `string` |  | Account that gets (or loses) access. |
| `records` | `Selection \| "all"` | `"all"` | Records in the `record.get` selection shape, or `"all"`. |
| `allowScopeWidening` | `boolean` |  | Confirm grants wider than the listed records (delegates, `"all"`). |
| `revoke` | `boolean` |  | Take the access back. |

Also takes the [write options](/docs/reference/sdk/client#write-options).

## Returns [#returns]

Resolves to `Write.Result`. Submitted transaction hashes and the plan that produced them.

| Field | Type | Description |
| --- | --- | --- |
| `hash` | `Hex` | Hash of the last transaction. |
| `hashes` | `readonly Hex[]` | Every submitted transaction, in order. |
| `id` | `string` | EIP-5792 bundle id when the calls were sent as one batch. |
| `plan` | `Plan` | The plan the write executed: its steps, in order, as they were submitted. |

## Errors [#errors]

| Error | Codes | When |
| --- | --- | --- |
| [`InvalidInputError`](/docs/reference/errors/invalid-input-error) | [`INVALID_NAME`](/docs/reference/errors/INVALID_NAME), [`INVALID_ADDRESS`](/docs/reference/errors/INVALID_ADDRESS), [`INVALID_RECORD_VALUE`](/docs/reference/errors/INVALID_RECORD_VALUE) | invalid input or an unconfirmed widening. |
| [`NotFoundError`](/docs/reference/errors/not-found-error) | [`RESOLVER_NOT_FOUND`](/docs/reference/errors/RESOLVER_NOT_FOUND) | the name has no resolver. |
| [`UnsupportedError`](/docs/reference/errors/unsupported-error) | [`RESOLVER_PROFILE_UNSUPPORTED`](/docs/reference/errors/RESOLVER_PROFILE_UNSUPPORTED) | public keys on a PermissionedResolver. |
| [`UnauthorizedError`](/docs/reference/errors/unauthorized-error) | [`CANNOT_GRANT_ROLES`](/docs/reference/errors/CANNOT_GRANT_ROLES), [`NOT_OWNER`](/docs/reference/errors/NOT_OWNER) | the account may not grant access. |
| [`UserRejectedError`](/docs/reference/errors/user-rejected-error) | [`USER_REJECTED`](/docs/reference/errors/USER_REJECTED) | the user rejects the request. |
| [`WalletError`](/docs/reference/errors/wallet-error) | [`CHAIN_MISMATCH`](/docs/reference/errors/CHAIN_MISMATCH), [`ACCOUNT_NOT_FOUND`](/docs/reference/errors/ACCOUNT_NOT_FOUND) | the wallet is on another chain or has no account to sign with. |
| [`UnsupportedError`](/docs/reference/errors/unsupported-error) | [`WALLET_BATCH_UNSUPPORTED`](/docs/reference/errors/WALLET_BATCH_UNSUPPORTED) | with `mode: "batch"` or a paymaster when the wallet cannot send calls as one batch. |

It can also fail with the errors every write can (`Errors.WriteError`: the common errors plus `InsufficientFundsError`, `TransactionError`, `UnsupportedError`, `UserRejectedError`, `WalletError`).

See [How errors work](/docs/sdk/errors-explained).

## Examples [#examples]

<Tabs groupId="api" items={["Client","Standalone","Effect"]} persist>
<Tab>
```ts title="Letting an app edit a text record"
const { hash } = await ens.permission.setRecordAccess({ name: "alice.eth", grantee: "0xB0b0000000000000000000000000000000000000", records: { texts: ["url"] } })
```
</Tab>

<Tab>
```ts title="Letting an app edit a text record with a standalone call"
import { Actions } from "@ensforge/sdk"

await Actions.permission.setRecordAccess(ens, { name: "alice.eth", grantee: "0xB0b0000000000000000000000000000000000000", records: { texts: ["url"] } })
```
</Tab>

<Tab>
```ts title="Letting an app edit a text record in an Effect program"
import { Actions } from "@ensforge/sdk/effect"

yield* Actions.permission.setRecordAccess(ens, { name: "alice.eth", grantee: "0xB0b0000000000000000000000000000000000000", records: { texts: ["url"] } })
```
</Tab>
</Tabs>

## Plan methods [#plan-methods]

Each method takes the same options as `permission.setRecordAccess` and sends nothing. See [Preview before sending](/docs/sdk/preview-before-sending).

| Method | Description |
| --- | --- |
| `permission.setRecordAccess.prepare(options)` | Builds the plan without sending anything. |
| `permission.setRecordAccess.simulate(options)` | Simulates the plan with `eth_call`, reporting each step. |
| `permission.setRecordAccess.estimateGas(options)` | Estimates the gas and ETH the plan needs. |

## Wait for the receipt with `setRecordAccessSync` [#wait-for-the-receipt-with-setrecordaccesssync]

Lets another account edit a name's records, or takes that access back. Resolves once the receipt is in.

Use when the next step depends on the change being on-chain.

`permission.setRecordAccessSync` takes the same options plus [`confirmations` and `timeout`](/docs/reference/sdk/client#sync-options).

Resolves to `Write.SyncResult`. Receipts plus the submitted hashes and plan.

<Tabs groupId="api" items={["Client","Standalone","Effect"]} persist>
<Tab>
```ts title="Letting an app edit a text record and waiting"
const { receipt } = await ens.permission.setRecordAccessSync({ name: "alice.eth", grantee: "0xB0b0000000000000000000000000000000000000", records: { texts: ["url"] } })
```
</Tab>

<Tab>
```ts title="Waiting with a standalone call"
import { Actions } from "@ensforge/sdk"

await Actions.permission.setRecordAccessSync(ens, { name: "alice.eth", grantee: "0xB0b0000000000000000000000000000000000000", records: { texts: ["url"] } })
```
</Tab>

<Tab>
```ts title="Waiting in an Effect program"
import { Actions } from "@ensforge/sdk/effect"

yield* Actions.permission.setRecordAccessSync(ens, { name: "alice.eth", grantee: "0xB0b0000000000000000000000000000000000000", records: { texts: ["url"] } })
```
</Tab>
</Tabs>

## See also [#see-also]

- [`permission.get`](/docs/reference/sdk/permission/get) to read access