# Notion API 403 restricted_resource: the integration can see the page but not do that

**TL;DR:** Re-share the page with the integration and grant the capability the call needs (read vs edit vs insert). restricted_resource means the share exists but the permission level is too low for the operation. Check the integration capabilities in Notion settings after re-sharing.

## The error

```
{"object":"error","status":403,"code":"restricted_resource","message":"Access to this resource is restricted."}
```

## Fix it

1. In Notion, open the page, Share, and confirm the integration is listed.
   Expected: The integration appears but with a low capability.
2. Change the share to grant the needed capability (e.g. Can edit for writes).
   Expected: The share now shows the higher capability.
3. Retry the MCP tool call.
   Expected: It succeeds.

## When this applies

Notion MCP calls 403 with restricted_resource on pages or databases that are shared with the integration.

## When this does NOT apply

404 object_not_found means the page is not shared at all; share it first. 401 means the token is wrong.

## Tool compatibility

makenotion/notion-mcp-server, Notion API

## Also seen as

- notion restricted_resource MCP
- Notion API 403 integration
- notion MCP cannot edit shared page

## Why it happens

Notion shares carry capability levels. A page shared as read-only 403s any write call with restricted_resource, which looks like an auth failure but is really a permission level on the share.

## Edge cases

- Database parent pages need sharing too, not just the database.
- Guests and free workspaces have their own capability limits.
- Re-sharing after a permission change is instant; no token change needed.