Projects
A project is a grouping for related documents. It lives in the left rail of the dashboard, under My Documents and inside each team.
On this page
How do I group documents into a project?
Create a project from the rail’s “+ New project” button, with an optional emoji and defaults that documents filed into it inherit. One level of nesting is allowed — a project can have sub-projects, but those can’t have their own.
Move documents in or out from a document’s “…” menu or the project’s “+ Add documents” picker. “Unfiled” is the catch-all for documents not in any project; deleting a project moves its documents back to Unfiled rather than deleting them. Personal projects hold personal documents; team projects hold that team’s documents.
What defaults can a project set?
Open Project settings (the gear next to “+ Add documents”, or set everything when you create the project). A project can pre-configure four things for its documents: a source/target language pair, glossaries, style guides, and memory settings. The pickers offer only resources the project’s documents can reach: a team project uses that team’s glossaries and style guides, a personal project the owner’s own (built-in style guides work everywhere).
The two kinds of default reach documents differently:
A document always wins over its project: change any control in the editor’s Memory panel and that document keeps its own choice; the panel says when its values come from the project. Sub-projects inherit any default they leave unset from their parent project, so a document filed in a sub-folder gets the same treatment as one at the top level.
| Defaults | How they apply |
|---|---|
| Language pair, glossaries, style guides | Copied into a document when it is created in the project, or when you pick “Use project defaults” while moving it in. Editing them later leaves existing documents alone. |
| Memory defaults | Read live on every run. They cover whatever a document doesn’t set itself, so editing them re-tunes every document in the project that has no memory settings of its own. |
If a document has several languages, does moving it move all of them?
Yes. Multi-language documents move as one unit — filing any language version into a project, or back to Unfiled, takes all its sibling versions with it. The project’s document count treats that group as a single document.
What happens to a document’s settings when I move it into a project?
Transept asks. When the target project has its own defaults, a prompt offers to keep the document’s current language pair, glossaries and style guides or adopt the project’s — and the choice applies only to that one move. Memory defaults are the exception: they are read live rather than copied, so they start covering the document either way, underneath anything the document sets itself.
Do a project’s memory defaults override my document’s settings?
No. A project’s memory defaults only fill in what a document leaves unset; any control you change in the editor’s Memory panel wins for that document. The one thing that outranks both is a team’s enforced memory policy — see translation memory.
Can I link a project to a client?
Yes. Set the Client field on a project and documents created in it, or moved into it, link to that client automatically; an explicit document-level client is never overwritten. See the CRM hub.
Can I create a project without going back to the dashboard rail?
Yes. The “Move to project…” dialog in a document’s “…” menu can create a new project inline, so you don’t have to set one up on the rail first.
Still stuck? Ask Literess in the app, or write to support@transept.ai.