How a project is built
A project is a working area with a key of its own. This page describes the areas it consists of and where each area's content comes from — not how a project is created; that is in Create a project.
The areas of a project
Inside a project the project navigation leads through the areas. Which of them appear depends on what is installed and on the role of the person reading.
| Area | Where the content comes from |
|---|---|
| Overview | the project's start page, written by hand |
| Dashboard | generated from key figures and the risk register |
| Repositories | live from the connected source control system |
| Pipelines | local project pipelines with their run history |
| Project wiki | freely written project documentation |
| Queries | saved queries over the work items |
| Settings | connection, tokens, mounts (maintainers only) |
An area nobody can fill does not appear. That holds even where the plugin behind it is installed: what decides is whether there is anything to show there.
Why no boards appear
A role applies to the project, not to the page
A person's role is evaluated at the project's root point and applies to the whole project. A repository is mounted through the namespace it hangs on — the same permission that governs wiki pages there decides viewing, obtaining and cloning.
There is therefore no second permission system beside the wiki's own. What follows from that for lists and numbers is in Visibility and permissions.
Related topics
- Create a project — namespace, project key, further languages
- Contributing — the ladder of roles and what each rung may do
- Visibility and permissions — what the numbers mean