> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.qosel.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.qosel.com/_mcp/server.

# Product overview

Qosel is made up of three surfaces, each with its own audience:

| Surface           | Address                         | Who uses it                                            |
| ----------------- | ------------------------------- | ------------------------------------------------------ |
| **Dashboard**     | `app.qosel.com`                 | Your hiring team — recruiters, hiring managers, admins |
| **Careers site**  | `your-company.qosel.com`        | Candidates browsing and applying to your jobs          |
| **People portal** | `people.qosel.com/your-company` | New hires and employees completing onboarding          |

You work in the **dashboard**. Candidates and employees never see it — they interact with your branded careers site and the People portal.

## Core concepts

Understanding a handful of objects makes everything else in Qosel click.

### Organization

Your company's workspace. It holds your team members, jobs, candidates, and settings. Your organization's URL slug (for example `acme`) becomes your careers site address: `acme.qosel.com`.

### Members and roles

People on your hiring team. Members are invited by email and assigned roles that control what they can see and do. You can define custom team roles under **Settings → Team roles**.

### Job

A role you are hiring for. A job has a description, requirements, compensation details, a location type (on-site, remote, or hybrid), and its own application form. Jobs move through a lifecycle — draft, review, scheduled, published — before appearing on your careers site.

### Pipeline and stages

The path an application follows, from first contact to hire. You can design multiple pipelines with custom stages (for example *Phone screen* or *Take-home exercise*) and pick the right pipeline per job. Every custom stage maps to one of six **normalized stages** — `Applied`, `Screening`, `Interview`, `Offer`, `Hired`, `Rejected` — so reporting and automations work consistently no matter how you name your stages.

### Candidate and application

A **candidate** is a person in your database. An **application** links a candidate to a specific job and tracks their progress through that job's pipeline. One candidate can have several applications over time — Qosel keeps the full history and detects duplicates so you always see one complete profile.

### Interview and scorecard

Interviews are scheduled from an application, using your connected calendar and video-conferencing tools. Interviewers submit **scorecards** — structured evaluations based on templates you define — and results roll up into an evaluation matrix for side-by-side comparison.

### Offer

A formal offer extended to a candidate, generated from an offer template with compensation details. Offers support an internal approval chain, versioning for renegotiations, and a secure link where the candidate accepts or declines online.

### Employee onboarding

Once a candidate is hired, they become an **employee** in the onboarding module. Onboarding workflows assign tasks, collect documents and e-signatures, and give the new hire a guided portal — starting with a magic link on day one.

### Automation

Rules that react to events in your hiring process — an application arriving, a stage change, an offer being accepted — and perform actions like sending an email, moving a stage, notifying Slack, or creating a task. Built visually, no code required.

## How it fits together

```
Careers site                    Dashboard                        People portal
─────────────                   ─────────                        ─────────────
Candidate applies  ──────▶  Application enters pipeline
                            Screening → Interviews → Scorecards
                            Offer approved and sent  ──────▶  Candidate accepts online
                            Hired → becomes Employee ──────▶  Day-one onboarding
```

## Next step

#### [Create your organization](/get-started/create-your-organization)

Set up your workspace and claim your careers site address