A: Hey there!

Fantastic to have you on board with Tier 4 and the Multi-Agent Add-On pre-order – that's a great setup for your micro-business! And looking forward to our call soon.

Let's clarify how team access and workspace management currently work in AgenticFlow, and how you can manage permissions for your staff:

1. Workspaces & Creating New Ones:

Your AppSumo Tier 4 purchase grants you one primary workspace.

The "Add Workspace" button: You might have noticed this button. For a period during and shortly after the AppSumo launch, we've sometimes temporarily rate-limited or controlled direct creation of additional brand new workspaces from the UI to manage initial onboarding and prevent abuse while we scale. If you have a critical need for a completely separate second workspace (which would typically be for a distinct business entity and require its own plan/LTD code), please discuss this with me on our call.

2. Team Members & Access within a Single Workspace (Your Current Setup):

When you invite your staff members to your Tier 4 workspace (you have 25 user seats), they currently gain access to see and use all agents and workflows created within that workspace.

Preventing Accidental Changes (The Challenge): You're absolutely right to be concerned about staff potentially changing or deleting critical workflows/agents if everyone has broad edit access. This is a common need for growing teams.

3. Best Current Approach for Controlled Staff Access - "Share for Use" (Not Edit):

While we don't have granular, folder-level, or per-agent/workflow edit permissions within a single workspace yet (this is a more advanced feature we're tracking for the roadmap), here's how you can give staff access to use agents/workflows without them being able to edit the core setup:

- Build & Finalize: As the Owner/Admin, you build and thoroughly test your core agents and workflows.
Share for Execution:

- For Agents (Chatbots): You can "Publish" an agent and provide your staff with the shareable preview link or embed the agent on an internal webpage/tool they use. They can interact with the agent (ask it questions, trigger its functions) but cannot access the agent's backend settings or edit its prompts/tools.

For Workflows: You can "Share" a workflow. This also provides a link where users (including your staff, if you give them the link) can input data and run the workflow, but they cannot see or edit the workflow's internal nodes and logic.

API Keys for Triggering (More Controlled): For very specific tasks, you could have workflows triggered via an API call. Your staff might use a simple internal form or tool you build that, on submission, calls the AgenticFlow API to run a specific workflow with their input, again without them ever touching the workflow's design.

Educating Your Team:

Clearly communicate to your staff which agents/workflows are "for use only" via shared links/embeds versus any they might be designated to help test or provide feedback on (perhaps by cloning them first).

In Short:

Your Tier 4 is one primary workspace. Adding team members gives them access to see/use items within it.

To prevent staff from editing/deleting your core automations, share agents and workflows with them via their public "run" or "preview" links/embeds rather than having them navigate directly through the builder interface for day-to-day use of finalized tools.

Granular edit permissions within a workspace is a more advanced feature we're looking at for the future.

Let's definitely discuss your specific team structure and needs on our call, and we can strategize the best way to set this up securely and efficiently for your staff!

Looking forward to it,
Sean