How AI Employees Relate to Projects
Audience: front-end end users
Belong to the current project
AI employees are not one shared set of bots at account level. They sit under the current project. Each project can have its own:
- AI employees, nodes, and enterprise resources
- Skill, SOP, tools, and MCP
- Sessions, tasks, and Token usage
After the same login switches to another project, you enter that project’s AI work environment. This is not a filter on the same list.
In short:
One project is one independent AI team and business environment.
Different projects usually need different roles, tools, and resources. The project boundary keeps those abilities separate. See [Explanation of "Projects"]
Difference from human members
A project can have both human members and AI employees. Both can take part in work, but they are not managed in the same place.
| AI employee | Human member | |
|---|---|---|
| Entry | AI Employee / AI Employee Management | Human Resources |
| Object | AI work roles and resource setup | Project members (Membership) |
| Ability source | Skill, SOP, tools, MCP, enterprise resources | Role, permissions, and human work ability |
| How they work | Receive tasks, call tools, follow a process | Manage, collaborate, approve, and do manual work |
If member-type filters include a “bot” label, that still does not replace create and mapping in this module. How people join a project: [How HR Relates to Project Members]
People and AI together
AI employees are not a replacement for project member management. The usual pattern is human members + AI employees: people set goals, confirm, or approve; the AI queries, organizes, or runs work from its setup.
Whether you see AI Employee Management and its submenus depends on the project role and plan.
Other business modules
With permission, an AI Employee can enter modules already opened in the current project, get information, call tools, and finish work. Whether it can use a module depends on the tools, Skill, SOP, MCP, and resource permissions given to it.
So it is not a chatbot outside the enterprise system. It is an intelligent working member inside the project’s business environment.
Common links include:
- System chat: the product includes four built-in channels — WhatsApp, LINE, wechat, and AIchat. Other chat apps can be added. Turning on hosting often needs an AI employee and a session
- Enterprise Docs / site building: you can reference docs in chat, or use the AI helper on a business page
In short
An account can join more than one project.
A project is one independent company or business environment.
Inside a project there are human members, AI employees, ability setup, plus sessions and tasks.
The project decides which business environment the AI Employee belongs to.
The AI Employee decides who does the work.
Skill, SOP, tools, and MCP decide how it can work.
Sessions and tasks decide what it is doing now.