Role-Based Project Access Control Within Shared Workspaces

🚀 Feature Request: Role-Based Project Access Control Within Shared Workspaces

Problem:
Currently, AgenticFlow credit limits and project visibility are set at the workspace level. When I invite team members into a shared workspace, they gain access to all projects. This includes sensitive experiments, in-progress workflows, or personal prototypes. It creates friction when collaborating with clients, external contractors, or teammates working on separate tasks.

Proposed Solution:
Enable workspace owners to:

• Create Project Folders within a shared workspace

• Assign access permissions (View or Edit) on a per-project basis

• Allow invited users to use the shared workspace credit without requiring them to purchase their own

• Keep internal or confidential projects hidden unless explicitly shared

Why this matters:

• Supports modular collaboration and protects sensitive work

• Allows for secure client-facing deployments inside a single workspace

• Makes workspace credit sharing more scalable and controlled

Who benefits:

• Agencies managing multiple client projects

• Startups with different departments using one workspace

• Freelancers or small teams collaborating with part-time contributors

• Educators guiding student projects in one platform

If you want to see AgenticFlow evolve into a more secure and flexible collaboration tool, please give this a vote. Every upvote helps prioritize this improvement.