Projects
A project keeps one client or campaign's work together — and, when you attach it, teaches Endless everything it knows about them.
The product describes a project as "A space for each client or campaign. Keep their assets, transcripts, and chats together so Endless always has the right context."
That sentence hides the thing that trips people up. A project does three separate jobs, and doing one never does the others. Once you know which job you're asking for, everything about projects becomes predictable.
Three jobs, kept separate
1. It holds things
Assets, chats, canvases, members and the project's knowledge. This is what fills the project's tabs.
2. It grants access
Linking something into a project lets the project's people read it.
3. It supplies context
Attaching a project to a chat loads its knowledge and its skills into that conversation.
Only the first job shows up in the list: each project wears its reach next to the assets, chats, canvases and members filed under it.
One never implies another. Adding an asset to a project makes it readable by the project's members — and loads nothing into any chat. Mentioning a project in a chat loads its knowledge — and does not file that chat under the project. If you want both, do both.
Who can open a project
You choose the reach when you create it, under "Who can access":
Workspace
"Anyone in your workspace can open this project and contribute."
Private
"Only you and the people you invite."
Either way you can add people to the project. On a private project, that list is the access control. On a workspace project, everyone can already open the page — but the member list still matters, because only members inherit the project's assets into their own Assets library. Being able to browse a project is not the same as having its files filed with yours.
The project's own Assets tab works the other way round: it lists what has been linked into the project for anyone who can open it. So a workspace-reach project is a place to share files, not a place to stash them.
Attaching a project to a chat
Attachment is the context job — the one that actually changes what Endless knows while it works with you.
Attach it
Type @ followed by the project's name in the composer, or pick it from the composer's
add menu. A chip appears above the composer with the project on it.
Confirm what that did
Open the chip and it tells you: "This project's knowledge and skills are loaded into this chat." Context is never silent — if a project is feeding the conversation, you can see it.
It stays attached
You don't re-mention a project every message. Once attached, it stays attached for the rest of that conversation, on any device you open it from.
Detach when you're done with it
Remove the chip — "Remove from chat" — and the project's knowledge and skills stop loading, even if the project was mentioned earlier in the conversation.
A detach is remembered on that device only. Attachment is worked out from the conversation itself, so it follows you everywhere; the removal is a local note on top of it. Open the same chat on another computer or phone and the project comes back attached — remove the chip there too.
Endless can attach a project by itself mid-conversation when the work is clearly about one, and it says so when it does. If that isn't what you wanted, remove the chip.
Each project has one knowledge entry
Every project owns a single, permanent Knowledge entry. The product describes it as "The project's knowledge — kept current by Endless, hidden from the general skills list, and loaded into a chat when you mention this project."
This is the project's memory. When you tell Endless something durable about the client — how their name is written, the tone their posts use, what always needs approval — it saves that rule into the project's knowledge and shows a "Saved to" card naming the project, so you know it happened. Next time you attach the project, it starts from there instead of from nothing.
It is the project's, permanently
The knowledge entry can't be unlinked from its project or deleted while the project exists. It goes when the project goes.
It loads only when attached
Knowledge is inlined into a conversation when the project is attached to it — never into every chat by default.
You can read and edit it yourself from the project's Knowledge tab. It's an ordinary skill underneath, so the same ideas apply — see Skills and knowledge.
Archiving a project
Archiving hides a project from the workspace without deleting anything. Archived ones live in Settings → Archived projects: "Archived projects are hidden from your workspace. Unarchive one to bring it back."
It's reversible
Unarchiving restores the project exactly as it was, keeping its links. It is a way to tidy up a finished campaign, not a way to delete one.
Different from deleting
Deleting a project is a separate, destructive action. Archiving touches nothing inside the project.
The Free plan is the only one that caps how many projects a workspace can have; every paid plan is unlimited. If you hit the cap, Endless says so when you try to create the next one — and archiving doesn't free a slot, because archived projects still count. Deleting one does.
Which one do I want?
| I want to… | Do this |
|---|---|
| Keep a client's files together | Link the assets into the project |
| Let a colleague reach a client's files | Add them to the project as a member |
| Have Endless write in the client's voice | Attach the project to the chat (@ its name) |
| Teach Endless a rule that should stick | Say it in a chat with the project attached |
| Stop a project influencing the current conversation | Remove its chip |
| Get a finished campaign out of the way | Archive it |