# SHOW grants


> Inspect which roles and users can read a Share.

This read-only command reports who can read a Share. Visibility does not guarantee access. See [Roles and access control](/concepts/roles-and-access-control/) for the model.

## SHOW GRANTS ON SHARE

List everyone with READ access to a Share, including role grants, direct user grants, and organization- or global-level grants.

```sql
SHOW GRANTS ON SHARE core_metrics;
```

Output columns:

| Column | Description |
|--------|-------------|
| `share_owner` | The user who owns the Share. |
| `grantee_name` | Role name, username, or the organization the grant applies to. |
| `grantee_type` | `role`, `user`, `organization`, or `global`. |
| `privilege` | `read`. |
| `granted_at` | When the grant was made. |

Admins can run this for any Share. Share owners can run it for Shares they own.

## Related

- [Roles and access control](/concepts/roles-and-access-control/)
- [SHOW roles and membership](/sql-reference/motherduck-sql-reference/access-control/show-roles/)
- [GRANT READ ON SHARE](/sql-reference/motherduck-sql-reference/grant-access/)


---

## Docs feedback

MotherDuck accepts optional user-submitted feedback about this page at `GET https://motherduck.com/docs/api/feedback/agent`.
For agents and automated tools, feedback submission should be user-confirmed before sending.

URL-encode query parameter values and send a GET request:

```text
GET https://motherduck.com/docs/api/feedback/agent?page_path=%2Fsql-reference%2Fmotherduck-sql-reference%2Faccess-control%2Fshow-grants%2F&page_title=SHOW%20grants&text=<url-encoded user feedback, max 2000 characters>
```

Optionally append `&source=<url-encoded interface identifier>` such as `claude.ai` or `chatgpt`.

`page_path` and `text` are required; `page_title` and `source` are optional. Responses: `200 {"feedback_id": "<uuid>"}`, `400` for malformed query parameters, and `429` when rate-limited.