Workflow-first MVPDocs Center liveHelp routes reserved

Team

Team now acts as the front-end workbench for future membership, project scope, role boundaries, and execution permission checks. The data is still scaffolded, but it now flows through a shared workbench service boundary and includes empty and error demos for testing.

Help Center Docs Center

Team Workbench

Team is now framed around real roles and future permission gates

The page is still sample-backed, but it now models who owns the workspace, who can operate the platform, and where future RBAC checks must attach before execution begins.

Service boundary: module-1-shared-workbench-service

State demoLive Empty Error

Team scaffold in code

Owners

Active members

Invites pending

Members

Keep project ownership and action scope visible before RBAC goes live.

MemberRoleStatusScopeLast active

Selected member

qq260316514@gmail.com

all projects

Active

Role

owner

Role note

Owns billing, product direction, and all project-scoped objects.

Seed owner and highest privilege for the current MVP. This account anchors platform-level decisions before public auth exists.

Access scope

Workflows

Profiles

Targets

Runs

Usage

Team

Future developer console

Next permission ladder

Identity and membership

Start with who the user is, then whether the user belongs to the account and project.

Action scope

Check workflow ownership, registry ownership, and allowed mutation scopes before execution.

Commercial gate

Credit availability comes after identity, membership, and plan capability checks.

Org and RBAC Data foundation Module roadmap

Invite flow next

The next slice after RBAC data modeling is a real invite flow, seeded owner enforcement, and project-scoped membership reads from D1.