Projects
Give related threads one source of truth, shared instructions, documents, and tasks.
A project keeps work that comes back together. It holds the source, the instructions, the files, the documents, the threads, and the tasks that belong to one thing, such as a repository, a launch, or a product area.
#Create one when the same thing keeps coming up
Make a project when several threads keep referring to the same source or the same decisions. Leave a one-off request as a plain thread. Atoi proposes a project when it notices the pattern, and nothing is filed until you agree.
#Open it under Settings
Open Settings → Your projects and choose the project. It opens on General and lists its pages in the rail. There is no overview and there are no tabs.
| Page | What it answers |
|---|---|
| General | What this project is and who owns it |
| Guidance | The instructions Atoi follows for work in this project |
| Repository | Where the source lives and which branch is the truth |
| Files | Working material you attach for Atoi to use |
| Workflows | The recurring work this project runs |
| Documents | Plans, briefs, and durable writing that live here |
| Members | Who can see and work in the project |
| Decisions | What was decided, and when |
| Danger | Archiving and removal, each behind its own confirmation |
Files are working material you attach. Documents are writing that lives with the project.
#Give it a source and a computer
A project can point at a repository. That is where the truth of the code lives. It can also be given a Computer to run on. The source says what governs the work. The computer says where it can run.
#File threads into it
Filing links a thread to the project. The thread keeps its identity and stays reachable from Ideas and search. Nothing moves or copies, and you can undo the filing.
#Who can see it
Projects live inside a Workspace. Every workspace member can find them. A public page is never an invitation.
Read Tasks next to see how long work reports back.
Was this useful?