Let Agents, and Team of Agents access all folders
under review
eddis
So I can create agents and teams in ever folder within a workspace, I think agents created on the top folder should be able to access all child folders.
And when you are in one of the child folders, you should be able to access all agents in a higher level.
What I want is to not need to create the same agent for every folder, I think that is a waste of time and makes the agent list on the right very ugly.
Log In
j
jiawei.kek
Merged in a post:
Fundamental AI Agent Suggestion
w
wealth_vision
Please allow the ability for other workspaces, folders, or projects to use AI Agents from another workspace, folder, or project. Instead of specifically associating AI Agents with the place it was created, consider having one big AI Agent pool and when you want to use an AI Agent then you simply just select it. Am I missing something? I know I can copy AI Agents into another area but then it can be tough to differentiate them.
w
wealth_vision
Yes, that would be amazing. A few examples, I own several businesses and have several workspaces for those businesses (just for me) we well as my personal workspace. Essentially all of my workspaces could use an analysis agent, an email writing assistant, a marketing agent, a content creation agent, an task management agent, etc... I spend a ton of time loading up the knowledge base of an agent with great information, sources, instructions, custom commands, etc... and then I can't use it in another area so I have to duplicate that work all over again. I know you can copy an agent but I don't really want to have Task Agent 1, Task Agent 2, Task Agent 3, etc... also, it slows me down when I build AI Agents at the Home folder level and then a new folder in the same workspace just below it can't access it unless I copy it. Could also be a really cool feature to just let users choose to turn on or off as well as an associated memory feature. That way if I choose to use the same agent in a few folders within a workspace, it can learn from the other departments and become more helpful... that would be cool! Hopefully that makes sense. Let me know if I can provide additional feedback or examples.
j
jiawei.kek
hi there, would something like this fit your description? https://www.taskade.com/feedback/feature-requests/p/let-agents-and-team-of-agents-access-all-folders
i understand that it would be convenient to have perhaps a hub to access all ai agents regardless of which folder you are currently in. (as of now, they "reside" within each workspace/team.) im curious if you have any specific scenarios where you see yourself using such a feature?
thanks for bringing this up!
universaldesignz
Granular privilege control makes it simple to manage access just right, ensuring everyone has only the permissions they need for their roles and tasks, whether that's for a department, several team members, individuals, or clients.
Narek Zograbian
Merged in a post:
Streamlining AI Agent Knowledge Management with Tag-Based Access
abeant
User Story:
As a Taskade user managing a workspace with multiple verticals and AI agents, I find it cumbersome to manually assign new projects and documents to each agent whenever they are created. I need a more efficient system that allows agents to automatically access relevant projects and documents without repetitive manual configuration.
---
Feature Requests:
- Tag-Based Project Access for AI Agents:
Description:
Allow AI agents to follow certain tags assigned to projects.Functionality:
- Agents can be configured to automatically access all projects with specific tags.
- When a new project is created and tagged appropriately, agents following that tag gain immediate access.
- Supports combination tags for more granular control (e.g., Vertical Tag+Document Type Tag). (Optional)
Benefits:
- Eliminates the need to manually add each new project to every relevant agent.
- Simplifies agent configuration by setting access parameters once at the onset.
- Enhances organization without requiring a separate folder or library system.
- Tag-Based Document Sharing and Management:
Description:
Enhance document management by allowing editing and tagging of documents for better agent access.Functionality:
Ability to Edit Document Names:
- Enable users to rename documents within agents and the media tab.
- Improves clarity and organization of documents accessible to agents.
Tagging for Documents:
- Allow documents to be tagged similarly to projects.
- Agents following specific tags gain access to relevant documents.
- Facilitates sharing a single document across multiple agents based on tags.
Benefits:
- Streamlines document management and sharing processes.
- Reduces redundancy and ensures agents have the most up-to-date information.
- Workspace-Wide Access Toggle for Agents:
Description:
Introduce a toggle option to grant agents access to all projects within a workspace.Functionality:
- Users can enable a setting that allows an agent to see all current and future projects without manual assignment.
- Ideal for agents requiring comprehensive workspace knowledge.
Benefits:
- Saves time by removing the need for manual updates when new projects are added.
- Ensures consistency and prevents potential oversights in agent access.
---
Use Case Context:
In workspaces with multiple verticals and specialized AI agents, some agents need access to all projects, while others only require information from certain areas. By implementing tag-based access controls, users can:
- Configure Agents Efficiently:Set up agents once with the appropriate tags for access, eliminating ongoing maintenance.
- Maintain Organized Access:Use tags to structure agent access aligned with organizational needs without complex systems.
- Enhance Scalability:Easily scale the system as new projects and documents are added, ensuring agents remain informed.
---
Summary of Benefits:
- Efficiency:Reduces manual tasks related to agent configuration and project/document sharing.
- Flexibility:Offers granular control over agent access through customizable tags.
- Clarity:Improves organization of projects and documents with editable names and tagging.
- Scalability:Supports growth within the workspace without adding administrative burden.
---
While the tag-based approach leverages the existing flexible taxonomy within Taskade, making it a practical solution, we acknowledge that other methods could also streamline the sharing model. Considering options like a "library" system for grouping projects or documents, or implementing folders that function more like traditional folders without the current sharing constraints, could also enhance organization and efficiency. The core objective of this request is to introduce a more efficient way to manage agent access and sharing models, reducing maintenance and simplifying workflows, whether through improved tag management or alternative organizational structures.
---
r
ryantaskade
under review
Narek Zograbian
This seems like an iteration of Agent Context, except you'd want them to be able to access everything. The other aspect seems like you want a space where you can manage all of your agents—similar to My Tasks but My Agents (like the option in Mobile)
eddis
Narek Zograbian That might be true.
What I want is for agents created at the workspace level, not withing a folder, to access and to be accessible from all the workspace.
And then agents created at a folder level to access only that folder.
This is particularly important for automations, I think it is important if I create an automation at the top level in a workspace, I should be able to create a trigger from any folder and any project within it.
Then also from automations, if I am in a folder, I should be able to choose an agent that was created at the top level of that workspace.
I want this parent/child inheritance relationship for agents and automations to avoid repetition.
Narek Zograbian
eddis: Thank you for clarifying and providing more details. This was insightful!
jimcranshaw
eddis 100%! Dont understand why authomations or AI agents are not able to do things in other folders. Like if i have a marketing and a sales folder there is still a lot of interconnection between those areas that Taskade should facilitate.
Narek Zograbian
jimcranshaw: Do you expect agents created in the Home Folder (Workspace) to be available in other folders by default (Marketing, Sales, etc.)?
eddis
Narek Zograbian Yes! That would be amazing. Don't forget Automations.
Automation workflows created in the Home Folder should access subfolders too.
jimcranshaw
Narek Zograbian yes, but thats not my concern here. I want an agent in my home folder to be able to read and write tasks from all folders within that workspace. So for example i say to my Home agent 'find all the tasks in these folders that are tagged with urgent and write them to my 'to do this week' list in my home folder. Agents should be able to see tasks of folders beneath them in the hierarchy and then copy or move those tasks to somewhere else.
Narek Zograbian
jimcranshaw It sounds like your feature request aligns with this one:
Correct me if I'm wrong about that.
Narek Zograbian
eddis Understandable! That'll require a fundamental change in Taskade's structure. However, it does make sense and does feel intuitive.
eddis
Narek Zograbian It would be amazing if you guys do that.
Narek Zograbian
eddis: We'll look into it!