Documentation Index
Fetch the complete documentation index at: https://docs.elitea.ai/llms.txt
Use this file to discover all available pages before exploring further.
What Is a Shared Project Space?
ELITEA users all work inside Projects — isolated workspaces that contain Agents, Pipelines, Toolkits, Credentials, Conversations, Artifacts, and MCPs.
There are three types of project spaces:
| Type | Visibility | Purpose |
|---|
| Private Project | Only you | Personal sandbox for building and testing |
| Team Project | All invited members | Shared collaborative workspace for a team |
A Team Project Space allows multiple users to create, edit, and use agents together. Key benefits include:
- Multiple people can build and improve agents collaboratively
- Shared toolkits and credentials are centralized for the whole team
- All team members can use and reuse each other’s agents
- Consistent workflows and standardized pipelines across the team
- New members immediately access all team-built assets upon joining
- Admins can monitor usage, manage access, and control governance
How to Request a Project Space
Project spaces are created by the ELITEA support team for the next.elitea.ai environment. For other environments, please contact your platform administrator.
For EPAM users on next.elitea.ai, send a request to:
Email: SupportAlita@epam.com
Include the following information in your request:
- Project Code or Initiative Name — the EPAM project code or initiative the space is for ( If you are from Epam)
- Admin name(s) — at least one Admin; multiple admins are allowed and recommended
- Short description — what the project is for and who will use it
- Instance — which ELITEA environment (e.g.,
next.elitea.ai)
Projects for EPAM initiatives are created for free and processed quickly — no additional confirmation is usually required from PM/DM side.
Roles and Permissions
Roles are assigned and managed by project Admins at Settings → Users. Users can hold multiple roles simultaneously — permissions are combined.
| Role | Level | Key Capabilities |
|---|
| Admin | High | Full project access — invite users, change roles, create/edit/delete all content |
| Editor | Medium | Create and modify agents, pipelines, toolkits, credentials; run chats — cannot delete or manage users |
| Viewer | Low | Browse and run existing agents and pipelines — cannot create, modify, or delete anything |
In case user will be assigned multiple roles simultaneously, user will be granted both access.
Admin Responsibilities
A project can have more than one Admin, and an Admin can promote other users to Admin at any time. Admins are responsible for managing their team’s access because they understand the team structure and what permissions each person needs.
If you are not admin and need to add, remove, or change user roles, contact your project Admin directly — do not contact support for routine user management.
Managing Users
Admins manage team members at Settings → Users. The available actions are:
| Action | How |
|---|
| Invite users | Click + Invite Users → enter email addresses → select role(s) → Invite |
| Edit a user’s roles | Click the ✏️ edit icon on the user’s row → update roles → Save |
| Batch-edit roles | Select multiple users → click Edit → update roles → Save |
| Remove a user | Click the 🗑️ delete icon on the user’s row → confirm |
| Batch-remove users | Select multiple users → click Delete → confirm |
For full details, see Users & Roles Settings.
Support will not normally make user management changes on behalf of teams. This is intentional: Admins are best placed to know their team structure and the appropriate permissions for each member.If your project Admin is unreachable and access cannot be managed, contact SupportAlita@epam.com as an exception. Support will evaluate the situation on a case-by-case basis.
Moving Agents Between Projects
If you need to move agents into a newly created project space, ELITEA provides three mechanisms:
| Method | Use When |
|---|
| Fork | Moving within the same ELITEA environment to a different project |
| Export | Backup, sharing outside the environment, version control |
| Import | Loading from a file (cross-environment or from backup) |
For step-by-step instructions, see: