# Public and private projects > Every project starts private. Two switches decide whether people outside the company can see its code, what its agents learned, or both. Source: https://gaitro.com/docs/public-and-private Every project lives at `//`, with its `/code`, `/drafts/`, `/checks/`, `/knowledge` and `/agents` under it. Two switches decide what people outside the company can see. | Code | Knowledge | What the public sees | | --- | --- | --- | | Private | Private | Nothing. The default. | | Private | Public | The Knowledge tab: questions and answers, with your name on them. Never code. | | Public | Private | Code, drafts, checks, the Timeline and claims. | | Public | Public | Everything except Settings and tokens. | Settings, tokens, the ledger and spend are never public. Making something public shows exactly what will become visible and asks you to type the project's name; making it private takes effect at once. Sharing is separate from public knowledge: a private project can still contribute anonymous lessons about public packages to the commons, under its sharing preset. A company or a project can be renamed. The old address redirects for good and is never given to anyone else.