Listing Platform Product Review Sandbox

Atlas HydrationUnited States

Deep implementationADM-001

System health

Healthy

Active users

28

Connected sources

6

Policy changes pending

2

Administration areas

Users & teams

Manage access, teams, and invitations.

Roles & permissions

Control route, object, and action permissions.

Execution registry

Govern the 37 execution definitions.

Templates & knowledge

Manage reusable templates and guidance.

Integrations

Monitor Amazon and research connectors.

Inspect immutable administrative events.

Integration health

Amazon Selling Partner APIHealthy · synced recently

Connected

Brand AnalyticsHealthy · synced recently

Connected

KeepaHealthy · synced recently

Connected

SmartScoutManual upload mode

Manual

Object storageHealthy · synced recently

Connected

Email notificationsHealthy · synced recently

Connected

What this page is supposed to answer

Who can do what?
Which definitions, policies, and integrations power the operating system?
What changed, who changed it, and what downstream behavior did it affect?
What should a Platform Admin decide or understand here?

Why it exists

Administration governs the registries, policies, integrations, permissions, taxonomies, and audit history that keep the platform coherent as it grows. This specific page exists to system administration overview for users, permissions, registry, templates, integrations, taxonomies, and audit/security.

How to use it

Start with the page header to confirm the screen, scope, and review status.
Read the primary cards or table as the operating surface for the current decision.
Use the element info buttons to inspect why a region, component, action, or state exists.
If the page feels wrong, add a Review Mode call-out and then save an explanation update describing what changed and why.

Important nuance

Execution definitions should be governed data, not scattered hard-coded workflows.
Policy changes affect downstream approval, publishing, automation, and permission behavior.
Administrative edits should leave an audit trail because they change how the platform reasons.
This screen follows a governed template so similar workflows remain consistent.
Old and new explanations should both remain available because product decisions are part of the system history.

Current explanation version

Architecture baseline2026-07-16 / Architecture conversation

What: Initial product guidance for Administration Home.

Why: Generated from the Listing Division architecture, screen map, navigation spec, execution ontology, component system, and sandbox implementation.

Guidance: Administration Home should system administration overview for users, permissions, registry, templates, integrations, taxonomies, and audit/security.

admin navigationhealth/statuspending changessecurity alertsconnector status

Architecture signals

Screen map: ADM-001Surface: AdministrationTemplate: DashboardPageTemplateEntities: user, integration, audit_eventStates: Healthy, Warning, Critical