## **📋 What OTTO can show about past changes**

OTTO does not have a customer-facing activity log that lists every action in an account over the last week or the past six weeks, and past actions cannot be replayed from a log inside OTTO. Deploy and undeploy events are stored as deployment history, including who deployed, when, the issue type, and the affected URLs. That history can be filtered by date, including the last week or six weeks, but it is used for reporting and the Work Summary export rather than shown as an activity log.

You can still review the current state of your OTTO data and use reporting that is available today.

## **📊 Export current OTTO data and use Reports**

To keep a record of what is in the project now, use the Export menu on the OTTO project. Work Summary opens a Google Sheet of completed tasks and deployment history. OTTO Suggestions emails a Google Sheet of the current suggestions. Neither file is a CSV or Excel download, and neither is a history of edits over the last six weeks.

1. Export from the OTTO project’s Export menu. Work Summary opens a Google Sheet, and OTTO Suggestions sends a Google Sheet by email. There is no direct CSV or Excel download.
2. Save the file with a clear date in the name so you can compare later exports yourself.
3. OTTO does not have a Reports screen. When a project has one, the header shows a Performance Report card that opens Report Builder. The Export menu also has Work Summary, which opens a Google Sheet of completed OTTO tasks.

You can export Work Summary again when you need another snapshot. Comparing those Google Sheets can show what changed between exports. OTTO also keeps deployment history of deploy and undeploy events, but that history is not shown as an activity log in the product.

## **⚙️ Shopify scopes for CMS Connector publishing**

For CMS Connector publishing, connect Shopify with an Admin API token or a custom app that has Admin API access. The connection needs the Admin API content scopes read\_content and write\_content. If access is denied, grant the required Admin API scopes and reconnect. The product does not offer a choice between Storefront scopes and an all-scopes option.

For blog publishing, these Admin API scopes are required:

- **read\_content**
- **write\_content**

If publishing fails, confirm the app or custom app is using Admin API access with those content scopes, then reconnect or update the scopes in Shopify and try CMS Connector publishing again.

## **💬 If you still need help**

If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.