> ## Documentation Index
> Fetch the complete documentation index at: https://docs.a7manager.se/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects and roles

## Projects separate fleets

A **project** is the top-level container. Every piece of operational data in the platform
belongs to exactly one project — every vehicle, component, defect, warranty claim,
measurement and inspection report.

This is what allows one installation to serve several fleets without them ever seeing each
other's data. The separation is enforced on every request, and a user working in one project
cannot reach another project's records at all.

A project has a name, an optional description, and an active flag.

## Access is granted per project

Users do not have global permissions. Access is granted as a **role within a specific
project**, and a user can hold different roles in different projects — or no access at all
to a project they are not assigned to.

A user can also hold **several roles in the same project**. When they do, their
capabilities are the sum of those roles. Someone who is both a Warranty Manager and an
Inspector can do everything either role allows.

## The roles

Roles are deliberately narrow. Each grants one clearly defined set of capabilities rather
than a general seniority level, and they are combined to describe a real job.

| Role                   | What it allows                                                                                                                                                                                                                                                                    |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Project Admin**      | Everything within the project. Bypasses every project-scoped permission check. Cannot grant Project Admin to anyone else.                                                                                                                                                         |
| **Asset Manager**      | Project-wide **read-only** observer. Reads fleet data (Service Book, Wheel, Assets, Defects, Measurements, KPI, Types), warranty and inspections. May write warranty comments and upload warranty documents, but changes no other state. Asset *edits* remain Project Admin only. |
| **Warranty Manager**   | The owner side of warranty work: file, submit, close and reopen claims and groups. Reads the warranty area only.                                                                                                                                                                  |
| **Warranty Supplier**  | The supplier side: investigate, accept, reject. Normally an external party. Reads the warranty area only.                                                                                                                                                                         |
| **Component Manager**  | The component repair loop: move components between repair states, add repair comments, upload documents. Reads the component repair area only.                                                                                                                                    |
| **Inspection Manager** | Create and manage inspection templates and reports, and assign inspectors. Reads the inspection area only.                                                                                                                                                                        |
| **Inspector**          | Submit findings on the reports they have been assigned to. Reads the inspection area only.                                                                                                                                                                                        |
| **Planner**            | Maintenance planning: create and edit plannings, drag planned work around the schedule, and maintain the manhour and cost estimates on tasks. Reads the planner area only.                                                                                                        |
| **AI Analytics User**  | Use Ask AI.                                                                                                                                                                                                                                                                       |

## Superusers

Superuser is a global flag on the user account itself, not a grant within a project. It
allows administering the platform as a whole — creating projects, managing user accounts —
and it applies everywhere rather than to one fleet.

The practical distinction:

* **Project Admin** is complete authority *inside one project*, granted per project.
* **Superuser** is platform-wide, set on the account, and is what creates projects in the
  first place.