Eco Manager Wiki

Appearance

Admin Studio ​

Purpose ​

Admin Studio is the internal super-user application for managing the Eco Manager platform model.

It provides a powerful CRUD and configuration interface across the Universal Entity Platform. It should feel more like a structured knowledge workspace than a traditional database admin panel.

Useful mental model:

text
Notion / Obsidian-style navigation
+
Entity platform CRUD
+
Strict permissions and audit

Who It Is For ​

Admin Studio is for:

  • platform administrators,
  • senior technical users,
  • product owners,
  • implementation consultants,
  • developers during early product development.

It is not intended for ordinary engineer day-to-day workflows. Engineers should use the main Eco Manager frontend for asset directory, credential, commissioning, and remote access work.

What Admin Studio Manages ​

Admin Studio should manage:

  • entity types,
  • entities,
  • hierarchy,
  • groups,
  • property groups,
  • property definitions,
  • property values,
  • tag groups,
  • tags,
  • templates,
  • relationships,
  • saved views,
  • root entity scopes,
  • selected permission assignments,
  • soft-deleted records,
  • audit inspection views.

Core Experience ​

Admin Studio should provide:

  • left sidebar entity/type explorer,
  • command palette,
  • global search,
  • entity detail panels,
  • graph/relationship navigation,
  • property group editors,
  • template editors,
  • tag group editors,
  • hierarchy tree explorer,
  • bulk edit surfaces,
  • soft-delete and restore workflows,
  • audit trail visibility.

What It Must Not Become Initially ​

Admin Studio is not initially a generic low-code builder.

It should not try to let non-developers build arbitrary application logic, backend integrations, automation flows, or custom UI screens in Alpha.

The architecture may support those capabilities in the future, but Alpha should focus on giving trusted users and developers a safe, powerful way to manage the entity platform configuration.

Guardrails ​

Admin Studio must enforce:

  • authentication,
  • role/capability authorization,
  • root entity scope,
  • Vault boundaries,
  • tenant encryption boundaries,
  • audit logging,
  • confirmation for dangerous operations,
  • soft delete by default,
  • explicit purge workflows only for highly privileged users.

Why It Matters ​

Admin Studio turns the Universal Entity Platform into a practical product capability.

Without Admin Studio, every metadata change requires developer intervention.

With Admin Studio, trusted users can configure new asset types, property groups, tag groups, templates, and views while developers focus on application-level workflows, integrations, security, and remote access.