Build a workspace per domain: sales, marketing, customer support, research. Bundle the prompts, workflows, scripts, connectors, and memory folders that domain requires. The default chat acts as an agent that selects the matching tool and can spin up to 10 sub-agents to run a chain of tasks in parallel.
A project bundles the tools, knowledge, and instructions for one job. Configure it once, share it with your team, and an agent works inside it.
A sales project pulls from Pipedrive and your call transcripts. A marketing project knows your brand voice and social copywriter prompts. A customer success project connects to Gmail and includes your support playbook. A recruiting project pulls from Affinity and your interview notes. Switching projects swaps the entire context (instructions, tools, knowledge, and default model) in one click.
See how Projects organize workAssign prompts, workflows, scripts, MCP connectors, and memory folders to a project, and they stay available. Call them by @ mention, or let Aisle pick them based on the prompt's context. One project holds the prompts, scripts, connectors, and memory for one workstream.
Read about project contentsPut documents in the project's memory folder. Aisle answers questions about them and cites the source file. No vector database or embeddings pipeline required.
Learn about MemoriesToggle a project to Shared, and every org member gets the same tools and instructions without individual setup. Notes, decisions, and file references save to the project's memory folders each time someone uses it, so every new conversation loads the prior context.
Sharing and permissionsThe default chat in a project is an orchestrator. It can decide which tools to use, design tasks and deploy sub-agents to work in parallel.
The default chat in a project judges when to query a memory folder, call a connector, run a workflow, or trigger a follow-up, then runs them in sequence within one response. You describe the outcome. The agent decides which tools to use and in what order.
How Projects work as an agentFor longer jobs, the project agent spins up sub-agents that share its tools and context. Each handles one task: one researches a competitor, another summarizes tickets, a third drafts a section, a fourth checks the dataset. The parent agent stitches the results back together.
See sub-agent runsA project is the surface where Aisle's other features become a single coordinated tool.
Project memory folders feed answers in chat, prompts, and workflows. Drop files in and ask.
Learn moreMulti-step automations that a project agent can call as a tool when the job calls for one.
Learn moreVersioned, reusable prompts the project agent can call as a tool, or your team can run by name.
Learn moreConfigure once. Share with the team. Let the agent and its sub-agents handle the work.