Roadmap & Future Architecture

🗺️ Roadmap & Refactors

This document outlines the planned architectural changes and refactors for the frontend, derived from the project’s backlog.

⚠️ Important for Developers

These items represent areas of the codebase that are subject to change. When working in these areas, please consult with the tech lead or strictly follow the patterns described here to avoid conflicts with future refactors.

🏗️ Architectural Refactors

1. Router & Access Control

• Status: ✅ In Progress
• Goal: Standardize role-based access using constants.
• Details: Refactoring router core to use constants for tenants and admin roles. Removing the superadministrator role as it is deprecated.

2. View-Co-located Components

• Status: 📅 Planned
• Goal: Improve modularity.
• Details: Move components specifically used for flows (src/components/workflow/*) into their respective view folders (e.g., src/views/workspace/components/).
• Why: Reduces global namespace pollution and makes feature-folders self-contained.

3. Tenant-Centric Connections

• Status: 📅 Planned
• Goal: Decentralize connection management.
• Details: Move connection (service) management to the Tenant level.
• Implication: Admins should check connections but not edit them directly. To edit, they should clone the connection into a management company.

4. Global Flows as Templates

• Status: 📅 Planned
• Goal: Clarify the purpose of “Global Flows”.
• Details: Global flows should be non-executable templates. They serve as blueprints that tenants can clone and instantiate.

5. Dynamic Auth Nodes

• Status: 📅 Planned
• Goal: Context-aware authentication.
• Details: The flow builder should show different Authentication Nodes depending on the selected Connection Type.

📝 Other TODOs

• Improve service environment determination (Development vs Production).