Permissions

AEO Enhancer requests specific Shopify permissions so it can generate previews, create drafts, write approved outputs, and support rollback.

This page explains what permissions are used for and how the app keeps usage safe.

Principles

AEO Enhancer follows these principles when using permissions:

• Least privilege where possible
• Approval first before any store changes
• Draft then approved separation for content
• Full audit logging and rollback support
• No silent background edits to storefront content

Common permission categories and why they are needed

Your exact permission list may vary by plan or enabled features, but these are the typical categories.

Read store data

Used to:

• Fetch store context like product types and collections
• Determine which surfaces exist for a query target
• Build accurate previews that reflect your catalog

Why it matters

• Content generation should be grounded in real store data, not invented assumptions

Read and write products

Used to:

• Create and store product description drafts
• Write approved product description output to approved storage
• Support rollback by restoring previous values

Important note

• AEO Enhancer should not overwrite your live product description field directly by default. Approved output should be stored in approved locations intended for rendering.

Read and write collections

Used to:

• Store collection description drafts
• Write approved collection description output
• Roll back to previous values if needed

Read and write content like blogs

Used to:

• Create blog draft articles in Shopify
• Publish only when you execute an approved task
• Unpublish or delete content during rollback when applicable

Theme or storefront related access

If you use a theme app extension block, Shopify will also manage installation and theme integration permissions.

AEO Enhancer uses this to:

• Render approved outputs safely on storefront pages
• Avoid rendering drafts unless you explicitly choose to

Metafields

Metafields are used as primary storage for preview, draft, and approved outputs.

This enables:

• Safe separation of draft and approved content
• Reversibility with rollback data
• Deterministic rendering from approved values only

What AEO Enhancer does not do with permissions

Unless you explicitly choose otherwise, AEO Enhancer should not:

• Apply changes without your approval
• Replace your existing live content silently
• Publish content without an approved task execution
• Render unapproved draft outputs on your storefront

Managing access and security

If you are reviewing permissions:

• Confirm your team understands who can approve and execute tasks
• Use Shopify roles to restrict who can install apps and manage themes
• If you remove app access, existing approved outputs stored in metafields may remain in your store until you remove them

Troubleshooting access issues

If you see errors like auth required:

• Use the reconnect flow inside the app
• Confirm you are logged into the correct Shopify store
• Confirm your account has the required role permissions

See Troubleshooting then Common errors for steps.

Related pages

• Policies then Privacy and data
• Core concepts then Approval first
• Core concepts then Tasks
• Troubleshooting then Common errors