Sync Data (Suite Parent)

VIDEO WALKTHROUGH

Sync Data — Suite Navigation: setup guide

1:55

Recorded on version 1.0.2 · Narrated walkthrough · English captions

Jump to a chapter 6 chapters

1. 0:00Set up Sync Data — Suite Navigation
2. 0:18Find the shared Sync Data menu
3. 0:36Choose the module that owns the data
4. 0:56Locate routing and schema tools
5. 1:15Grant only the permissions needed
6. 1:35Your setup checklist

Read the full video transcript

Sync Data — Suite Navigation 1.0.2 — Magento Admin setup

00:00:00 — Set up Sync Data — Suite Navigation
Welcome to the Agentic Ecom Sync Data — Suite Navigation guide. We'll use Magento Admin to review the setup and explain the handoff to your headless storefront. This walkthrough covers stable version 1 point 0 point 2 and assumes the extension is installed.

00:00:18 — Find the shared Sync Data menu
Open the Agentic Ecom menu and choose Sync Data. This small parent module is installed as a dependency of the sync extensions. It provides the shared menu and permission branch. There is no enable switch, configuration form or data-sync operation of its own.

00:00:36 — Choose the module that owns the data
CMS Block Bundle and CMS Page Bundle handle content. Product Shell Bundle handles product shells, and Global Data Bundle handles store-wide information. Open the tool that matches your source change. The shared menu keeps these separate operations together without turning them into one bulk sync.

00:00:56 — Locate routing and schema tools
The same menu includes URL Rewrite Bundle for route snapshots and Schema Explorer for the available Graph Q L fields. Refresh the relevant Magento snapshot or schema, then use the corresponding Astro Admin sync. You do not need to run every tool after every edit.

00:01:15 — Grant only the permissions needed
Administrators assign access under System, Permissions, User Roles. The Sync Data parent groups the child tools, so a role can be granted the tools it needs. Test the role using a separate administrator account. Removing this dependency while keeping its child modules is not a supported way to hide the menu.

00:01:35 — Your setup checklist
Your next steps are to use the correct child tool, assign suitable admin permissions, sync in astro then verify the result. Use a staging store for the end-to-end check. The complete installation and integration reference is at user guides dot Agentic Ecom dot net.

Download videoEnglish captionsDownload transcript

Sync Data is the small infrastructure module that ties the headless-storefront sync suite together. It owns one thing: the shared “Sync Data” admin menu and its ACL resource. Each of the suite’s data modules attaches its own admin page and permission under this parent, so they appear as one tidy, ordered group in the admin and share a single access-control branch.

Install

Install Sync Data (Suite Parent) with Composer using your AgenticEcom licence key (find it on your My Licences page — one key unlocks every module you own):

# 1. Register the AgenticEcom repository (once per store)
composer config repositories.agenticecom composer https://repo.agenticecom.net
composer config --global --auth http-basic.repo.agenticecom.net <YOUR-LICENCE-KEY> x

# 2. Require this module
composer require agenticecom/module-sync-data

# 3. Apply it
php bin/magento setup:upgrade && php bin/magento setup:di:compile && php bin/magento cache:flush

Have the whole platform?

Install every module in one command with composer require agenticecom/suite — see Install the complete suite.

Compatibility

Magento

Check the exact release against your Magento Open Source version.

PHP

Check the exact package requirements and test your PHP version.

Type

Infrastructure — menu + ACL parent only.

Install

Comes in automatically with any sync module.

There's nothing to configure here

This module has no settings, no GraphQL and no storefront behaviour of its own. It exists so the sync modules stay organised and consistently permissioned. You’ll never install it on purpose — it arrives as a dependency of the sync suite.

What attaches under it

Menu leaf	Provided by	What it does
CMS Block Bundle	CmsBlockBundle	Bundles CMS blocks for a headless storefront
CMS Page Bundle	CmsBlockBundle	Bundles CMS pages for a headless storefront
Product Shell Bundle	ProductShellBundle	Pre-warmed product shells (JSON + GraphQL)
Global Data Bundle	GlobalDataBundle	Store config + categories + payment methods
URL Rewrite Bundle	UrlRewriteData	URL rewrites for headless routing
Schema Explorer	SchemaDiscovery	Discover the GraphQL API surface

Why a separate parent module?

One menu, stable order

Each sync module declares its own menu leaf with a fixed sort order, so the group always renders in the same sensible sequence regardless of install order.

One ACL branch

The parent owns AgenticEcom_SyncData::sync_data; every sync module’s view permission hangs off it, so an admin role can be granted the whole suite (or individual tools) cleanly.

Always installed together

Every sync module depends on this parent, so the menu and ACL always exist — no module has to duplicate them, and none can render an orphaned menu item.

FAQ

Do I need to configure Sync Data?

No — it has no configuration. It only provides the shared admin menu and ACL resource that the sync modules attach to. Configure each sync module on its own page instead.

Why is it installed if I only wanted one sync module?

Every sync module depends on this parent so the “Sync Data” menu and its permission branch always exist. Installing any one sync module brings it in automatically — it’s lightweight and has no runtime behaviour of its own.

Can I grant access to just one sync tool?

Yes — because each tool’s permission hangs off this parent’s ACL branch, you can grant an admin role the whole suite or any individual tool from System → Permissions → User Roles. Check exact-release compatibility before deployment.