Organize projects and repositories
Keep your company's products or client projects in one structured workspace.
Three levels, each answering a different question. A workspace says whose this is — a product, a department, a client. A project says what you are working on. A repository says what it is built from. Fifteen repositories in one flat list is not a structure; this is what lets you say "these four are billing" and hand somebody the right part.
Create a workspace for a product, a department or a client.
Add a project inside it for the thing you are working on.
Connect the repositories that project is built from.
Open a repository to have it read, and use the project's Documents and Work tabs from there.
The three levels are fixed: nothing nests deeper, there are no tags or labels, and a repository belongs to one project at a time. Each repository is read on its own, and a project with two or more is also read as one product — one drawing of where they meet and one question over all of them. There is no limit on the number of repositories on any plan; the credit balance bounds what gets read.
See it on a real product
Eight models are published in full and open without an account. Ask one of them the question this page is about.