> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sitesuper.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Core concepts
> Organizations, projects, supers, schedules, and roles — the building blocks of SiteSuper.
SiteSuper has a small number of concepts. Once these click, everything else follows.
## Organization
Your top-level account — also called a **workspace**. It holds:
* **Billing & credits** — one balance for all your projects.
* **Team members** — the managers and owners who log in.
* **Supers** — your superintendents (shared across all projects).
* **Projects** — the individual job sites.
Most companies need exactly one organization. You'd create a second only to fully separate another company or billing entity. The **organization switcher** sits at the top-left of the app.
## Project
A **project** is a single job site or crew (internally called a "team"), e.g. *Yorkville South — Phase 2*. Projects organize:
* Which supers are assigned and reporting.
* The project's document folder (Drive or SharePoint) and AI-built schedule context.
* Reports, variances, action items, and the weekly summary.
A super can belong to many projects at once.
## Super
A **superintendent** is the field worker who provides the daily report. Key things to know:
* Supers **do not log in**. SiteSuper reaches out to *them* on a schedule.
* Each super has contact details (phone, email, SMS number, WhatsApp) and **contact preferences** (a primary method plus fallbacks).
* Supers live at the organization level and are **assigned** to one or more projects.
## Schedule
A **schedule** defines *when* and *how* SiteSuper contacts a super, and **for which project**:
* **Days** and **time** (in the site's timezone).
* The **channel** — by default the super's primary/fallback methods, optionally overridden per schedule.
* The **project** it belongs to — so the conversation and report are attributed to the right job. A super on multiple projects has a schedule per project.
A super can have multiple schedules (e.g. a weekday morning call and a Saturday SMS). You don't define questions per schedule — SiteSuper drives the report from the project's planned work and open variances (see [Schedules](/schedules)).
## Contacts
**Contacts** are the external people on a project — trades, subs, suppliers, inspectors, engineers, owner reps. They're attributed to a project, power variance follow-up (who gets chased when something slips), and can be added or corrected by the AI from the field. See [Contacts](/contacts).
## Reports, variances & action items
* A **report** is a single captured update from a super, parsed into structured sections.
* A **variance** is an issue the AI detects from reports (e.g. progress behind schedule, a missed inspection, a material shortfall). Variances can trigger automated follow-up chains.
* An **action item** is a task assigned to your team off the back of a variance.
## Roles
Full control: billing, account, team management, and granting owner rights — plus everything a Manager can do.
Manages supers, schedules, integrations, and reviews/acts on reports and variances.
A field worker. Does not log in — only receives outreach and gives reports.
Roles exist at two levels: your **organization** role (Owner/Manager) governs billing and cross-project access; your **project** role governs what you can do within a specific project. In practice, Owners and Managers can manage everything they're a member of.
## Credits
Outbound actions consume credits:
| Action | Cost |
| ---------- | ------------------- |
| Phone call | 12 credits / minute |
| SMS | 2 credits |
| Email | 2 credits |
New accounts start with **\$10 in free credits**. Top up any time from **Settings → Billing**, and optionally enable **auto top-up** so dispatch never stops mid-day.