# Permissions

{% hint style="info" %}
Granular permissions require the [Pro edition](/getting-started/editions.md).
{% endhint %}

Advanced SEO adds three permissions under the **Advanced SEO** group:

| Permission          | Description                                                                                     |
| ------------------- | ----------------------------------------------------------------------------------------------- |
| `configure seo`     | Full access to all SEO settings, defaults, configuration, and the SEO tab on entries and terms. |
| `edit seo defaults` | Edit collection and taxonomy defaults, and access the SEO tab on entries and terms.             |
| `edit seo content`  | Access the SEO tab on entries and terms.                                                        |

Super users always have full access regardless of permissions.

## How Permissions Work

### Site Defaults

Only users with the `configure seo` permission can edit site defaults.

### Collection & Taxonomy Defaults

Users need the `configure seo` or `edit seo defaults` permission **and** Statamic's native permission for the corresponding content type. For example, to edit SEO defaults for the Pages collection, a user needs `edit seo defaults` plus either Statamic's `configure collections` or `edit pages entries` permission. Accessing the configuration requires `configure seo` and the native `configure collections` or `configure taxonomies` permission.

### SEO Tab on Entries & Terms

Any of the three permissions grants access to the SEO tab. Additionally, the collection or taxonomy must have its [Editable](/usage/settings-and-defaults.md#configuration) toggle enabled.


---

# Agent Instructions: 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:

```
GET https://advanced-seo.michaelaerni.ch/usage/permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.