# The Quantum Club Documentation — Full Content
> Full text of every public documentation page for The Quantum Club and Club OS,
> inlined for AI assistants. Guides for Members (candidates), Partners (hiring
> teams), and platform administrators.
---
# API
URL: https://docs.thequantumclub.com/api
> The public integration surface of The Quantum Club — SCIM 2.0 provisioning and webhooks, documented exactly as production serves them.
Add the documentation to any AI agent as live, queryable tools.
---
# Authentication
URL: https://docs.thequantumclub.com/api/authentication
> Authenticate both directions of the integration surface — bearer tokens for the SCIM requests you send, HMAC signatures for the webhook deliveries you receive.
## SCIM bearer tokens
Every SCIM request carries a tenant-scoped bearer token in the `Authorization` header:
```bash
curl https://chgrkvftjfibufoopmav.supabase.co/functions/v1/scim-users?count=1 \
-H "Authorization: Bearer tqc_scim_3q2-8h…"
```
```js
const res = await fetch(
'https://chgrkvftjfibufoopmav.supabase.co/functions/v1/scim-users?count=1',
{ headers: { Authorization: `Bearer ${process.env.TQC_SCIM_TOKEN}` } },
);
const body = await res.json();
```
```python
import os
import requests
res = requests.get(
"https://chgrkvftjfibufoopmav.supabase.co/functions/v1/scim-users",
params={"count": 1},
headers={"Authorization": f"Bearer {os.environ['TQC_SCIM_TOKEN']}"},
)
body = res.json()
```
Token properties:
- **Format:** `tqc_scim_`.
- **Tenant-scoped:** the tenant is resolved from the token itself, never from the URL or body. One token can only ever read or write its own tenant.
- **Hashed at rest:** only a PBKDF2-SHA256 hash is stored. The plaintext is displayed once at issuance and cannot be recovered — if it is lost, issue a new token.
- **Revocable and expirable:** revoked or expired tokens receive `401` immediately.
Tokens are issued from the SCIM administration area; issuance and revocation are step-up-protected admin operations. See [SCIM provisioning](/platform/identity/scim) for the operational workflow.
### Treat the token as a secret
- Store it only in your identity provider's credential field or a secrets manager.
- Never commit it to source control, paste it into tickets, or log it. The platform redacts `tqc_scim_` substrings from its own sync logs; do the same on your side.
### Rotation
Multiple unrevoked tokens per tenant are allowed, so rotation has no downtime: issue the new token, update the IdP, confirm syncs succeed, then revoke the old token.
## Webhook signature verification
Webhook deliveries are authenticated in the other direction: The Quantum Club signs each request so your receiver can verify origin and integrity.
Each delivery includes:
| Header | Content |
| --- | --- |
| `X-Webhook-Signature` | Hex-encoded HMAC-SHA256 of the raw request body, keyed with your endpoint's shared secret |
| `X-Webhook-Event` | The event type, for example `meeting.ended` |
| `X-Webhook-Delivery-ID` | Unique delivery identifier, for deduplication |
Verify by computing the same HMAC over the **raw body bytes** and comparing in constant time:
```js
import { createHmac, timingSafeEqual } from 'node:crypto';
function verifyWebhook(rawBody, signatureHeader, secret) {
const expected = createHmac('sha256', secret)
.update(rawBody) // raw bytes, before any JSON parsing
.digest('hex');
const a = Buffer.from(expected, 'hex');
const b = Buffer.from(signatureHeader, 'hex');
return a.length === b.length && timingSafeEqual(a, b);
}
```
```python
import hashlib
import hmac
def verify_webhook(raw_body: bytes, signature_header: str, secret: str) -> bool:
expected = hmac.new(
secret.encode(),
raw_body, # raw bytes, before any JSON parsing
hashlib.sha256,
).hexdigest()
return hmac.compare_digest(expected, signature_header)
```
Compute the HMAC over the raw request body exactly as received. Parsing the JSON and re-serializing it can reorder keys or change whitespace, which produces a different digest and a false verification failure.
Rules for receivers:
- Reject any request whose signature does not verify; do not process the payload first.
- Use a constant-time comparison to avoid timing side channels.
- Keep the shared secret out of client-side code and logs.
For endpoint requirements, retry behavior, and delivery semantics, see [webhooks](/api/webhooks). For the event catalog, see [webhook events](/api/webhook-events).
Your SCIM token lives only in the IdP and a secrets store, and your webhook receiver rejects unsigned or mis-signed requests using a constant-time comparison over the raw body.
---
# Docs MCP server
URL: https://docs.thequantumclub.com/api/mcp
> Add The Quantum Club documentation to any AI agent — Claude, Cursor, ChatGPT, or your own — as live, queryable tools.
The Quantum Club runs a public **Model Context Protocol** server. Add it to any
MCP client and your AI agent can search the documentation, read full pages, and
ask grounded questions — without leaving the chat.
## Endpoint
```
https://tqc-docs-mcp.darryl-2c6.workers.dev/mcp
```
Transport is **Streamable HTTP**. The server is read-only, needs no API key, and
exposes only documentation — no product data.
## Tools
| Tool | What it does |
| --- | --- |
| `search_docs` | Find the most relevant documentation sections for a query, with their page paths. |
| `get_page` | Fetch a full documentation page as markdown by path, for example `/api/scim`. |
| `ask_docs` | Ask a natural-language question and get a concise answer grounded only in the docs, with sources. |
## Add it to your agent
```bash
claude mcp add --transport http tqc-docs https://tqc-docs-mcp.darryl-2c6.workers.dev/mcp
```
Settings → MCP → Add new server, then paste:
```json
{
"tqc-docs": {
"url": "https://tqc-docs-mcp.darryl-2c6.workers.dev/mcp"
}
}
```
Add to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"tqc-docs": {
"url": "https://tqc-docs-mcp.darryl-2c6.workers.dev/mcp"
}
}
}
```
Any MCP client that supports Streamable HTTP:
```json
{
"mcpServers": {
"tqc-docs": {
"url": "https://tqc-docs-mcp.darryl-2c6.workers.dev/mcp"
}
}
}
```
Your agent now lists `search_docs`, `get_page`, and `ask_docs` among its
tools. Ask it something like "Using the tqc-docs tools, how do I set up SCIM?"
and it will answer from this documentation, with sources.
## Why this exists
Most documentation can only be read by a person in a browser. Increasingly, the
reader is an AI agent — writing an integration, answering a teammate, or building
against The Quantum Club. The MCP server makes the documentation a first-class
tool for those agents, so they answer from current, accurate source instead of
guessing.
## Related
- [Authentication](/api/authentication)
- [SCIM 2.0 reference](/api/scim)
- [Webhooks](/api/webhooks)
---
# Rate limits
URL: https://docs.thequantumclub.com/api/rate-limits
> Know exactly what a 429 means here, why authentication surfaces fail closed, and how to retry so your integration recovers cleanly.
## The model
Rate limiting is atomic (no check-then-write races) and identity-aware. Two buckets apply simultaneously:
- **Per-identity bucket.** Requests are counted against the acting identity — the SCIM token for provisioning traffic, or the account-plus-IP pair on authentication surfaces. One noisy tenant cannot starve another.
- **Per-IP ceiling.** A separate, higher cap on total requests from a single IP address. This stops fan-out abuse from one host even when it spreads load across many identities — and conversely, the per-identity bucket means many users behind one corporate NAT do not exhaust each other.
### Fail-closed on authentication surfaces
Behavior when the limiter itself cannot be evaluated differs by surface:
- **Authentication endpoints fail closed.** If the limit cannot be checked, the request is rejected. Availability is sacrificed before brute-force protection.
- **Non-authentication surfaces fail open**, biased toward availability. SCIM in particular tolerates this because identity providers re-list on their next sync sweep, so a transiently accepted request is reconciled.
## Current limits
| Surface | Limit |
| --- | --- |
| SCIM (per token) | 1,200 requests per hour |
| Per-IP infrastructure ceiling | Applies in addition to per-identity buckets |
Limits are subject to tuning; treat a `429` as authoritative rather than hard-coding thresholds.
## What a 429 looks like
```http
HTTP/1.1 429 Too Many Requests
Content-Type: application/json
Retry-After: 60
{
"error": "Rate limit exceeded. Please try again later.",
"retryAfter": 60,
"message": "Too many requests. Please wait 60 seconds before trying again."
}
```
The `Retry-After` header (and the matching `retryAfter` JSON field) is in **seconds**.
## Retry guidance
### Honor Retry-After first
If the response carries `Retry-After`, wait at least that long. Retrying earlier only re-fills the bucket you already exhausted.
### Back off exponentially with jitter
Without a `Retry-After` value, use exponential backoff (for example 1s, 2s, 4s, 8s…) with random jitter so concurrent clients do not retry in lockstep.
### Cap concurrency at the source
For SCIM, avoid running a bulk "push now" while a backfill or initial sync is in progress — that is the common way to trip the 1,200/hour token limit. The limit relaxes at the next hourly window.
### Retry only what is safe
`429` responses are always safe to retry. For non-idempotent operations that returned an ambiguous network failure, prefer a read-back (for example a SCIM filter query) over a blind re-POST, which can produce `409 uniqueness` conflicts.
Identity providers already implement compliant retry behavior for SCIM. The guidance above matters most for custom scripts and middleware you build yourself.
Your client honors `Retry-After`, backs off with jitter when it is absent, and never runs unbounded retry loops against authentication endpoints.
## Related
- [Authentication](/api/authentication)
- [Webhooks](/api/webhooks)
---
# SCIM 2.0 reference
URL: https://docs.thequantumclub.com/api/scim
> Every SCIM 2.0 endpoint, filter, response shape, and deprovision rule — the complete reference for what your identity provider can send and expect back.
For setup and identity-provider walkthroughs, see [SCIM provisioning](/platform/identity/scim).
## Base URL and auth
```text
https://chgrkvftjfibufoopmav.supabase.co/functions/v1
```
All requests except schema discovery require `Authorization: Bearer tqc_scim_…`. The tenant is resolved from the token — see [authentication](/api/authentication).
## Endpoints
| Operation | Method | Path | Success |
| --- | --- | --- | --- |
| List users | GET | `/scim-users` | 200 |
| Read user | GET | `/scim-users/{id}` | 200 |
| Create user | POST | `/scim-users` | 201 |
| Replace user | PUT | `/scim-users/{id}` | 200 |
| Patch user | PATCH | `/scim-users/{id}` | 200 |
| Deprovision user | DELETE | `/scim-users/{id}` | 204 |
| List groups | GET | `/scim-groups` | 200 |
| Read group | GET | `/scim-groups/{id}` | 200 |
| Create group | POST | `/scim-groups` | 201 |
| Replace group | PUT | `/scim-groups/{id}` | 200 |
| Patch group / members | PATCH | `/scim-groups/{id}` | 200 |
| Delete group | DELETE | `/scim-groups/{id}` | 204 |
| Service provider config | GET | `/scim-schemas/ServiceProviderConfig` | 200 (no auth) |
| Resource types | GET | `/scim-schemas/ResourceTypes` | 200 (no auth) |
| Schemas | GET | `/scim-schemas/Schemas` | 200 (no auth) |
## Provision a user
Create a user with `POST /scim-users`. The body is a SCIM `User` resource sent as `application/scim+json`; a successful create returns `201` with the stored resource, including its server-assigned `id`.
```bash
curl https://chgrkvftjfibufoopmav.supabase.co/functions/v1/scim-users \
-H "Authorization: Bearer tqc_scim_…" \
-H "Content-Type: application/scim+json" \
-d '{
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
"userName": "alice@acme.com",
"name": { "givenName": "Alice", "familyName": "Janssen" },
"emails": [{ "value": "alice@acme.com", "primary": true }],
"externalId": "00u1abcd2EFGHIJKL345",
"active": true
}'
```
```js
const res = await fetch(
'https://chgrkvftjfibufoopmav.supabase.co/functions/v1/scim-users',
{
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.TQC_SCIM_TOKEN}`,
'Content-Type': 'application/scim+json',
},
body: JSON.stringify({
schemas: ['urn:ietf:params:scim:schemas:core:2.0:User'],
userName: 'alice@acme.com',
name: { givenName: 'Alice', familyName: 'Janssen' },
emails: [{ value: 'alice@acme.com', primary: true }],
externalId: '00u1abcd2EFGHIJKL345',
active: true,
}),
},
);
const created = await res.json(); // 201 — the stored User, with server id
```
```python
import os
import requests
res = requests.post(
"https://chgrkvftjfibufoopmav.supabase.co/functions/v1/scim-users",
headers={
"Authorization": f"Bearer {os.environ['TQC_SCIM_TOKEN']}",
"Content-Type": "application/scim+json",
},
json={
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
"userName": "alice@acme.com",
"name": {"givenName": "Alice", "familyName": "Janssen"},
"emails": [{"value": "alice@acme.com", "primary": True}],
"externalId": "00u1abcd2EFGHIJKL345",
"active": True,
},
)
created = res.json() # 201 — the stored User, with server id
```
A duplicate `userName` or `externalId` returns `409` with `scimType: uniqueness`.
## Filters
List endpoints accept the subset that mainstream identity providers emit: `userName eq`, `externalId eq`, `id eq`, `active eq true|false`, `emails eq`, `emails.value eq`, and the bracketed `emails[type eq "work"].value eq` form (the selector is treated as the inner attribute). Groups additionally support `displayName eq`, `members eq`, and `members.value eq`.
```bash
curl -G https://chgrkvftjfibufoopmav.supabase.co/functions/v1/scim-users \
--data-urlencode 'filter=userName eq "alice@acme.com"' \
-H "Authorization: Bearer tqc_scim_…"
```
```js
const url = new URL(
'https://chgrkvftjfibufoopmav.supabase.co/functions/v1/scim-users',
);
url.searchParams.set('filter', 'userName eq "alice@acme.com"');
const res = await fetch(url, {
headers: { Authorization: `Bearer ${process.env.TQC_SCIM_TOKEN}` },
});
const list = await res.json(); // SCIM ListResponse
```
```python
import os
import requests
res = requests.get(
"https://chgrkvftjfibufoopmav.supabase.co/functions/v1/scim-users",
params={"filter": 'userName eq "alice@acme.com"'},
headers={"Authorization": f"Bearer {os.environ['TQC_SCIM_TOKEN']}"},
)
listing = res.json() # SCIM ListResponse
```
Unsupported filters return:
```json
{
"schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
"status": "400",
"detail": "Filter not supported: …",
"scimType": "invalidFilter"
}
```
## Response shapes
List responses follow RFC 7644 `ListResponse`:
```json
{
"schemas": ["urn:ietf:params:scim:api:messages:2.0:ListResponse"],
"totalResults": 1,
"startIndex": 1,
"itemsPerPage": 1,
"Resources": [
{
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
"id": "5f3a…",
"userName": "alice@acme.com",
"name": { "givenName": "Alice", "familyName": "Janssen" },
"displayName": "Alice Janssen",
"emails": [{ "value": "alice@acme.com", "primary": true }],
"externalId": "00u1abcd2EFGHIJKL345",
"active": true,
"meta": {
"resourceType": "User",
"created": "2026-01-15T09:12:00Z",
"lastModified": "2026-06-01T14:03:00Z",
"location": "https://…/scim-users/5f3a…"
}
}
]
}
```
The enterprise user extension (`urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`) is accepted, stored, and returned verbatim; only the core attributes above project onto platform profiles.
## Deprovision semantics
`DELETE /scim-users/{id}` returns `204` and:
- Removes the SCIM binding for the user — subsequent SCIM `GET` for that id returns `404`, per RFC 7644.
- **Suspends** the underlying account; sign-in is blocked.
- Retains the profile for audit. Deprovisioning is not data erasure — see [GDPR](/platform/privacy/gdpr) for deletion.
`PATCH` with `active: false` suspends without removing the binding; `active: true` reactivates.
## Errors
| HTTP | scimType | Cause |
| --- | --- | --- |
| 401 | `invalidCredentials` | Missing, revoked, expired, or wrong-tenant token |
| 400 | `invalidValue` | Missing `userName` on create or patch |
| 400 | `invalidFilter` | Unsupported filter expression |
| 400 | `invalidSyntax` | Malformed PATCH `Operations` array |
| 409 | `uniqueness` | `userName` or `externalId` already provisioned |
| 429 | — | Per-token limit (1,200/hour) exceeded — see [rate limits](/api/rate-limits) |
## Not supported
Bulk operations (`/Bulk`), password synchronization (by design — passwords are never copied across the wire), and SCIM v1.
`GET /scim-users?count=1` with your token returns a `ListResponse` with an integer `totalResults`.
---
# API stability
URL: https://docs.thequantumclub.com/api/versioning
> How the public API changes and what stays stable — the published OpenAPI contract is the source of truth, and additive evolution is the default.
The published contract is the API: if a field, endpoint, or event is in the [OpenAPI reference](/api/reference) and on these pages, you can depend on it; if it is not, it is not part of the public surface.
## There is no URL version
The public API does not use a version segment in its resource paths. There is no `/v1/` to pin, and you do not select a version per request.
The base URL is the production Edge Functions host — `https://chgrkvftjfibufoopmav.supabase.co/functions/v1`. The `functions/v1` here is the platform's function runtime prefix, not an API resource version; the resources themselves (`scim-users`, `webhook-dispatcher`, and so on) are unversioned. Treat the host and path you are given as stable, and do not parse a version out of the URL.
What is versioned is the contract document itself. The published [`openapi.yaml`](/api/reference) carries an `info.version` (currently `1.0.0`) that moves as the surface evolves. That number describes the document, not a routing prefix.
## The contract is the source of truth
`apps/public/public/openapi.yaml` is generated from the production deployment, not written by hand. Every path it lists is verified to exist in production before it ships; anything outside it is not part of the public API and may change without notice.
This has a practical consequence for how you build:
- **Depend only on what is documented.** Fields, query parameters, status codes, and events shown in the reference and on these pages are the contract. Undocumented response fields, internal endpoints, and incidental behavior are not, even if you can observe them.
- **Read defensively.** Tolerate unknown fields in responses and webhook payloads rather than rejecting them. Additive changes (see below) ship without warning, and a strict parser turns a non-breaking change into an outage on your side.
## What counts as a breaking change
A change is breaking if a correct, defensively written integration could stop working because of it. These are the changes the API avoids making without a deliberate migration path:
- Removing an endpoint, a response field, or a webhook event type.
- Renaming a field, an event type, or a query parameter.
- Changing the type or format of an existing field (for example, a string becoming an object).
- Making a previously optional request parameter required.
- Tightening validation so input that used to be accepted is now rejected.
- Changing authentication, the signature scheme, or the meaning of an existing status code.
## What counts as a non-breaking change
These ship continuously and do not require any action on your part:
- Adding a new endpoint or a new webhook event type.
- Adding a new optional field to a response or a webhook payload's `data`.
- Adding a new optional, defaulted request parameter.
- Adding a new accepted value to an open-ended field.
- Relaxing a previous limit, or fixing a bug so behavior matches the documented contract.
This is why both the [webhook events](/api/webhook-events) reference and the consumption guidance tell you to ignore unrecognized event types and unknown fields: that tolerance is what makes additive changes safe to receive.
## Limits and quotas are tuned, not frozen
[Rate limits](/api/rate-limits) are operational values, not part of the contract. They can be tuned up or down without a version change, which is why that page tells you to treat a `429` and its `Retry-After` header as authoritative rather than hard-coding a threshold. Build to the response, not to a number you copied once.
## How a deprecation would be communicated
When a breaking change becomes necessary, it is announced before it lands, not discovered after. The mechanism is the [changelog](/changelog): removals and migrations are recorded there with the affected surface and what to do, ahead of the change taking effect. Watch the changelog if you maintain an integration; it is the one place breaking changes are surfaced.
The most resilient integration reads only documented fields, tolerates unknown ones, treats rate-limit responses as authoritative, and watches the changelog. Built that way, additive changes never reach you as incidents.
## Related
- [Interactive reference](/api/reference)
- [Webhook events](/api/webhook-events)
- [Rate limits](/api/rate-limits)
- [Changelog](/changelog)
---
# Webhook events
URL: https://docs.thequantumclub.com/api/webhook-events
> Every event type emitted in production, with the exact payload your endpoint will receive for each.
If an event is not on this page, it does not exist.
## Event catalog
All current events belong to the **meetings** domain:
| Event | Fired when |
| --- | --- |
| `meeting.started` | A meeting transitions to in-progress |
| `meeting.ended` | A meeting completes |
| `meeting.cancelled` | A meeting is cancelled |
| `participant.joined` | A participant joins a meeting |
| `participant.left` | A participant leaves a meeting |
| `recording.ready` | A meeting recording becomes available |
| `transcript.ready` | A meeting transcript becomes available |
Subscriptions are per endpoint: each registered endpoint declares which of these event types it receives. See [webhooks](/api/webhooks) for delivery mechanics.
## Envelope
Every event shares the same envelope; only `data` varies. All six top-level fields are always present:
```json
{
"id": "evt-uuid",
"type": "meeting.started",
"timestamp": "2026-06-12T10:00:00Z",
"delivery_id": "delivery-uuid",
"organization_id": "org-uuid",
"data": { }
}
```
| Field | Type | Meaning |
| --- | --- | --- |
| `id` | UUID string | Unique identifier for this event occurrence. |
| `type` | string | The event type, one of the seven listed above. Also repeated in the `X-Webhook-Event` header. |
| `timestamp` | ISO 8601 string | When the event was produced, in UTC. |
| `delivery_id` | UUID string | Unique per delivery attempt's target. Deduplicate on this — it is also sent as `X-Webhook-Delivery-ID`. |
| `organization_id` | UUID string | The organization the event belongs to. |
| `data` | object | The per-event body documented below. |
The body is signed as-sent: `X-Webhook-Signature` is the hex HMAC-SHA256 of the exact JSON bytes shown. See [webhooks](/api/webhooks) for verification and [authentication](/api/authentication) for a constant-time check.
## Payloads by event
Each example below is a complete delivery body — the shared envelope wrapping that event's `data`.
### meeting.started / meeting.ended / meeting.cancelled
The three meeting lifecycle events carry an identical `data` shape; only `type` differs.
```json
{
"id": "9f1c0b3a-7d2e-4a51-9b6f-2c8e0d4a1f33",
"type": "meeting.ended",
"timestamp": "2026-06-12T11:00:04Z",
"delivery_id": "c4a8e2f0-1b6d-4e90-8a3c-5f7b9d0e1a22",
"organization_id": "1d7e5c9a-3b2f-4e80-9c1a-6d8f0b2e4a55",
"data": {
"meeting_id": "7a2b4c6d-8e0f-4a12-9b34-5c6d7e8f9a01",
"title": "Final interview — Senior Engineer",
"scheduled_start": "2026-06-12T10:00:00Z",
"scheduled_end": "2026-06-12T11:00:00Z",
"host_id": "3e5f7a9b-1c2d-4e60-8f01-2a3b4c5d6e70"
}
}
```
| `data` field | Type | Notes |
| --- | --- | --- |
| `meeting_id` | UUID string | The meeting this event concerns. |
| `title` | string | The meeting title at the time of the event. |
| `scheduled_start` | ISO 8601 string | Planned start time. |
| `scheduled_end` | ISO 8601 string | Planned end time. |
| `host_id` | UUID string | The user who owns the meeting. |
### participant.joined / participant.left
Both participant events share one `data` shape; `type` distinguishes a join from a leave.
```json
{
"id": "2b8d4f60-9a1c-4e23-8b50-7d9e1f3a5c66",
"type": "participant.joined",
"timestamp": "2026-06-12T10:02:14Z",
"delivery_id": "e1f3a5c7-2b4d-4068-9a1c-3e5f7b9d0e44",
"organization_id": "1d7e5c9a-3b2f-4e80-9c1a-6d8f0b2e4a55",
"data": {
"meeting_id": "7a2b4c6d-8e0f-4a12-9b34-5c6d7e8f9a01",
"participant_id": "5c7e9a1b-3d4f-4602-8a1c-9b0d2e4f6a88",
"user_id": "3e5f7a9b-1c2d-4e60-8f01-2a3b4c5d6e70",
"name": "Alice Janssen",
"role": "participant",
"timestamp": "2026-06-12T10:02:14Z"
}
}
```
| `data` field | Type | Notes |
| --- | --- | --- |
| `meeting_id` | UUID string | The meeting the participant belongs to. |
| `participant_id` | UUID string | The participant record for this person in this meeting. |
| `user_id` | UUID string or `null` | The Quantum Club user. `null` for an unauthenticated guest. |
| `name` | string | The participant's name; falls back to `"Unknown"` when no name is on record. |
| `role` | string | The participant's role in the meeting. |
| `timestamp` | ISO 8601 string | The join time for `participant.joined`, the leave time for `participant.left`. |
The `data.timestamp` is the moment the participant joined or left; the envelope `timestamp` is when the event was produced. They are usually the same to the second but are computed independently.
### recording.ready
Emitted once per recording when it finishes processing and becomes available.
```json
{
"id": "8c0e2a4f-6b1d-4e30-9a52-1c3e5f7b9d00",
"type": "recording.ready",
"timestamp": "2026-06-12T11:14:09Z",
"delivery_id": "a3c5e7f9-0b2d-4e41-8a63-2d4f6b8e0a11",
"organization_id": "1d7e5c9a-3b2f-4e80-9c1a-6d8f0b2e4a55",
"data": {
"meeting_id": "7a2b4c6d-8e0f-4a12-9b34-5c6d7e8f9a01",
"recording_id": "6d8f0b2e-4a5c-4e71-8b93-0c1d2e3f4a55",
"duration_seconds": 3120,
"size_bytes": 482344960
}
}
```
| `data` field | Type | Notes |
| --- | --- | --- |
| `meeting_id` | UUID string | The meeting the recording belongs to. |
| `recording_id` | UUID string | The recording that is now ready. |
| `duration_seconds` | integer | Recording length in seconds. |
| `size_bytes` | integer | Recording file size in bytes. |
The event signals availability and carries the recording's identifiers; it does not embed a download link. Fetch the media itself through the meetings surface using `recording_id`, where access stays subject to the recording's consent and permission checks.
### transcript.ready
Emitted once per transcript when it finishes processing.
```json
{
"id": "4a6c8e0f-2b3d-4e51-9a74-3c5e7f9b1d22",
"type": "transcript.ready",
"timestamp": "2026-06-12T11:16:42Z",
"delivery_id": "b5d7f9a1-3c4e-4062-8b85-4e6f8a0c2d33",
"organization_id": "1d7e5c9a-3b2f-4e80-9c1a-6d8f0b2e4a55",
"data": {
"meeting_id": "7a2b4c6d-8e0f-4a12-9b34-5c6d7e8f9a01",
"transcript_id": "9b1d3f5a-7c8e-4092-8a16-5d7f9b1c3e44",
"language": "en"
}
}
```
| `data` field | Type | Notes |
| --- | --- | --- |
| `meeting_id` | UUID string | The meeting the transcript belongs to. |
| `transcript_id` | UUID string | The transcript that is now ready. |
| `language` | string | The transcript's primary language code (for example `en`). |
Like `recording.ready`, this event carries identifiers rather than the transcript content. Retrieve the transcript through the meetings surface using `transcript_id`.
Recordings and transcripts exist only for meetings where participants gave recording consent — see [GDPR and data rights](/platform/privacy/gdpr). The `recording_id` and `transcript_id` reference personal data; treat them, and anything you fetch with them, as sensitive and keep them out of general application logs.
## Consumption notes
- Delivery is **at-least-once and unordered** — deduplicate on `delivery_id` and do not infer sequence from arrival order. A retried `participant.joined` can arrive after the matching `participant.left`.
- Use the envelope `timestamp` (and the participant payload's own `timestamp`) for ordering decisions.
- New event types and new `data` fields may be added over time as additive, non-breaking changes — see [API stability](/api/versioning). Ignore unrecognized `type` values and unknown fields gracefully rather than failing the delivery; your endpoint only receives types it subscribed to, but a tolerant parser costs nothing.
There are no `job.*`, `candidate.*`, or `offer.*` webhook events today. Integrations that need hiring-pipeline data should not poll for event names that this page does not list.
Your consumer handles all seven meeting-domain events, deduplicates on delivery_id, and degrades gracefully on unknown types.
## Related
- [Webhooks](/api/webhooks)
- [API stability and change policy](/api/versioning)
- [Authentication](/api/authentication)
---
# Webhooks
URL: https://docs.thequantumclub.com/api/webhooks
> Build a receiver that verifies signatures, acknowledges fast, and survives retries — everything delivery expects from your endpoint, with working code.
## How delivery works
When a subscribed event occurs, a delivery is queued and dispatched to your endpoint as an HTTP `POST` with a JSON body and three headers:
```http
POST /your/webhook/path HTTP/1.1
Content-Type: application/json
X-Webhook-Signature: 7f8a1c… (hex HMAC-SHA256 of the raw body)
X-Webhook-Event: meeting.ended
X-Webhook-Delivery-ID: 9b2e4f10-…
```
The payload envelope is consistent across all events:
```json
{
"id": "evt-uuid",
"type": "meeting.ended",
"timestamp": "2026-06-12T10:30:00Z",
"delivery_id": "9b2e4f10-…",
"organization_id": "org-uuid",
"data": { }
}
```
The `data` object varies by event — see the [event catalog](/api/webhook-events).
## Endpoint requirements
- **HTTPS** with a valid certificate. Plain HTTP endpoints are not a supported target.
- **Respond fast.** Deliveries time out after **10 seconds**. Acknowledge with a `2xx` immediately and process asynchronously; any non-`2xx` status or timeout counts as a failure.
- **Verify the signature** before processing. Compute HMAC-SHA256 over the raw request body with your endpoint's shared secret and compare against `X-Webhook-Signature` in constant time. Full verification snippet: [authentication](/api/authentication).
## Retries and backoff
Failed deliveries are retried automatically:
| Attempt | Delay after failure |
| --- | --- |
| 1 → 2 | 5 minutes |
| 2 → 3 | 30 minutes |
| 3 (final) | marked failed after roughly 2 hours |
A delivery is attempted at most **3 times**. Separately, an endpoint that accumulates **10 consecutive failures** across deliveries is automatically disabled to protect both sides; re-enable it after fixing the receiver.
A disabled endpoint receives nothing until it is reactivated. Monitor your receiver's error rate — ten straight failures (for example an expired certificate) silently stops your event stream.
## Delivery semantics: at-least-once, unordered
Design your consumer around two guarantees that are deliberately weak:
- **At-least-once.** A delivery can arrive more than once — for example when your endpoint processed the event but the `2xx` response was lost. Deduplicate on `delivery_id` (or the payload `id`).
- **Unordered.** Retried deliveries interleave with newer events, so `meeting.ended` can arrive before a delayed `meeting.started`. Use the payload `timestamp` and your own state rather than arrival order.
```js
// Idempotent consumption sketch
async function handleDelivery(req) {
if (!verifyWebhook(req.rawBody, req.headers['x-webhook-signature'], SECRET)) {
return respond(401);
}
const event = JSON.parse(req.rawBody);
if (await alreadyProcessed(event.delivery_id)) {
return respond(200); // duplicate — acknowledge, do nothing
}
await markProcessed(event.delivery_id);
await enqueueForProcessing(event); // process async, respond fast
return respond(200);
}
```
## Set up a subscription
Webhook endpoints are registered per organization with a target URL, a shared secret, and the list of event types to receive. Endpoints, secrets, and delivery history are managed in the partner administration area at [os.thequantumclub.com](https://os.thequantumclub.com).
Your endpoint verifies signatures, responds with a 2xx inside 10 seconds, deduplicates on delivery_id, and tolerates out-of-order arrival.
## Related
- [Webhook events](/api/webhook-events)
- [Authentication](/api/authentication)
---
# Club Booking
URL: https://docs.thequantumclub.com/booking
> Share one link, let people book real time on your calendar, and turn every booking into a meeting that runs itself.
Shown in-app as **Scheduling** and **Booking Links**.
Club Booking is the scheduling layer of The Quantum Club: you publish a booking link, a guest picks a time that is genuinely free, and a confirmed booking lands on both your calendars. No back-and-forth email, no double-bookings.
## The core loop
### Set your availability
Tell Club Booking the hours and days you take meetings, your timezone, and how much buffer you want around each one. Connect Google or Microsoft so your real busy time is subtracted automatically. See [Availability](/booking/availability).
### Create a booking link
Give the link a duration, optional questions, and limits like minimum notice or a daily cap. Each link gets its own public address at `/book/your-slug`. See [Create a booking link](/booking/create-a-booking-link).
### Share it
Send the link, drop it in a signature, or embed it on a page. Guests see only times that pass every rule you set. See [The guest experience](/booking/the-guest-experience).
### Let it run
A booking writes to your calendar, sends confirmations, and can open a Quantum Meetings room on its own. Reminders go out before the meeting, and high-risk no-shows get an extra nudge. See [Reminders and no-shows](/booking/reminders-and-no-shows).
Once a link is live, a guest can book a free slot and you both get a calendar event without exchanging a single message.
## Who it is for
- **Members** use booking links for intro calls, mentoring, and any meeting they would otherwise schedule by hand.
- **Partners** use the same engine for hiring — interview links candidates book themselves, and concierge scheduling runs on your behalf. See [Interview scheduling](/booking/interview-scheduling).
## What makes it different
A slot only appears when it is genuinely bookable — inside your hours, clear of your calendars, and past your minimum notice.
Because availability is computed against your live calendars at the moment a guest looks, the times they see are the times you can actually take. The same booking can open a Quantum Meetings room, attach Club AI for notes, and collect payment before it is confirmed — so one link does the work of a scheduler, a video tool, and a checkout.
## In this section
- [Create a booking link](/booking/create-a-booking-link)
- [Availability](/booking/availability)
- [Connect your calendar](/booking/connect-your-calendar)
- [The guest experience](/booking/the-guest-experience)
- [Reminders and no-shows](/booking/reminders-and-no-shows)
- [Payments](/booking/payments)
- [Interview scheduling](/booking/interview-scheduling)
---
# Availability
URL: https://docs.thequantumclub.com/booking/availability
> Understand exactly how Club Booking decides which slots a guest can see — your hours, your buffers, and your real calendar busy time.
Availability is the rule that decides which times a guest is offered. Club Booking starts from the hours you keep, removes everything you are already committed to, and shows only what is left.
## What you set
Your availability settings apply across your booking links:
- **Working hours and days** — the window you take meetings, day by day. Defaults to 09:00–17:00, Monday through Friday.
- **Slot interval** — how finely slots are offered, 30 minutes by default.
- **Buffers** — default padding before and after meetings, which individual links can override.
- **Booking window and minimum notice** — how far ahead and how close to now bookings are allowed.
- **Timezone** — your home timezone, used to anchor every slot.
## How a slot is computed
When a guest opens your booking page, Club Booking works through your day in order:
### Start from your hours
Only times inside your working hours and available days are candidates. Everything else is off the table before anything is subtracted.
### Subtract your buffers and existing bookings
Buffer time and other bookings on the link block the slots they touch, so back-to-back collisions cannot happen.
### Subtract your connected calendars
If you have connected Google or Microsoft, Club Booking reads your busy time and removes any slot that overlaps an event — across every calendar you have told it to check, not just your primary one. Your Quantum Meetings already on the books are blocked too.
### Apply your limits
Slots inside your minimum notice, past your booking window, or beyond a daily cap are dropped. What remains is what the guest sees.
Every time a guest sees is inside your hours, clear of your calendars and buffers, and within your booking rules.
## Timezones
Guests book in their own timezone. Club Booking shows them slots translated to where they are, then stores the booking against your timezone so the event lands correctly on both sides. Neither of you has to do the math.
## Busy time across calendars
The point of connecting a calendar is that a slot you are busy in never gets offered. Club Booking checks your connected calendars live at the moment a guest looks, so a meeting you added five minutes ago is already subtracted.
Without a connection, Club Booking still works — it just cannot see events outside The Quantum Club. It will offer any slot inside your hours that is not already booked through a link, so keep your hours tight or connect a calendar. See [Connect your calendar](/booking/connect-your-calendar).
## Related
- [Connect your calendar](/booking/connect-your-calendar)
- [Create a booking link](/booking/create-a-booking-link)
---
# Connect your calendar
URL: https://docs.thequantumclub.com/booking/connect-your-calendar
> Connect Google or Microsoft so Club Booking subtracts your real busy time and writes confirmed bookings straight to your calendar.
Connecting a calendar is what makes availability trustworthy: your real busy time is subtracted before a guest ever sees a slot, and confirmed bookings land on your calendar without a copy-paste.
## Supported calendars
Club Booking connects to **Google** and **Microsoft**. Connect the account that already holds your meetings — that is the busy time you want subtracted.
## Connect
### Open your calendar connections
Go to Scheduling and open your calendar settings.
### Choose Google or Microsoft
Pick your provider and sign in. You authorize The Quantum Club to read your busy time and write events; you stay in control of the account.
### Choose which calendars to check
If your account has more than one calendar, decide whether Club Booking checks all of them for conflicts or just your primary one. Checking all of them is the safer default — a slot you are busy in anywhere never gets offered.
Your calendar shows as connected, and the next slot a guest sees already has your busy time removed.
## What the connection does
- **Reads your busy time** so overlapping slots are hidden across every calendar you check.
- **Writes confirmed bookings** to your calendar as events, so a booking is on your schedule the moment it is made.
- **Stays current** by refreshing access in the background, so you are not reconnecting every week.
## If a connection stops working
Access can lapse — a password change or a revoked permission will break the link. When that happens, Club Booking can no longer see your busy time, and it falls back to offering any slot inside your hours that is not already booked through a link. If slots start appearing on times you are busy, reconnect the calendar from your scheduling settings.
The most common cause of a wrong slot being offered is a calendar connection that quietly expired. Reconnect first, then check your hours and buffers.
## Related
- [Availability](/booking/availability)
- [Create a booking link](/booking/create-a-booking-link)
---
# Create a booking link
URL: https://docs.thequantumclub.com/booking/create-a-booking-link
> Build a shareable booking link with the duration, buffers, notice, questions, and limits that fit how you meet.
A booking link is a public page where guests pick a time that works for both of you. Each link carries its own rules, so you can keep a 15-minute intro link and a 60-minute deep-dive link side by side.
## Build the link
### Set the duration
Choose how long the meeting runs. New links default to 30 minutes; set whatever length the conversation needs.
### Add buffers
Set buffer time before and after the meeting so back-to-back bookings do not collide. Buffers are subtracted from your availability the same way a busy calendar event is, so a 30-minute meeting with a 15-minute after-buffer holds 45 minutes of your day.
### Set how far ahead, and how soon
Two limits keep the link sensible: a booking window (how many days into the future guests can book, 60 by default) and a minimum notice (how close to now a booking is allowed, 2 hours by default). A guest cannot grab the next ten minutes, and they cannot book six months out unless you allow it.
### Add custom questions
Ask for what you need before the meeting — a topic, a company name, a link to review. Answers travel with the booking so you walk in prepared.
### Brand it
Give the link a title, a short description, and an accent color. You can point guests to a confirmation message or a redirect of your choosing once they finish booking.
Your link is live at `/book/your-slug` and ready to share the moment you save it.
## Caps and approval
Each link can carry limits beyond the basic window:
- **Daily cap** — limit how many bookings a single day can take, so a busy link does not swallow your week.
- **Single-use or total-use** — a link can accept one booking and close, or cap the total number of times it can ever be booked. Useful for a one-off slot you do not want reused.
- **Approval required** — turn this on and a booking arrives as a request you confirm, rather than landing on your calendar automatically.
## Turn a booking into a meeting
A booking link can create a Quantum Meetings room on its own. With auto-create enabled — the default — every booking comes with a meeting room already attached, so neither side has to make one. You can also switch on Club AI for the meeting so notes and insights are captured without anyone pressing record.
Because the meeting room, the questions, and any payment all hang off the same link, sharing the link is the only step you have to repeat. Everything downstream is configured once.
## Related
- [Availability](/booking/availability)
- [The guest experience](/booking/the-guest-experience)
- [Payments](/booking/payments)
---
# Interview scheduling
URL: https://docs.thequantumclub.com/booking/interview-scheduling
> Use the same booking engine for hiring — let candidates book themselves on an interview link, or have a scheduler arrange it for them.
Hiring interviews run on the same Club Booking engine as every other meeting, so the availability, calendars, reminders, and meeting rooms you already know apply to candidates too. There are two ways an interview gets on the calendar.
## Two ways to schedule
### Candidate self-booking
Share an interview booking link and the candidate picks a time that is genuinely open against the host's availability. The interview lands on the host's calendar, and the candidate gets the same confirmation and reminders as any guest. This removes the email thread entirely — the candidate schedules themselves.
### Concierge scheduling
When a candidate should not be left to self-serve, a scheduler arranges the interview directly — choosing the interviewer and the time on their behalf. The booking lands on the interviewer's calendar, and the candidate's application advances to reflect the scheduled interview.
However the interview was booked, it sits on the right person's calendar with the candidate confirmed and the meeting room ready.
## What rides along
Because interviews are bookings, everything Club Booking does for a meeting applies:
- **Real availability** — slots are computed against the host's connected calendars, so an interview never lands on a busy time. See [Availability](/booking/availability).
- **A Quantum Meetings room** when the link creates one, so a video interview has somewhere to happen the moment it is booked.
- **Reminders** before the interview, for both sides. See [Reminders and no-shows](/booking/reminders-and-no-shows).
## How it ties into hiring
An interview booking is connected to the candidate's application, so scheduling an interview moves the candidate forward in your pipeline rather than living in a separate calendar tool. The mechanics here are the booking half; for the hiring workflow around it — pipeline stages, interviewers, and what the candidate sees — that lives in the hiring section of the product.
Interview links are booking links with a candidate and an application attached. If you understand how a booking link works, you already understand how interview scheduling works.
## Related
- [Create a booking link](/booking/create-a-booking-link)
- [Availability](/booking/availability)
- [Reminders and no-shows](/booking/reminders-and-no-shows)
---
# Payments
URL: https://docs.thequantumclub.com/booking/payments
> Require payment at the time of booking so a slot is only held once the guest has paid through Stripe Checkout.
For paid sessions, Club Booking can collect payment as part of booking. Turn it on for a link and the guest pays before the slot is held — no invoicing, no chasing.
## Turn on payment for a link
A booking link can require payment. When you set it, you choose:
- **An amount** for the session.
- **A currency** the guest is charged in.
With payment required, the booking is not held until the guest has paid.
A payment-required link asks the guest to pay before the slot is confirmed.
## How the guest pays
When a guest books a payment-required link, Club Booking sends them to a Stripe Checkout page to pay the amount you set. Payment is collected through Stripe, so card details are handled by Stripe and never by the booking page itself. Once the payment goes through, the booking is confirmed and follows the same path as any other — calendar event, confirmation, reminders, and a meeting room if the link creates one.
On a paid link, the slot belongs to the guest only after they have paid — so a confirmed paid booking is always a paid one.
Requiring payment is a setting on each booking link, not an account-wide switch. Keep your free intro link free and charge only on the links where it makes sense.
## Related
- [Create a booking link](/booking/create-a-booking-link)
- [The guest experience](/booking/the-guest-experience)
---
# Reminders and no-shows
URL: https://docs.thequantumclub.com/booking/reminders-and-no-shows
> Keep bookings from slipping — automatic reminders before every meeting, plus an extra AI nudge for the ones most likely to be missed.
A booking is only useful if both people show up. Club Booking sends reminders before every meeting and adds an extra, targeted nudge to the bookings most at risk of being missed.
## Reminders
Once a booking is confirmed, reminders go out on a schedule ahead of the meeting — a day before, an hour before, and shortly before it starts. Reminders can reach the guest by email and by text, so the meeting stays top of mind without you sending anything yourself.
Reminders carry the meeting details and, when the link creates one, the link to join the Quantum Meetings room.
Every confirmed booking gets its reminders automatically — you do not schedule or send them.
## The no-show nudge
Some bookings are likelier to be missed than others. Club Booking flags high-risk bookings in the next day and sends each one an extra, personalized reminder beyond the standard schedule.
That nudge is built to recover the meeting, not just repeat the time:
- A friendly note that you are looking forward to meeting.
- An easy reschedule link, in case the original time stopped working.
- A way to add the meeting to their calendar.
A booking at risk of being missed gets one more, warmer touch — with an easy path to reschedule rather than simply not show.
The intervention runs on its own and sends each at-risk booking a single extra reminder, so the guest is helped, not pestered.
The nudge leads with a reschedule link on purpose: a guest who moves the meeting keeps the conversation alive, where a silent no-show ends it. See [The guest experience](/booking/the-guest-experience) for how guests reschedule on their own.
## Related
- [The guest experience](/booking/the-guest-experience)
- [Create a booking link](/booking/create-a-booking-link)
---
# The guest experience
URL: https://docs.thequantumclub.com/booking/the-guest-experience
> See exactly what a guest goes through on your booking page — picking a time, confirming, and rescheduling or cancelling on their own.
A guest never needs a Quantum Club account to book with you. Your link opens a public page at `/book/your-slug` where they pick a time, answer your questions, and confirm — and then manage the booking themselves if plans change.
## Booking, from the guest's side
### Open the link
The guest lands on your booking page and sees your title, description, and a calendar of open times. Slots are shown in the guest's own timezone.
### Pick a time
They choose from the slots you actually have free. Times that fail your rules — too soon, outside your hours, already busy — are never shown.
### Answer your questions and confirm
They enter their name and email, answer any custom questions you set, and confirm. If the link requires approval, the booking arrives to you as a request rather than a confirmed event.
The guest sees a confirmation, and the booking is on both calendars — with a meeting room attached if the link creates one.
## What the guest receives
After booking, the guest gets a confirmation by email with the details and, when the link creates one, a Quantum Meetings room to join. Reminders follow before the meeting. See [Reminders and no-shows](/booking/reminders-and-no-shows).
## Self-service reschedule and cancel
Plans change, and you do not want to be the bottleneck. Each booking carries a private management link in the guest's email. From it, the guest can:
- **Reschedule** to another open slot, recomputed against your live availability.
- **Cancel** the booking, with a reason.
You decide whether a link allows guests to reschedule or cancel on their own. When those controls are off, changes route back through you instead.
The person who made the booking can change it — without emailing you — but only within the limits you set on the link.
A guest rescheduling does not get a free pass around your availability. The new time has to be genuinely open, just like the original booking — so a reschedule can never put a meeting on a slot you are busy in.
## Related
- [Create a booking link](/booking/create-a-booking-link)
- [Reminders and no-shows](/booking/reminders-and-no-shows)
- [Payments](/booking/payments)
---
# Glossary
URL: https://docs.thequantumclub.com/glossary
> Every proper noun on the platform, defined once — so you always know exactly what Club AI, Club Sync, and the rest refer to.
These names are never translated or abbreviated.
| Term | Meaning |
| --- | --- |
| **The Quantum Club** | The platform itself — a premium career management platform connecting Members with Partners. Always spelled out in full. |
| **Club OS** | The operating system of The Quantum Club — the application at os.thequantumclub.com. |
| **Member** | An approved candidate in The Quantum Club. Membership begins after the approval review. |
| **Partner** | A company using The Quantum Club to hire — with its own team, roles, and hiring pipeline. |
| **Talent Strategist** | A human advisor assigned to guide Members and support Partner searches. |
| **Club AI** | The AI layer across the platform — matching, recommendations, and assistants. Includes Search, Deep Think, and Canvas modes. |
| **Club Sync** | The proprietary auto-apply feature for Members — with Club Sync enabled, you automatically apply to roles with a 90 percent or higher match score. |
| **Quantum Meetings** | The built-in video meeting platform — interviews, instant meetings, recordings, and AI insights. |
| **Quantum Signals** | An observed work-sample assessment that supports screening decisions. |
| **Incubator20** | A business-strategy simulation assessment built around a written business plan. |
| **Academy** | The learning platform — courses, learning paths, and certificates. |
| **Club Home** | Your dashboard — the first screen after signing in. |
| **Pipeline** | A Partner's hiring flow for a job, from application to offer, organized in stages. |
| **Scorecard** | A structured interview feedback form completed by interviewers. |
---
# Members
URL: https://docs.thequantumclub.com/members
> Your membership of The Quantum Club, from first sign-in to your next role — every step, documented.
Settings, security, your data, and what to do when something does not work.
---
# Job-search privacy
URL: https://docs.thequantumclub.com/members/account/job-search-privacy
> Run a confidential search — control which companies see you, what they see, and keep your current employer out of it.
## The three controls
Job-search privacy is governed by three independent controls in
[Settings](/members/account/settings) under **Privacy**. They stack: each one
narrows what a partner can see, and you can use any combination.
- **Field sharing** — per-field toggles for what partners see by default.
- **Stealth Mode** — anonymize your profile until you choose to reveal it.
- **Company blocklist** — name specific companies that may never see you.
## Choose what partners see
Field sharing decides which details appear to a partner you have not yet engaged
with. You toggle each field on or off, including your full name, email, phone,
location, current title, LinkedIn, salary expectations, and notice period.
One rule cuts through all of it: **applying to a company's role shares the
details that application needs with that company.** Deciding to apply is itself
consent. Field sharing governs what partners see when you have *not* taken that
step.
## Stealth Mode
Stealth Mode anonymizes your profile for cold outreach and blind-hiring
scenarios — it hides identifying details until you approve a conversation. Turn
it on and choose an **Anonymization Level**:
| Level | Name | Effect |
| --- | --- | --- |
| 1 | Basic Stealth | The lightest masking of identifying details. |
| 2 | Enhanced Stealth | A stronger layer over who you are. |
| 3 | Full Stealth | The most thorough anonymization. |
While Stealth Mode is on and you have not applied to a company's role, a partner
browsing candidates sees only non-identifying signal — your experience level,
skills, remote and employment preferences. Your name shows as **Candidate**, and
your contact details, current company, location, salary, and resume stay hidden
until you engage.
You can also set **Allow Cold Outreach** to decide whether partners may reach out
while you are anonymized. Leave it off to stay fully unsolicited-free.
Applying is consent. Until you apply, you control exactly how much of you a partner can see.
## Keep your current employer out
The **company blocklist** is the direct answer to "I don't want my current
employer to know I'm looking." Search for a company by name and add it; blocked
companies cannot see your profile, regardless of your other settings. Add your
current employer, and anyone else you would rather not surface to.
The blocklist works on companies you choose, so it covers more than one employer
— add former employers, competitors, or anyone you would rather keep at a
distance. Review it whenever your situation changes.
## How this works with Club Sync
When [Club Sync](/members/jobs/match-scores) acts on your behalf, it stays inside
these controls — your stealth setting, field sharing, and blocklist all hold.
Partners receive only the fields you have marked shareable or the information you
approve. Nothing about automation overrides the privacy you set here.
Your search is visible only to the partners you choose, on the terms you set — with your current employer blocked outright.
## Related
- [Understanding match scores](/members/jobs/match-scores)
- [Privacy and your data](/members/account/privacy)
- [Settings](/members/account/settings)
---
# Language & region
URL: https://docs.thequantumclub.com/members/account/language-and-region
> Read The Quantum Club in your language and keep every meeting time anchored to where you actually are.
## Set your display language
Your interface language lives in [Settings](/members/account/settings) under
**Language & Region**, in the **Display Language** selector. The choice applies
across the product and follows your account, so the same language greets you on
every device you sign in from.
English and Dutch (Nederlands) are both fully supported, alongside several other
languages. Switching is instant — pick your language and the interface
re-renders without a reload.
The display language translates the product interface — navigation, settings,
labels, and guidance. It does not translate content that other people wrote,
such as a partner's job description or a message from your Talent Strategist;
that text stays in the language it was written in.
## Set your region and time
Region settings sit in the same **Language & Region** section and shape how
dates, times, and scheduling read for you:
- **Date Format** — how calendar dates display.
- **Time Format** — 12-hour or 24-hour clock.
- **Timezone** — the anchor for every meeting invitation and reminder.
Meeting invitations and reminders are scheduled against your timezone. Keep it
accurate when you travel or relocate, or a reminder you trust will fire at the
wrong hour.
## A sensible setup
### Choose your language
Set **Display Language** to the language you read most comfortably. You can
change it any time without losing anything.
### Match your clock to your life
Set **Date Format** and **Time Format** to the conventions you actually use, so
times never need a second reading.
### Confirm your timezone
Check that **Timezone** reflects where you are right now, not where you signed
up. Revisit it after any move.
Your interface reads in your language, and dates, times, and meeting reminders all match your real location.
## Related
- [Settings](/members/account/settings)
- [Privacy and your data](/members/account/privacy)
- [Troubleshooting](/members/account/troubleshooting)
---
# Privacy and your data
URL: https://docs.thequantumclub.com/members/account/privacy
> See exactly what The Quantum Club holds about you, export all of it, or delete your account — no support ticket required.
## What is stored and why
The Quantum Club stores what membership requires to function, and the purpose of each category is concrete:
- **Identity and contact details** — your name, email, and verification data. Required to operate your account securely and, because the network is human-reviewed, to keep it trusted.
- **Your career profile** — resume, skills, work history, photo, and preferences. This is the substance of your membership; it powers matching, applications, and your Talent Strategist's work.
- **Activity data** — applications, saved jobs, assessment results, and Academy progress. This is your own history on the platform and feeds [your analytics](/members/grow/your-analytics).
- **Meeting artifacts** — recordings and transcripts from recorded Quantum Meetings calls, with consent surfaced before you participate. See [After the meeting](/members/meetings/after-the-meeting).
- **Security data** — sessions, sign-in methods, and security events, kept to protect the account itself.
Data is collected for the membership purposes above — never harvested for unrelated uses. If a category has no membership purpose, it is not stored.
## Manage it from privacy settings
Your privacy controls live in settings under **Privacy & Data Rights**, where you manage your personal data and exercise your GDPR rights directly — no support ticket required.
### Export your data
### Open Privacy & Data Rights
Go to settings and open the privacy section.
### Request the export
Choose the data export option and your preferred format.
### Download
When you see **Data Export Ready**, your data has been exported and the download starts shortly. Store the file securely — it contains everything the platform holds about you.
You should now have a complete copy of your data downloaded.
### Delete your account
Deletion is available from the same place. **Delete Account** permanently deletes your account and all associated data.
Choosing **Delete My Account** removes your profile, applications, history, and access — this is not a deactivation you can reverse later. Export your data first if you may ever want it.
## Your rights, in short
Under GDPR you have the right to access, correct, export, and erase your personal data. The export and deletion tools above cover access, portability, and erasure directly; corrections you make yourself by editing your [profile](/members/get-started/complete-your-profile) and settings. For anything these tools do not cover, contact The Quantum Club through your account.
## Related
- [Settings](/members/account/settings)
- [Account security](/members/account/security)
- [After the meeting](/members/meetings/after-the-meeting)
---
# Security
URL: https://docs.thequantumclub.com/members/account/security
> Harden your account with passkeys and MFA, audit every active session, and know the five ways back in if everything else fails.
## Passkeys
Passkeys are the recommended way to sign in — phishing-resistant, nothing to remember, one tap with your device's biometrics or screen lock. From your security settings you can:
- **Add a passkey** on each device you sign in from. The platform also offers to enroll one after sign-in if you have none yet.
- **Review your passkeys** and remove any tied to a device you no longer own.
Keep at least two passkeys (for example, laptop and phone) so losing one device never locks you out.
## Two-factor authentication
MFA adds a second factor on top of your password: a 6-digit code from an authenticator app. Once enabled, sign-ins prompt for the code, with the option to **Trust this device for 30 days** on machines you control. Sensitive account actions can also require a fresh second-factor check even mid-session — that is deliberate.
## Active sessions
The sessions list shows every device currently signed in to your account. Review it periodically and whenever something feels off:
### Open your sessions
In security settings, open the active sessions list. Each entry shows the device and session details.
### Revoke what you do not recognize
Revoke any session you do not recognize or no longer use — a borrowed laptop, an old phone. Revoking signs that device out immediately. Revoking a session is a protected action and may ask you to re-verify before it completes.
### If something looked wrong
After revoking an unknown session, rotate your credentials: change your password if you use one, and check your passkeys and MFA are intact.
You should now see only sessions you recognize in the list.
## The five recovery methods
If you lose access, five independent recovery routes exist. Open **Can't sign in?** on the sign-in page to start.
A recovery link sent to your account email. The standard route when you still control your inbox.
One-time codes you generated in advance from security settings. Store them somewhere safe and offline — each code works once. This is the route that works when you have lost your password, MFA, and devices at the same time.
Any passkey on any of your devices can recover access — a second reason to enroll more than one device.
If your account is connected to your organization's identity provider, signing in through SSO restores access without platform credentials.
The human path of last resort. A concierge verifies your identity through multiple independent checks before restoring access. Slower by design — the friction is the security.
Generate recovery codes and add a second passkey now, while you have access. Every recovery method except concierge depends on something you prepared in advance.
## Related
- [Create your account](/members/get-started/create-your-account)
- [Privacy and your data](/members/account/privacy)
- [Troubleshooting](/members/account/troubleshooting)
---
# Settings
URL: https://docs.thequantumclub.com/members/account/settings
> Decide how, when, and in what language The Quantum Club reaches you — notifications, quiet hours, appearance, and email.
## Notifications
Notification settings give you a master switch per channel, plus per-event controls under each:
- **Email Notifications** — interview, application, and account updates by email. Toggle individual types such as **Application Updates**, **New Messages**, **Meeting Reminders**, **Stage Updates**, and **Offer Notifications**, and set a **Digest Frequency** if you prefer batched delivery over immediate sends.
- **Push Notifications** — alerts on your device for time-sensitive events.
- **SMS notifications** — optional, used only for urgent scheduling and security updates. Requires a phone number.
- **WhatsApp notifications** — urgent scheduling updates through WhatsApp when available. Add a phone number to enable it.
- **In-app notifications** — product alerts and account updates inside The Quantum Club.
### Quiet Hours
**Enable Quiet Hours** to pause non-urgent notifications during a window you define with a **Start Time** and **End Time**. Urgent items still get through; everything else waits.
Keep email on for application and offer events, enable push for meeting reminders, and set Quiet Hours over your sleep window. You can tighten from there once you see your real notification volume.
## Language and region
Under **Language & Region**, set your **Display Language**, **Date Format**, **Time Format**, and timezone. The timezone matters more than it looks — meeting invitations and reminders are scheduled against it, so keep it correct when you travel or relocate.
## Appearance
Under **Appearance**, choose your **Theme** — **Light** or **Dark**. The choice is purely visual and applies immediately.
## Email preferences
Your account email is where security messages, approval updates, and notification email all arrive. You can update the address associated with your account from settings; changes to your sign-in email are confirmed for security before they take effect. Fine-grained control over which emails you receive lives in the notification settings above, not in a separate subscription page.
You should now have each notification channel set deliberately, Quiet Hours covering your off-hours, and your language, timezone, and theme matching how you work.
## Related
- [Account security](/members/account/security)
- [Privacy and your data](/members/account/privacy)
- [Troubleshooting](/members/account/troubleshooting)
---
# Troubleshooting
URL: https://docs.thequantumclub.com/members/account/troubleshooting
> Diagnose sign-in, approval, meeting, email, and application problems symptom by symptom — likely cause first, then the fix.
## Signing in
Likely cause: you are on a device or browser profile where the passkey was never created, or the passkey was removed.
Fix: choose **More ways to sign in** and use another method — magic link or password — to get in. Then go to [Security](/members/account/security) and add a passkey for this device. If a passkey you expect has disappeared from the list, it was removed; enroll a new one. Keeping passkeys on two devices prevents this entirely.
Likely cause: the email landed in spam, the link expired — magic links expire in one hour — or you requested several links in a row and hit the rate limit.
Fix: check spam and search your inbox for The Quantum Club. If the link is older than an hour, request a fresh one and open the newest email only — each new request supersedes earlier links. If you see a rate-limit message, wait the indicated minutes before requesting again. Open the link in the same browser you want to stay signed in on.
Likely cause: a typo, or the email and password genuinely do not match.
Fix: retype carefully (check caps lock), or use **Forgot password?** to reset. If you never set a password — many members sign in only with passkeys or magic links — use a magic link instead. Repeated failures temporarily lock the account for security; wait a few minutes before retrying. If you are fully locked out, the [five recovery methods](/members/account/security) get you back in.
## Approval
Likely cause: review is human and queue depth varies — a few business days is normal. Longer waits usually mean an incomplete dossier or an unverified email.
Fix: sign in and confirm every onboarding checkpoint is complete, and that you verified your email address. If both are done and you are well past a week, reply to your onboarding email so the team can check your review. Meanwhile, the waiting time is usable — see [The approval journey](/members/get-started/approval-journey).
## Meetings
Likely cause: a restrictive network (corporate VPN, strict firewall) or an unstable connection blocking the call from establishing.
Fix: reload the meeting link first. If it still fails, switch networks — off the VPN, or from mobile data to Wi-Fi — and try a different browser. If you remain stuck moments before an interview, tell the host immediately; meetings can be rejoined as soon as you connect.
Likely cause: the browser permission was denied — often by an accidental click on "Block" — or another app is holding the camera.
Fix: you do not need to fix it to get in — choose **Join Anyway** to enter with devices off. To restore them: open the browser's site settings for the meeting page, set Camera and Microphone to Allow, close other apps using the camera, and reload. Full walkthrough: [Join a meeting](/members/meetings/join-a-meeting).
## Email and notifications
Likely cause: spam filtering, a corporate mail gateway quarantining the messages, or the notification type is switched off.
Fix: search all mail folders for The Quantum Club and mark a found message as Not Spam. Add the sender to your contacts. Then check [Settings](/members/account/settings) — confirm **Email Notifications** is enabled, the specific types you expect are on, and Quiet Hours or digest frequency is not deferring them. On a work address, ask IT whether the messages are quarantined, or switch your account to a personal address.
## Applications
Likely cause: nothing has changed yet on the company's side — screening and interview stages routinely sit unchanged for days or weeks.
Fix: check the application's timeline for the date of the last real event before assuming something is stuck. Stage changes appear there as they happen and notify you through your enabled channels. If a status contradicts reality — you completed an interview but the stage never moved — ask your Talent Strategist to check with the company. Statuses explained: [Apply and track](/members/jobs/apply-and-track).
If none of these resolve it, your Talent Strategist is your fastest route for anything involving applications or companies, and account-level issues can be raised through your account at [os.thequantumclub.com](https://os.thequantumclub.com).
## Related
- [Account security](/members/account/security)
- [Join a meeting](/members/meetings/join-a-meeting)
- [Settings](/members/account/settings)
---
# WhatsApp & SMS
URL: https://docs.thequantumclub.com/members/account/whatsapp-and-sms
> Verify your phone once, then let The Quantum Club reach you on the channel you actually check for time-sensitive updates.
## What these channels are for
SMS and WhatsApp are reserved for time-sensitive items — meeting reminders,
urgent scheduling changes, and security alerts. They are not a chat inbox and
not where your applications or messages live; those stay inside The Quantum
Club. Both channels are opt-in and both require a verified phone number.
## Verify your phone number
A verified number is the prerequisite for every text-based notification. You
verify it once with a one-time code.
### Add your number
In settings, enter your mobile number where prompted for phone verification.
### Request the code
A 6-digit code is sent to your phone by SMS. If it does not arrive, you can
request another after a short cooldown.
### Enter the code
Type the 6-digit code to confirm the number. The code expires, and a fresh one
is sent each time you request it.
Your number now shows as verified, and SMS and WhatsApp notifications can be enabled against it.
Each code works once and only for a short window. If you mistype it or wait too
long, request a new one rather than reusing the old.
## Turn channels on
Channels are controlled per type in [Settings](/members/account/settings), not
here:
- **SMS notifications** — urgent scheduling and security updates by text.
- **WhatsApp notifications** — the same class of urgent updates through
WhatsApp, where available.
Both stay off until you enable them, and both need the verified number above.
Quiet Hours still apply: non-urgent items wait for your window to close, while
genuinely urgent ones come through.
## What these channels do not do
Being precise about the limits keeps your expectations right:
- **They are outbound, not a help desk.** Replying to a notification text does
not open a support conversation or reach your Talent Strategist. Use your
account for anything that needs a response.
- **They never carry sensitive data.** Codes and reminders only — never
passwords, documents, or full message contents.
- **WhatsApp coverage depends on availability.** When WhatsApp delivery is not
available for your number or region, you still receive the same updates by SMS
or in-app.
If you change numbers, re-verify the new one before you rely on text alerts. An
unverified or stale number silently misses every SMS and WhatsApp send.
## Related
- [Settings](/members/account/settings)
- [Account security](/members/account/security)
- [Troubleshooting](/members/account/troubleshooting)
---
# Incubator20
URL: https://docs.thequantumclub.com/members/assessments/incubator20
> Walk into the timed business-strategy simulation knowing the format — and write a 300–450 word plan that shows your thinking at its best.
## What it is
Incubator20 is a timed business-strategy simulation. You receive a realistic business scenario, frame the problem, build a plan section by section, and commit a final business plan of **300 to 450 words total**. It is a work sample: the output is the kind of strategic writing you would produce in a real role, under real time pressure.
## How a session flows
### Brief
You read the scenario. The timer has not started yet, so read it properly — most weak plans trace back to a skimmed brief.
### Frame
The timer starts. You answer framing questions that force you to define the problem before proposing anything. Your framing answers carry into the next phase.
### Build
You draft the plan across structured sections on the plan canvas, with a live word counter against the 450-word ceiling. An AI chat is available inside the session to think out loud with — it is part of the format, not a shortcut.
### Commit
You review the full plan and submit. The plan must land between 300 and 450 words to submit; the screen tells you exactly how many words to add or trim. If time expires, you can still submit whatever you have written, as long as it is not empty.
You should now see Incubator20 marked complete at /assessments, with your committed plan attached to your profile.
## How to approach it
- **Spend framing time on framing.** A precise definition of the problem makes every later sentence easier and sharper.
- **Decide, do not survey.** 300–450 words leaves no room for "on the other hand" tours. Pick a direction and argue it.
- **Use the structure.** The plan sections exist to keep you covering strategy, execution, and risk — write to them rather than around them.
- **Budget words like money.** Draft tight from the start; cutting 150 words under a timer is harder than writing 350 deliberate ones.
- **Leave commit time.** Reserve the final minutes for a full read-through. One pass for clarity is worth more than one extra paragraph.
## What reviewers look at
Reviewers read your plan as evidence of judgment, not polish:
- **Clarity of thought** — is the problem defined and the logic traceable?
- **Decision quality** — did you commit to a direction and justify it with the scenario's facts?
- **Prioritization** — did you spend your scarce words on what matters most?
- **Realism** — does the plan respect constraints, or does it assume them away?
Your result becomes a supporting signal on your profile, reviewed by humans alongside everything else — see [how results are used](/members/assessments/overview).
## Related
- [Assessments overview](/members/assessments/overview)
- [Quantum Signals](/members/assessments/quantum-signals)
---
# Assessments overview
URL: https://docs.thequantumclub.com/members/assessments/overview
> Know what assessments add to your profile, where yours live, and exactly how results are — and are not — used.
## Why assessments exist
A resume shows what you say you have done. An assessment shows how you work when given a real problem. The Quantum Club uses assessments to add observed evidence to your profile — concrete signal that helps reviewers and hiring companies see strengths a CV cannot carry.
## Where to find them
Assessments live at `/assessments`. You see assessments that have been assigned to you — typically by a company as part of an application, or by your Talent Strategist — along with any due date and notes the assigner left for you. Some assessments may also be open for you to take proactively.
## The current assessments
## How results are used
This part matters, so here it is plainly:
- **Results are supporting signals.** They add evidence to your profile alongside your resume, work history, and interviews. No assessment result decides an outcome on its own.
- **Humans review them.** Reviewers, hiring companies, and your Talent Strategist read assessment evidence in context. The decision-makers are people.
- **They measure work, not personality.** The Quantum Club's assessments observe how you handle realistic tasks. They are not personality tests and make no clinical or diagnostic claims about you.
- **Scoring happens server-side.** Your results are computed and stored by the platform, not in your browser, so they are consistent and tamper-resistant for everyone.
The strongest performances come from treating an assessment like a real task with a real deadline: read the brief carefully, manage your time, and make clear decisions. There is no trick to find and no profile to perform.
## Practical notes
- Check the **due date** when an assessment is assigned and plan an uninterrupted block for it.
- Read any **notes** from the assigner — they often carry context about what the role values.
- Timed assessments save your progress as you work; give them your full attention rather than running them in a background tab.
## Related
- [Incubator20](/members/assessments/incubator20)
- [Quantum Signals](/members/assessments/quantum-signals)
- [Apply and track applications](/members/jobs/apply-and-track)
---
# Quantum Signals
URL: https://docs.thequantumclub.com/members/assessments/quantum-signals
> Take Quantum Signals knowing exactly what it observes, how a session runs, and how the result is — and is not — used.
## What it is
Quantum Signals is an **observed work-sample assessment**. You work through realistic professional moments — for example, triaging incoming signals and handling a trust-sensitive situation — and the platform records how you approach them. The output is observed evidence of how you work, attached to your profile as a supporting signal.
Quantum Signals observes how you work — it does not judge who you are.
## What it is not
This deserves its own section, stated without hedging:
- **It is not a personality test.** Quantum Signals observes behavior on work tasks. It does not categorize your personality, infer traits, or place you on any psychological scale.
- **It makes no clinical or diagnostic claims.** Nothing in the assessment measures, screens for, or comments on any psychological or medical condition.
- **It does not decide outcomes.** Results are classified as screening support: they inform human screening decisions but never make them. No application is accepted or rejected by a Quantum Signals score alone — a human always reviews the evidence in context.
Your result is one well-documented data point a reviewer reads alongside your resume, interviews, and everything else. It can strengthen your case or prompt a follow-up question. It cannot, by design, be the reason for a decision on its own.
## How a session works
### Receive the assignment
Quantum Signals appears at `/assessments` when it is assigned to you, with any due date and notes from the assigner.
### Set aside focused time
The scenarios reward attention. Take the session in one sitting, in a quiet environment, the way you would handle real work that matters.
### Work the scenarios
Respond to each situation as you genuinely would. There is no persona to perform — the value of the evidence comes from it being an honest sample of your working style.
### Submit
Your responses are scored server-side and the result attaches to your profile as observed work-sample evidence.
You should now see the assessment marked complete at /assessments.
## How to approach it
Do the work as yourself. Because Quantum Signals samples real behavior rather than testing knowledge, the best preparation is being rested and focused. Trying to guess "the right answer" usually produces weaker evidence than handling the situation the way your experience tells you to.
## Related
- [Assessments overview](/members/assessments/overview)
- [Incubator20](/members/assessments/incubator20)
- [Apply and track applications](/members/jobs/apply-and-track)
---
# The approval journey
URL: https://docs.thequantumclub.com/members/get-started/approval-journey
> Know what happens while a human reads your dossier, how long it usually takes, and how to make the waiting time count.
## Why there is a review
The Quantum Club is private by design.
Every new member's dossier is read by a human reviewer — not scored by an algorithm and waved through.
That review protects the quality of the network you are joining: companies trust that members are vetted, and you benefit from that trust the moment you apply to a role.
## What happens during review
When you complete onboarding, your dossier moves into a pending-approval state and two things happen:
- **A human reviews your dossier.** Reviewers look for evidence of unusually high agency — scope, proof, and trajectory — not keyword volume. Links, a sharp CV, and concrete outcomes help them calibrate fast.
- **A Talent Strategist is assigned to you.** This is the person who will know your profile, calibrate introductions, and work with you once you are approved.
You can sign in during this period. Your account works, but member features stay locked until approval.
## Typical timeline
Most reviews complete within a few business days. Complex profiles, missing evidence, or high application volume can extend that. If the reviewer needs more from you, you hear about it by email rather than being silently declined.
If you have waited noticeably longer than a week, check that your onboarding is fully complete and your email is verified, then see [Troubleshooting](/members/account/troubleshooting).
## What you can prepare meanwhile
The review window is useful time:
- **Tighten your dossier evidence.** Strong links and a current CV speed up calibration.
- **Get your resume ready.** You upload it right after approval — see [Complete your profile](/members/get-started/complete-your-profile).
- **Think through compensation.** Onboarding asks for market expectations; having a clear, honest range protects your time later.
- **Set up security.** Add a passkey and review your sign-in methods under [Security](/members/account/security).
## What unlocks on approval
Approval opens the full member surface in one step:
You also get applications tracking, offer comparison, Quantum Meetings for interviews, and direct contact with your Talent Strategist.
## If the outcome is a decline
Not every application is approved. A decline is about fit with the current network, not a verdict on your career. You are notified by email, and the notice explains anything you can do next.
## Related
- [Complete your profile](/members/get-started/complete-your-profile)
- [Welcome to The Quantum Club](/members/get-started/welcome)
---
# Complete your profile
URL: https://docs.thequantumclub.com/members/get-started/complete-your-profile
> Build the profile Club AI matches from — every section you complete sharpens your scores and your Talent Strategist's case for you.
Prerequisites: an approved account. Have a current resume file ready.
## Why completeness matters
Club AI matches you to roles using your skills, experience, location, and salary expectations. Every empty section is signal it cannot use. A complete profile means higher-confidence [match scores](/members/jobs/match-scores), better recommendations, and a Talent Strategist who can advocate for you with specifics instead of guesses. If you enable Club Sync auto-apply later, the profile is also what gets you past the 90 percent match threshold.
## Build the profile
### Upload your resume
Open your profile and upload your resume. Keep it current — partners and your Talent Strategist see it alongside applications. You can preview, download, or replace it at any time.
### Add your skills
List the skills you actually use, not every tool you have touched. Skills feed directly into matching, so precision beats volume — a focused list produces better matches than a padded one.
### Fill in work history
Add each role with scope and outcomes. Reviewers and matching both weigh evidence of what you delivered, so "grew revenue from X to Y" carries more than a list of duties.
### Upload a photo
A clear, professional photo. It appears wherever partners and strategists see your profile, including meeting rooms and application views.
### Confirm preferences
Check your location, mobility, and compensation expectations carry over correctly from onboarding. These gate which roles you are matched to — a stale location quietly filters out good roles.
You should now see your profile with resume, skills, work history, and photo in place, and no incomplete sections flagged.
Revisit your profile after every meaningful change — a new skill, a finished role, a salary expectation shift. Matching reflects what is on the profile today, not what was true when you joined.
## Related
- [Understanding match scores](/members/jobs/match-scores)
- [Find jobs](/members/jobs/find-jobs)
- [Privacy and your data](/members/account/privacy)
---
# Create your account
URL: https://docs.thequantumclub.com/members/get-started/create-your-account
> Create your account in minutes — and choose between passkey, magic link, password, and SSO with the trade-offs clear.
Prerequisites: an email address you control. If your organization uses single sign-on, your work email is enough.
## Choose a sign-in method
A passkey uses your device's fingerprint, face, or screen lock instead of a password. Nothing to remember, nothing to phish, and signing in takes one tap. This is the recommended method, and the platform prompts you to add one after your first sign-in if you start another way.
Enter your email and choose **Send a secure magic link**. A sign-in link arrives in your inbox and expires in one hour. Good for a first sign-up or for devices where you have not added a passkey yet.
A traditional email and password. Choose **More ways to sign in**, then **Sign in with password**. Use at least 12 characters with an uppercase letter, lowercase letter, number, and symbol.
If your organization manages access, choose **Continue with single sign-on**, enter your work email, and you are routed to your identity provider.
Passkeys cannot be reused, guessed, or phished, and they sync across your devices through your platform account. They are both the fastest and the most secure option. You can manage them later under [Security](/members/account/security).
## Create the account
### Open the sign-in page
Go to [os.thequantumclub.com](https://os.thequantumclub.com) and open `/auth`. Choose **Sign up**.
### Enter your email
Use an address you check regularly — approval updates and interview invitations arrive there.
### Pick your method
Follow the prompts for your chosen method. With a magic link, open your inbox and click the link; it expires in one hour. With a password, confirm it meets the strength requirements.
### Verify your email
If you signed up with a password, verify your email with the link we send before continuing.
### Start onboarding
You land in onboarding, where you build the dossier that goes to human review. Work through each checkpoint at your own pace — progress is saved.
You should now see the onboarding checkpoints, starting with Identity and access.
## Related
- [The approval journey](/members/get-started/approval-journey)
- [Account security](/members/account/security)
- [Troubleshooting sign-in](/members/account/troubleshooting)
---
# Quickstart
URL: https://docs.thequantumclub.com/members/get-started/quickstart
> Go from a fresh invite to a dossier in human review and a Talent Strategist assigned — your first ten minutes as a member of The Quantum Club.
**Prerequisites:** an email address you control. If your organization uses single sign-on, your work email is enough.
### Create your account
Go to [os.thequantumclub.com](https://os.thequantumclub.com), open `/auth`, and choose **Sign up**. Pick a sign-in method — a passkey is recommended, with magic link, password, and SSO also available. Use an address you check regularly, since approval updates and interview invitations arrive there. Full detail in [Create your account](/members/get-started/create-your-account).
### Complete onboarding
You land in onboarding, a structured set of checkpoints that builds your private dossier: identity, proof of work, trajectory, compensation expectations, and mobility. Work through each checkpoint at your own pace — progress is saved, so you can stop and return.
### Submit for human review
When onboarding is complete, your dossier moves into a pending-approval state. A real reviewer reads it and a Talent Strategist is assigned to you. You can sign in during this period, but member features stay locked until approval. See [The approval journey](/members/get-started/approval-journey) for what happens and when.
### Prepare while you wait
The review window is useful time. Have a current resume ready to upload, think through an honest compensation range, and add a passkey under [Security](/members/account/security). Tightening your dossier evidence — strong links and a sharp CV — speeds up the reviewer's calibration.
### Build your profile on approval
Approval opens the full member surface in one step. Complete your profile — resume, skills, work history, and a photo — because completeness directly improves how well Club AI matches you to roles. From there you can search curated jobs, apply, and track each application through screening, interviews, and assessments. See [Complete your profile](/members/get-started/complete-your-profile).
You should now have an account, a completed onboarding dossier in pending review, and a Talent Strategist assigned. On approval, your profile and the full member surface unlock.
## Related
- [Welcome to The Quantum Club](/members/get-started/welcome)
- [The approval journey](/members/get-started/approval-journey)
- [Complete your profile](/members/get-started/complete-your-profile)
---
# Welcome to The Quantum Club
URL: https://docs.thequantumclub.com/members/get-started/welcome
> See the whole journey before you start it — what membership in The Quantum Club means, and the path from first sign-in to your next role.
## What membership is
The Quantum Club is a private, invite-reviewed career management platform. Every member is reviewed by a human before joining, which keeps the network high-signal for both you and the companies hiring through it. Once you are in, the platform manages your entire career motion in one place: curated roles, applications, interviews, offers, and long-term growth.
## Your journey
### Sign up
Create your account at [os.thequantumclub.com](https://os.thequantumclub.com) with a passkey, magic link, password, or your organization's SSO. See [Create your account](/members/get-started/create-your-account).
### Complete onboarding
A structured set of checkpoints builds your private dossier: identity, proof of work, trajectory, compensation expectations, and mobility.
### Human review
Your dossier goes to a real reviewer and a Talent Strategist is assigned to you. Read [The approval journey](/members/get-started/approval-journey) for what happens and when.
### Build your profile
Resume, skills, work history, and a photo. Completeness directly improves how well Club AI matches you to roles — see [Complete your profile](/members/get-started/complete-your-profile).
### Find and pursue roles
Search curated jobs, apply, and track every application through screening, interviews, and assessments.
### Interview and compare offers
Run video interviews in Quantum Meetings, prepare with the Interview Prep AI chat, then weigh offers side by side at /offers.
### Keep growing
Academy courses, referrals, personal analytics, and Club AI keep working for you between roles, not only during a search.
## What makes it different
Two things run side by side for every member:
- **A human Talent Strategist.** A real person assigned to you who knows your dossier, calibrates introductions, and advocates for you with hiring companies.
- **Club AI.** The platform's intelligence layer. It scores how well roles match your skills, experience, location, and salary expectations, analyzes offers, helps draft cover letters, and answers questions in Search, Deep Think, and Canvas modes.
Neither replaces the other.
Club AI surfaces signal; humans make the decisions that matter.
## Where to go next
---
# Academy
URL: https://docs.thequantumclub.com/members/grow/academy
> Turn Academy courses into visible, verifiable progress — learning paths, saved progress, and certificates anyone can check.
## What the Academy is
The Academy is The Quantum Club's learning surface: structured courses you take inside the platform, organized so that what you learn compounds into your career profile rather than disappearing into a certificates drawer.
## Courses
Courses range from compact formats to in-depth programs — workshops run several modules over a few hours, while masterclasses go deeper across many modules. Each course is broken into modules you complete in order, and your progress is saved as you go, so you can work in short sessions.
## Learning paths
Learning paths chain related courses into a sequence toward a capability, not a single topic. Follow a path when you have a destination in mind — moving into a new domain, leveling up for a target role — and individual courses when you are filling a specific gap.
## Progress
Your progress is tracked per course and per path: modules completed, where you left off, and what is next. Pick up exactly where you stopped from the Academy home.
## Certificates
Completing a course earns a certificate. Certificates are verifiable — each one carries a verification code that anyone can check on the platform, which makes them worth putting on a profile or CV rather than being decorative.
A certificate aligned with a role you are pursuing strengthens the same profile that [match scores](/members/jobs/match-scores) read. Choose courses with your target roles in mind, not at random.
## Leaderboard
The leaderboard ranks members by learning activity. Use it for momentum — a visible streak is a strong motivator — but remember the goal is capability, not rank. One finished course beats ten started ones.
## Getting the most from it
- **Schedule it.** Two fixed sessions a week beats waiting for free time that never arrives.
- **Finish before you start.** Complete the current course before enrolling in the next; completion is what produces certificates and momentum.
- **Pair learning with practice.** Apply what a module teaches in your current work or in an [assessment](/members/assessments/overview) — applied knowledge is what interviews surface.
## Related
- [Your analytics](/members/grow/your-analytics)
- [Understanding match scores](/members/jobs/match-scores)
- [Referrals](/members/grow/referrals)
---
# Club AI
URL: https://docs.thequantumclub.com/members/grow/club-ai
> Talk to the intelligence layer of The Quantum Club as an assistant that knows your search, cites its sources, and can take action when you confirm it.
## What Club AI is
Club AI is the intelligence layer of The Quantum Club. You meet it everywhere — match scores, offer analysis, cover letters — but you can also talk to it directly as an assistant. Unlike a generic chatbot, it answers from your own context inside the platform: your profile, your applications and their stages, your tasks, and your meetings. It cites the in-app facts it used, and when you ask it to do something, it can act on your behalf after you confirm.
## The four modes
Choosing the right mode is most of the skill. A toggle in the prompt box switches between them, and the placeholder text changes to tell you which one is active.
**Normal** is the default. The assistant answers directly from your in-app context, cites the facts it used, and recommends a next action. Use it for quick questions where you already trust the context — "what stage is my application at Acme?" or "what should I work on next?"
**Search** is for questions whose answer depends on facts the platform does not hold — companies, markets, current context. It uses your in-app context first, then flags what needs outside verification rather than inventing it. Toggle it on when freshness matters.
**Deep Think** trades speed for rigor. The assistant reasons longer, stays structured, and is explicit about its assumptions before it concludes. Use it for judgment-heavy questions: comparing two offers with different risk profiles, planning a pivot, deciding how to handle a negotiation. Expect a slower, substantially better answer.
**Canvas** produces work as a concrete artifact you can see and iterate on, instead of a reply in the chat. Use it when the output is a thing rather than an answer: a plan, a document draft, something with shape.
A practical rule: facts you have → Normal, facts you need → Search, decisions → Deep Think, artifacts → Canvas.
## What it knows about you
Club AI is scoped to you. It reads only your own candidate context — never another member's, and never internal platform data:
- **Your profile** — title, current company, location, availability, and how complete your profile is.
- **Your applications** — each one's role, company, stage, and match score, most recent first.
- **Your tasks** — what is open, its priority, and what is due.
- **Your meetings** — upcoming sessions and their summaries.
Because the answer is built from this, a thin or out-of-date profile produces a thinner answer. Keeping your [profile](/members/get-started/complete-your-profile) current is the single biggest lever on answer quality.
## Citations you can check
Club AI does not ask you to take its word. When it uses an in-app fact, it cites the source, and the assistant message shows which categories of your data fed the answer — Profile, Applications, Open roles, Tasks, Conversation memory, Documents, and Meetings among them. If the context does not contain what you asked about, it says so plainly and asks for the missing source rather than guessing. Treat a cited answer as checkable and an uncited claim as something to verify.
## Memory across the conversation
Each conversation is saved and named, so you can leave and come back to it. Within a thread, the assistant carries the history of what you have discussed, so you can refine — "now make it more direct", "you ignored the relocation factor" — instead of restarting. When your live situation and an earlier answer disagree, the current context wins: if an application has moved stage since the assistant last mentioned it, the fresh fact overrides the stale one. Start a new conversation when you switch topics, so old context does not bleed into a fresh question.
## Actions it can take
Club AI is more than an answer engine. When it helps, it can act through the platform — but the experience is built around your confirmation, not its autonomy. What it can do for you as a member includes:
- **Move you around the product** — open the right page when that is the fastest path, after telling you why.
- **Work on your search** — find roles, analyze how a job fits you, research a company, draft a cover letter, or prepare interview questions and a briefing.
- **Manage your tasks** — create a task, create several at once, reschedule them, or suggest what to do next.
- **Handle scheduling** — propose meeting times, find open slots, check for conflicts, and book.
- **Draft outreach** — write a message or schedule a follow-up for you to review.
Anything that writes — applying to a role, sending a message, booking or cancelling a meeting — pauses for your explicit confirmation before it happens. You see what the assistant is about to do and approve it; it does not act behind your back. Reading and drafting are free; committing is yours.
## Writing good prompts
The quality gap between a weak and strong prompt is enormous. Three habits close it:
- **Give context, not keywords.** "Review this offer: base X, equity Y, my current comp Z, my priority is learning rate" beats "is this offer good".
- **State the output you want.** "Give me three options with trade-offs" or "draft this in under 200 words" shapes the answer before it is written.
- **Iterate instead of restarting.** The second message — "now make it more direct" or "you ignored the relocation factor" — is where the real value appears.
Good member prompts in practice: "Deep Think: I have offers A and B [details]. I optimize for career growth over cash. Argue both sides, then recommend." Or with Search on: "What should I know about [company] before a final-round interview next week?" You can also attach a file — paste in a job description or a document and ask the assistant to work against it directly.
## Limits to respect
- **It advises; you decide.** Club AI never makes decisions about your applications or offers — humans do, including you. Treat its output as a strong second opinion, and remember that every action it takes is one you confirmed.
- **It works from what it is given.** Out-of-date profile data or a vague prompt produce confident-sounding answers built on sand. If the context is missing, the assistant will say so — believe it.
- **Verify what matters.** For high-stakes facts — compensation norms, contract terms — confirm independently or ask your Talent Strategist. The strategist knows things no model does.
## Related
- [Compare offers](/members/jobs/compare-offers)
- [Cover Letter Builder](/members/grow/cover-letter-builder)
- [The AI interview coach](/members/meetings/ai-coach)
---
# Cover Letter Builder
URL: https://docs.thequantumclub.com/members/grow/cover-letter-builder
> Generate a cover letter written against one specific role, then refine it until it sounds like you and no one else.
Prerequisites: a complete [profile](/members/get-started/complete-your-profile) — the builder writes from what your profile says about you.
## Generate and refine
### Start from the role
Open the job you are applying to and choose **Generate a Cover Letter**. Starting from the job detail page matters: the builder writes against that specific role's requirements instead of producing a generic letter.
### Generate the draft
The builder combines the role's requirements with your profile — skills, work history, outcomes — and produces a first draft tailored to the position.
### Read it as the hiring manager
Before editing, read the draft once asking a single question: would this make me want to meet this person? Mark every sentence that any candidate could have written.
### Refine
Replace the generic sentences with specifics only you can claim — a number, a named project, a reason this company. Ask for revisions with direction: shorter, more direct, lead with the strongest achievement. Iterating on the draft beats regenerating from scratch.
### Final pass and use
Trim to one focused page or less, check the company and role names are exact, and attach it to your application.
You should now have a cover letter that names the role, leads with your strongest relevant evidence, and contains at least two claims only you could make.
## What separates a good letter
- **Specificity.** One concrete outcome with a number does more than three paragraphs of qualities.
- **Their problem, your evidence.** The strongest structure is: here is what this role needs, here is proof I have done exactly that.
- **Brevity.** Hiring managers skim. Under 250 words, ruthlessly relevant, beats a full page of competence.
Never send the first generation unedited. The AI produces a strong structure from your profile, but the details that get interviews — the named project, the genuine reason for wanting this company — have to come from you.
## Related
- [Apply and track applications](/members/jobs/apply-and-track)
- [Club AI](/members/grow/club-ai)
- [Complete your profile](/members/get-started/complete-your-profile)
---
# Referral earnings and payouts
URL: https://docs.thequantumclub.com/members/grow/referral-earnings
> Follow a referral from projected reward to paid out — how earnings are calculated, approved, and tracked, with nothing left to guess.
Your earnings live in the referrals hub at `/referrals`. This page covers the money: how an earning is calculated, the states it moves through, and how it becomes a payout. For the basics of referring and the tier ladder, see [referrals and invites](/members/grow/referrals).
## How an earning is calculated
An earning is created against the placement your referral produces, not against the sign-up. The amount is the placement fee for that hire multiplied by your share of it. While the referral is still in pipeline, the hub shows a **projected** figure — the same calculation weighted by how likely the application is to reach a hire at its current stage. That is why your projected number moves as a referral advances or stalls.
Projected rewards are estimates from live pipeline probability. They are not promises. The figure firms up as the application advances and only becomes confirmed when the hire is real.
## The states an earning moves through
Each earning carries a status you can read directly in the hub:
| Status | What it means |
| --- | --- |
| **Projected** | The referral is in pipeline. The amount is an estimate weighted by stage probability. |
| **Qualified** | The referral was hired. The earning is confirmed and waiting to be paid. |
| **Paid** | The payout was approved and settled. It is recorded with a payment reference. |
| **Cancelled** | The application was rejected or withdrawn, so no earning is due. |
## The payout approval flow
Payouts are reviewed and released by The Quantum Club — you do not approve your own. A qualified earning becomes a payout that moves through review, approval, and settlement. When it is marked paid, the matching earning flips to **Paid** and a payment reference is attached, so every settled reward is traceable.
## Tracking what you have earned
The earnings view separates what is real from what is still building:
- **Realized Rewards** — confirmed earnings from placed referrals.
- **Projected Rewards** — estimates from your active pipeline.
- **Earnings history** — every earning with its status, grouped by year, with paid and outstanding totals to support your own records.
## Notifications
You are notified as referrals move and money lands. Hire and payout events can reach you by email; pipeline events such as a new sign-up or a stage advance appear in your activity feed. You control which of these you receive in your referral notification preferences.
### Watch projected turn to qualified
When a referral is hired, its earning moves from Projected to Qualified. That is your signal the reward is confirmed.
### Wait for approval
The Quantum Club reviews and releases the payout. You receive a payout notification when it settles.
### Reconcile from history
Use the earnings history, grouped by year, to check paid versus outstanding for your own records.
You can tell the status of each earning, know that payouts are released by The Quantum Club after a hire, and find your paid-versus-outstanding totals by year.
## Related
- [Referrals and invites](/members/grow/referrals)
- [Your analytics](/members/grow/your-analytics)
---
# Referrals and invites
URL: https://docs.thequantumclub.com/members/grow/referrals
> Refer members and companies, watch your pipeline build, and earn from the placements your network produces.
## How referrals work
The referrals hub at `/referrals` is where you bring people into The Quantum Club and get rewarded when those introductions turn into placements. There are two directions to refer:
- **Refer a Member** — introduce a strong operator into the network. When your referral leads to a placement, you earn from the placement fee.
- **Claim Company** — connect a company into the network through its referral program and earn from the hiring it generates.
Use **Share Link** to get your personal referral link; anyone who joins through it is attributed to you automatically. The **Invites** tab tracks invitations you have sent.
## Tracking your pipeline and earnings
The hub shows your full referral economics, not vanity counts:
- **Pipeline** — referrals currently moving through stages, with notifications as each one advances.
- **Total Revenue Generated** — placement fees produced by your referrals.
- **Realized Rewards** — confirmed earnings from placed referrals.
- **Projected Rewards** — estimates from your active pipeline, so you can see what is building before it lands.
- **Activity** and **History** — the running record of everything your network has done.
## The tier ladder
Placements move you up a tier ladder. The hub shows your current tier, your progress to the next one, and how many placements remain to get there. Higher tiers carry a percentage bonus on rewards — the program pays consistency, not one lucky introduction.
Because earnings come from placements, not sign-ups, one excellent referral outearns ten casual ones. Refer people you would genuinely vouch for — that is also what keeps the network worth joining.
## Achievements and challenges
Milestones unlock achievements as you go — placements, tier upgrades, streaks. Time-boxed **challenges** appear periodically with their own leaderboards; choose **Join Challenge** while one is active to compete. The **Leaderboard** tab shows where you stand among referrers.
## Getting started
### Open the referrals hub
Go to `/referrals` and copy your link with **Share Link**.
### Make your first introduction
Send the link to one person who genuinely belongs in the network, with a personal note about why.
### Watch the pipeline
Follow their progress in the Pipeline tab. You are notified as they advance, and rewards appear as projected, then realized.
You should now see your referral link copied and your first invite tracked under Invites.
## Related
- [Your analytics](/members/grow/your-analytics)
- [Welcome to The Quantum Club](/members/get-started/welcome)
---
# Your analytics
URL: https://docs.thequantumclub.com/members/grow/your-analytics
> Read your application funnel like a diagnostic — find the stage where applications stall, and fix that one first.
Your analytics live at `/my-analytics`.
## What you see
Your analytics turn your activity on The Quantum Club into a picture of how your search is actually performing:
- **Application funnel** — how your applications flow from Applied through Screening, Interview, and Offer, and where they stop. The funnel shape is the single most useful diagnostic in a job search.
- **Interview performance** — how often applications convert into interviews and how interviews convert onward, so you can tell whether your profile or your interviewing is the current constraint.
- **Activity and engagement** — what you have applied to, saved, and completed over time, which keeps you honest about volume and consistency.
## How to read the funnel
The funnel tells you where to focus by showing where applications die:
| Where applications stall | What it usually means | What to do |
| --- | --- | --- |
| Few applications at all | Volume problem | Set a weekly application target; use [match score sorting](/members/jobs/match-scores) to spend it well |
| Applied, but rarely Screening | Profile or targeting problem | Strengthen your [profile](/members/get-started/complete-your-profile); apply to higher-match roles |
| Screening, but rarely Interview | Positioning problem | Tailor applications; add a [cover letter](/members/grow/cover-letter-builder); ask your Talent Strategist what companies are reacting to |
| Interview, but rarely Offer | Interview performance | Drill with the [Interview Prep AI](/members/meetings/ai-coach); review your [meeting insights](/members/meetings/after-the-meeting) |
## Make it a habit
### Review weekly
Open `/my-analytics` once a week, same day each week. Trends matter more than any single number.
### Find the one constraint
Identify the single stage where the most applications stall. Fix that, not everything at once.
### Change one thing
Adjust the matching input — profile, targeting, preparation — that addresses the constraint.
### Measure the shift
Next week, check whether the constrained stage improved. If it did, move to the next constraint; if not, try a different fix.
You should now know which funnel stage is your current bottleneck and the one change you are making this week.
A thin funnel after two weeks means almost nothing; a consistent stall over six weeks means a lot. Give the data enough volume to be honest with you before reacting to it.
## Related
- [Apply and track applications](/members/jobs/apply-and-track)
- [Understanding match scores](/members/jobs/match-scores)
- [The AI interview coach](/members/meetings/ai-coach)
---
# Apply and track applications
URL: https://docs.thequantumclub.com/members/jobs/apply-and-track
> Submit an application in three steps and follow it through every stage to an outcome.
Prerequisites: an approved account with a [complete profile](/members/get-started/complete-your-profile) — your resume travels with every application.
## Apply to a role
### Open the role
From [Jobs](/members/jobs/find-jobs), open a listing to see the full description, requirements, responsibilities, and salary range.
### Choose Apply Now
Select **Apply for this Position**. If you have already applied, the listing shows **Already Applied** instead — you cannot double-apply.
### Confirm submission
You see a confirmation once the application is in. From this moment it is visible to the hiring company and your Talent Strategist.
Many roles benefit from a tailored cover letter. From the job detail page, choose **Generate a Cover Letter** to open the [Cover Letter Builder](/members/grow/cover-letter-builder) pre-loaded with that role.
## Track your applications
Open the **Applications** tab on the Jobs page to see everything you have in flight.
### What the statuses mean
| Status | Meaning |
| --- | --- |
| Applied | Submitted and visible to the company |
| Screening | Being reviewed against the role's requirements |
| Interview | You are in the interview loop |
| Assessment | An assessment has been assigned — see [Assessments](/members/assessments/overview) |
| Offer | The company has extended an offer |
| Hired | Signed and done |
| Rejected | The company moved on with someone else |
### The timeline
Each application has a timeline showing stage changes as they happen, so you always know where things stand without chasing anyone.
### Where feedback appears
When a company or your Talent Strategist leaves feedback on an application, it appears on the application itself. Decline notices include any feedback the company chose to share. You are also notified through your enabled channels — manage those under [Settings](/members/account/settings).
You should now see your application in the Applications tab with an Applied status and a timeline entry.
## Related
- [Understanding match scores](/members/jobs/match-scores)
- [Compare offers](/members/jobs/compare-offers)
- [Your analytics](/members/grow/your-analytics)
---
# Club Sync
URL: https://docs.thequantumclub.com/members/jobs/club-sync
> Let The Quantum Club apply to your strongest-matching roles on your behalf — only after you turn it on, and only on the terms you set.
Club Sync applies to roles for you automatically, so a strong match never passes
while you are not looking. It is off until you turn it on, it follows rules you
choose, and you can switch it off at any time.
Club Sync never acts without your explicit consent. It stays off by default; it
runs only after you enable it; and turning it off stops it immediately. You are
in control before, during, and after.
## What Club Sync does
When Club Sync is on, The Quantum Club submits applications on your behalf to
roles that clear the match threshold you set. Each application is filed the same
way a direct application is — it enters your Applications list and the company's
pipeline, marked as a Club Sync application so its origin is clear. Club Sync
runs on a regular schedule and you receive a summary of every application
submitted for you.
Club Sync only ever applies. It does not accept offers, decline roles, schedule
interviews, or make any binding decision for you — those stay yours.
## Turning it on
Club Sync is off until you enable it. You turn it on from your jobs view, where
a confirmation step asks you to set your terms before anything is submitted:
- **Match threshold** — the minimum match score a role must reach before Club
Sync will apply. You set it on a slider; the default is 90% and the floor
is 80%, so Club Sync only ever applies to your strongest fits.
- **Exclude your current employer** — on by default, so Club Sync does not apply
to roles at the company where you work.
- **Notify before applying** — choose to be told about each application.
- **Profile and dossier sharing** — choose how much of your profile travels with
a Club Sync application.
Your choices are recorded as a consent receipt the moment you confirm, so there
is a clear record of what you agreed to and when.
## Pausing or turning it off
Turn Club Sync off from the same control you used to turn it on. Once off, no
further applications are submitted on your behalf. Applications already filed
stay in your Applications list, where you track and manage them like any other.
## What data it uses
Club Sync works from the profile you already maintain. It applies based on your
match score for a role, and the application carries the profile and dossier
detail you chose to share when you turned it on. Your application is visible to
the hiring company and your Talent Strategist — not the wider membership — the
same as any application you submit yourself.
---
# Compare offers
URL: https://docs.thequantumclub.com/members/jobs/compare-offers
> Line your offers up side by side — compensation, terms, and the details that differ — and respond from one place.
Prerequisites: at least one application that has reached the Offer stage. The tool lives at `/offers`.
## Compare your offers
### Open the Offers page
Choose **Offers** in the navigation. Every offer extended to you through the platform appears here. If the page is empty, you have no active offers yet — **Browse Jobs** takes you back to the board.
### Filter by status
Switch between **All**, **Pending**, **Accepted**, and **Declined** to focus on what needs a decision.
### Switch to Compare view
The default **Cards** view shows each offer individually. Switch to **Compare** to line offers up side by side — compensation, terms, and the details that differ — so trade-offs become visible instead of mental arithmetic.
### Read the Club AI analysis
Each offer includes a **Club AI Analysis** that breaks down how the offer sits against your expectations and the market. Use **Get Negotiation Help** for guidance on what to push on and how. Treat both as preparation for your own judgment, not a decision made for you.
### Respond
From an offer you can **Accept**, **Decline**, or use **Propose Changes** to open a negotiation rather than answering yes or no. Your Talent Strategist sees the same offer and can advise before you commit.
Negotiate after receiving an offer, not during early interviews. Once an offer is on the table you have leverage; before that you only have a conversation.
You should now see your offers in Compare view with a Club AI Analysis on each, and know which action — accept, decline, or propose changes — you are taking.
## Related
- [Apply and track applications](/members/jobs/apply-and-track)
- [Your analytics](/members/grow/your-analytics)
- [Club AI](/members/grow/club-ai)
---
# Find jobs
URL: https://docs.thequantumclub.com/members/jobs/find-jobs
> Search the curated board, cut it down with filters and the map view, and save the roles worth your time.
Prerequisites: an approved member account. Jobs live at `/jobs`.
## Search and filter
### Open the Jobs page
Choose **Jobs** in the navigation. You see curated roles for The Quantum Club members — every listing has been placed there deliberately, not scraped.
### Search
Use the search field — **Search jobs by title, company, or skills...** — to query across titles, companies, and skills in one box.
### Apply filters
Open **Filters** to narrow by **Location**, **Employment Type**, **Salary Range (EUR)**, **Companies**, **Departments**, and **Remote only**. The header shows how many roles match your current filters. Use **Clear All Filters** to reset.
### Sort the results
Sort by what matters right now — newest first, **Match Percent** to lead with your strongest fits, or **Salary High To Low**.
### Switch to the map view
The map view plots roles geographically, which is the fastest way to scan opportunities around a city or a relocation target.
## Save roles
On any listing, choose **Save Job** to bookmark it. Saved roles collect in your saved list so you can compare, revisit, and apply when ready. Choose **Remove from Saved** to drop one.
If you switch on Club Sync, you automatically apply to roles with a 90 percent or higher match score. Keep your [profile](/members/get-started/complete-your-profile) accurate before enabling it — auto-apply is only as good as the profile behind it.
## Recommendations
The **Recommended for You** section surfaces roles based on your profile, alongside similar and trending jobs. These reflect your current skills, experience, location, and salary expectations — another reason to keep the profile current.
You should now see a filtered job list (or map) and at least one role in your saved jobs.
## Related
- [Apply and track applications](/members/jobs/apply-and-track)
- [Understanding match scores](/members/jobs/match-scores)
- [Complete your profile](/members/get-started/complete-your-profile)
---
# How applications work
URL: https://docs.thequantumclub.com/members/jobs/how-applications-work
> Your path from finding a role to signing an offer — the stages an application moves through, and the people and tools behind it.
Applying through The Quantum Club is not sending a résumé into a void. Every application moves through visible stages, a named Talent Strategist supports you, and you can see where you stand at any moment. This page is the whole journey; each step links to the page that goes deep.
## Your journey, end to end
| Step | What happens | Goes deep in |
| --- | --- | --- |
| Discover | Browse a curated board of roles matched to your profile | [Find jobs](/members/jobs/find-jobs) |
| Match | Each role shows how closely it fits you | [Match scores](/members/jobs/match-scores) |
| Apply | Submit in a few steps; your profile and résumé travel with it | [Apply and track](/members/jobs/apply-and-track) |
| Track | Follow the application through every stage on a live timeline | [Apply and track](/members/jobs/apply-and-track) |
| Decide | Compare and respond to offers | [Compare offers](/members/jobs/compare-offers) |
## How roles reach you
You are not scrolling an open job board. The Quantum Club shows you roles whose requirements line up with your profile, ranked by a match score, with the strongest fits badged as your best matches. If you turn on Club Sync, the platform can apply on your behalf to roles that clear a match threshold you set — see [match scores](/members/jobs/match-scores) for how that threshold works.
## What the stages mean
An application moves through Applied, Screening, Interview, Assessment, and Offer, ending in either Hired or a decline. Each change lands on the application's timeline as it happens, so you always know where you stand without chasing anyone. [Apply and track](/members/jobs/apply-and-track) lists every status in full.
## Your Talent Strategist
From the moment you apply, a named human — your Talent Strategist — can see the application and works on your behalf: shaping how you are presented, preparing you for interviews, and staying involved as the role progresses. You are never negotiating alone.
## Preparing for interviews
When you reach the interview stage, you can prepare with role-specific guidance and a [practice space](/members/meetings/ai-coach), alongside your Strategist's coaching. Preparation is support that is there whenever you want it, not a test of access.
## Your data, your control
Your application is visible to the hiring company and your Talent Strategist — not the wider membership. Feedback a company chooses to share appears on the application itself, including with a decline. You control what your profile shows and how you are notified; see [privacy](/members/account/privacy) and [settings](/members/account/settings).
## Where to go next
---
# Understanding match scores
URL: https://docs.thequantumclub.com/members/jobs/match-scores
> Know exactly what the match percentage measures — and how to use it without letting it decide for you.
## What goes into a score
Club AI compares your profile against each role across several dimensions:
- **Skills** — overlap between the skills on your profile and what the role requires, weighted by how central each skill is to the work.
- **Experience** — your seniority and work history against the role's experience level.
- **Location** — where the role sits relative to your location, mobility, and remote preferences.
- **Salary alignment** — the role's range against your stated compensation expectations.
The output is the match percentage you see on listings, the **Best Match** badge on recommendations, and the **Match Percent** sort option on the Jobs page.
## What a score means
A high score means the role's stated requirements line up closely with what your profile says about you. It is a prioritization signal: with limited time, start with your strongest matches, because those are the applications where your profile already makes the case.
Scores also power Club Sync. With auto-apply enabled, you automatically apply to roles scoring 90 percent or higher — the score acts as your threshold.
## What a score does not mean
A match score is not a verdict, and it is worth being precise about its limits:
- **It does not predict whether you get the role.** Hiring decisions are made by humans — companies, with input from your Talent Strategist — not by the score.
- **It is not a measure of your ability.** A 60 percent match means the role asks for things your profile does not show, not that you are a 60 percent candidate.
- **It only knows what your profile says.** A skill you have but never listed is invisible to matching. Stale location or salary data drags scores on roles that actually fit.
- **A lower score is not a closed door.** If a role excites you and you can make the case, apply. The score ranks fit on paper; it does not read ambition.
Scores support human judgment — they never replace it.
Match quality is a direct function of profile quality. Before questioning a string of low scores, review [Complete your profile](/members/get-started/complete-your-profile) — most scoring surprises trace back to missing skills or outdated preferences.
## How to use scores in practice
- Sort by **Match Percent** when starting a search session, then read the top listings properly rather than applying blind.
- Treat 90 percent and above as "apply today" territory.
- For mid-range scores, check which dimension is dragging — often it is location or salary, which you may consider flexible even if your profile says otherwise.
- Update your profile, then watch how scores shift. That feedback loop tells you what the market values in your profile.
## Related
- [Find jobs](/members/jobs/find-jobs)
- [Complete your profile](/members/get-started/complete-your-profile)
- [Apply and track applications](/members/jobs/apply-and-track)
---
# After the meeting
URL: https://docs.thequantumclub.com/members/meetings/after-the-meeting
> Find the recording, transcript, and AI insights from your Quantum Meetings call — and know exactly when recording applies to you.
## What gets created
When a host enables recording for a meeting, three things can come out of it:
- **The recording** — the full video of the call, available to download or share once processing finishes.
- **The transcript** — a written record of what was said, which makes the meeting searchable and reviewable without re-watching.
- **AI insights** — analysis generated from the meeting, surfacing key moments and takeaways so you can review a one-hour interview in minutes.
## Where to find them
Open the meeting from your meetings list after it ends. Recordings, transcripts, and insights attach to the meeting itself, so everything from one interview lives in one place. From a saved recording you can **Download Recording**, **Share Recording**, or **Create Clip** to cut a shareable segment instead of sending the whole call.
Recordings and transcripts appear after processing, not instantly when the call ends. If a fresh meeting shows nothing yet, give it a little time and reload.
## Recording consent, in plain language
Recording is a host decision — and you always know when it applies to you, before you participate.
In practice:
- When the host has enabled recording, you see a **Recording Consent Required** notice before you participate, telling you the meeting will be recorded.
- Recording exists for quality and review purposes — typically so interviewers and candidates can revisit what was actually said.
- If you are not comfortable being recorded, say so before the meeting starts. Declining consent is always your right; raise it with the host or your Talent Strategist so the meeting can proceed in a way that works for everyone.
For how your data is handled more broadly, see [Privacy and your data](/members/account/privacy).
## How to use the outputs
- **After an interview**, read the AI insights the same day. They show where the conversation went well and where you hedged — direct input for your next [Interview Prep session](/members/meetings/ai-coach).
- **Use the transcript** to capture exact phrasing — the role's priorities as the interviewer described them are gold for follow-ups and offer conversations.
- **Use clips** when one segment matters: a question you want your strategist's read on travels better as a two-minute clip than a link to a full recording.
## Related
- [Join a meeting](/members/meetings/join-a-meeting)
- [The AI interview coach](/members/meetings/ai-coach)
- [Privacy and your data](/members/account/privacy)
---
# The AI interview coach
URL: https://docs.thequantumclub.com/members/meetings/ai-coach
> Turn the Interview Prep AI into a sparring partner — real questions, honest critique, and sharper stories before the conversation that counts.
## What it does
Interview Prep is a focused AI chat for getting ready to interview. Instead of generic advice, it works from context: tell it the role, the company, and what stage you are at, and it helps you rehearse answers, anticipate questions, sharpen your stories, and stress-test your reasoning before the real conversation.
It complements — never replaces — your Talent Strategist. Use the AI for repetition and drilling; use your strategist for judgment calls about the specific company and process.
## How to use it well
### Bring the context
Start by telling it which role you are interviewing for and paste the parts of the job description that matter. Specific context produces specific preparation; a vague opening produces a vague session.
### Ask it to interview you
Have it play the interviewer for the role and ask you real questions one at a time. Answer out loud or in writing as you actually would, rather than describing what you would say.
### Get critique, not comfort
After each answer, ask what was weak, what was missing, and what a stronger version sounds like. Ask it to push back on your claims — interviewers will.
### Drill your stories
Work your two or three core achievement stories until they are tight: situation, action, outcome, numbers. Ask the chat to find the moments where you ramble or undersell.
### Close with the hard questions
End the session on the questions you fear — the gap on your CV, the failed project, the salary question. Rehearsed once is nervous; rehearsed five times is calm.
You should now have rehearsed your core stories and your hardest questions, with a concrete fix noted for each weak answer.
The best sessions happen one or two days before the interview — close enough to be fresh, far enough to act on what you learn. A final ten-minute warm-up on the day works well too.
## What it is good and bad at
Strong at: question drilling, structuring answers, spotting filler, rehearsing difficult moments, summarizing a job description into likely themes.
Weak at: insider knowledge of a specific interviewer's style, and anything that depends on information you have not given it. It works from what you provide — feed it well.
## Related
- [Join a meeting](/members/meetings/join-a-meeting)
- [After the meeting](/members/meetings/after-the-meeting)
- [Club AI](/members/grow/club-ai)
---
# In the meeting
URL: https://docs.thequantumclub.com/members/meetings/in-the-meeting
> Use the tools inside a Quantum Meetings room — polls, Q&A, whiteboard, captions, live translation, and reactions — without leaving the call.
Once you are in the room, the conversation is not the only thing happening. A Quantum Meetings room carries a set of tools for participating beyond your microphone — vote, ask, draw, read along, and react, all in the same window.
## Polls
When the host runs a poll, it appears in the room for you to answer. Open the poll, choose your option, and submit — your vote is counted live, and results can be shown back to the room as a chart. Polls are a quick way to read the room without everyone talking over each other.
## Q&A
Questions have their own channel so they do not get lost in the conversation. Use the Q&A panel to post a question, which the host can address in turn rather than tracking who raised what verbally. It keeps a clear queue in a larger session where speaking up is harder.
## Whiteboard
The room includes a shared whiteboard for when words are not enough. Open the whiteboard to sketch a diagram, map a flow, or work through a problem visually with the other participants, all on the same canvas in real time.
## Live captions
Turn on captions to read what is being said as it is spoken. Captions transcribe the conversation live on screen — useful in a noisy environment, on a weak connection, or any time reading along is easier than listening.
On-screen captions help you follow the call as it happens. The searchable transcript you review afterward is produced separately from the recording — see [After the meeting](/members/meetings/after-the-meeting).
## Live translation
When you and another participant do not share a first language, live translation bridges it. The room can translate the conversation so each person can follow along in a language they read comfortably, rather than the meeting defaulting to whoever is most fluent in one tongue.
## Reactions
React without interrupting. Send an emoji reaction and it appears on screen for everyone — a quick way to agree, applaud, or signal you have a point without unmuting and cutting across the speaker.
You should be able to answer a poll, post a question, open the whiteboard, switch on captions, and send a reaction — all without leaving the room.
## What you do not need to set up
These tools live in the room you are already in. There is nothing to install and no separate app — the room runs in your browser, and each tool opens in a panel beside the video. The host enables the ones a given meeting uses, so you may not see every tool in every call.
## Related
- [Join a meeting](/members/meetings/join-a-meeting)
- [After the meeting](/members/meetings/after-the-meeting)
- [The AI interview coach](/members/meetings/ai-coach)
---
# Join a meeting
URL: https://docs.thequantumclub.com/members/meetings/join-a-meeting
> Get into any Quantum Meetings call from a link — signed in or as a guest, even when your camera is blocked.
Prerequisites: a meeting link and a modern browser. An account is not required — guest links work without one.
## Join from a link
Open the meeting link while signed in to The Quantum Club. The room recognizes you — no name entry, no extra dialog. If the host has switched on **Require Approval**, you wait briefly while the host admits you; otherwise you go straight to the pre-join screen.
Meeting links work without a Quantum Club account when the host has allowed non-members. Open the link, enter your name (email is optional), and request to join. You may see **Waiting for Host** — the host will approve your entry shortly.
## Step by step
### Open the link
Click the invitation link. It opens directly in the browser — nothing to install.
### Grant camera and microphone access
The browser asks for permission to use your camera and microphone. Camera and microphone access is optional: grant access now, or join with devices off.
### Check your audio and video
On the pre-join screen, confirm your camera preview looks right and your microphone is picking up sound. Switch devices here if you have more than one.
### Join
Enter the room. You see your own tile and the meeting controls for camera, microphone, and leaving the call.
You should now be in the meeting room with your tile visible and controls along the bottom.
## If your camera or microphone is blocked
A denied permission does not lock you out. When access is blocked, the room shows a **Join Anyway** option — choose it to enter with your devices off. You can still hear and see the meeting, and you can enable devices later once you fix the browser permission.
To fix the permission itself: open your browser's site settings for the meeting page, set Camera and Microphone to Allow, then reload. The same applies if you initially clicked "Block" by accident.
Mobile browsers work the same way: open the link, grant or skip permissions, join. If the connection struggles on mobile data, moving to Wi-Fi usually resolves it — see [Troubleshooting](/members/account/troubleshooting).
## Related
- [The AI interview coach](/members/meetings/ai-coach)
- [After the meeting](/members/meetings/after-the-meeting)
- [Troubleshooting](/members/account/troubleshooting)
---
# Partners
URL: https://docs.thequantumclub.com/partners
> Hiring with The Quantum Club — publish roles, run a disciplined pipeline, and decide with evidence.
Company settings, billing, the audit log, and confidential searches.
---
# Audit log
URL: https://docs.thequantumclub.com/partners/administration/audit-log
> Answer "who did what, and when" for any team action — every entry recorded with actor and timestamp, filterable for compliance.
## Where to find it
Open the Partner Hub and select the **Audit Log** tab in the Operations group.
## What is logged
Every entry records three things:
- **Actor** — the team member who performed the action.
- **Action** — what happened, in plain terms.
- **Timestamp** — when it happened.
Logged actions cover the team activity that affects candidates and roles, including:
| Action | Example |
| --- | --- |
| **Candidate Moved** | A candidate advanced or moved between pipeline stages |
| **Job Created** | A new role was created |
| **Team Invited** | A teammate was invited to the workspace |
| **Application Rejected** | An application was declined |
## Filtering and search
Use the search box ("Search by user or action...") to find entries by teammate name or action keyword, and the **All Actions** filter to narrow the list to one action type — for example, only Candidate Moved events when reconstructing how a candidate progressed. If nothing matches, the log shows "No audit log entries found"; widen the filter before concluding an action never happened.
## Why it matters for compliance
The audit log is your evidence layer:
- **Accountability** — every consequential action is attributable to a person at a time. When a candidate asks why they were declined, or a hiring manager asks who moved a candidate, the answer is on record rather than in memory.
- **Process audits** — regulated hiring processes need to show decisions followed a defined path. Timestamped actor records are exactly what an auditor asks for.
- **Incident reconstruction** — if something looks wrong in your pipeline, the log shows what changed, who changed it, and when, which turns speculation into a five-minute lookup.
- **Access reviews** — combined with SCIM provisioning logs at the platform level, you can demonstrate both who had access and what they did with it.
Some areas keep their own focused trails on top of the workspace log: confidential searches record disclosure and access events in their own Audit Trail, and Hiring Committee sessions keep a decision audit trail. Check the relevant feature page when auditing those flows.
## Related
- [Confidential searches](/partners/administration/confidential-searches)
- [Hiring Committee](/partners/intelligence/hiring-committee)
- [SCIM provisioning](/platform/identity/scim)
---
# Billing and invoices
URL: https://docs.thequantumclub.com/partners/administration/billing
> Manage your subscription, payment method, and invoices — and act on a Past Due before it becomes a suspension.
**Prerequisites:** billing is restricted to Owner and Admin roles in your partner workspace. Other roles do not see billing data — see [roles and permissions](/partners/get-started/roles-and-permissions).
## Where to find it
Open the Partner Hub and select the **Billing** tab in the Operations group. The page is organized into three tabs: **Subscription**, **Billing Details**, and **Invoices**.
## Subscription
The **Your Subscription** panel shows your **Current Plan**, its **Status**, and the **Renews on** date. Payments are processed by Stripe; use **Update Payment Method** to change the card or payment details on file through Stripe's secure checkout — The Quantum Club never stores your card number.
Subscription statuses you may see:
| Status | Meaning |
| --- | --- |
| **Active** | Subscription is current |
| **Trial** | You are in a trial period |
| **Past Due** | A payment failed — update your payment method to avoid service interruption |
| **Canceled** | The subscription has been canceled |
| **Suspended** | Access is suspended for non-payment |
A Past Due status means a renewal payment failed. Update your payment method promptly to avoid service interruption for your whole team.
## Billing details
The **Billing Information** tab holds your company billing details used for invoicing — keep the legal entity name, address, and tax details current so invoices clear your accounts-payable process without rework.
## Invoices
The **Your Invoices** tab lists your invoices, including placement fee invoices, with two actions:
- **Download** — get the PDF for your records or finance team.
- **Pay Now** — settle an open invoice immediately through Stripe checkout.
### Update your payment method
Open **Billing** → **Subscription**, select **Update Payment Method**, and complete the Stripe form with the new details.
### Verify the change
Back on the Subscription tab, confirm the status shows **Active** and the renewal date is unchanged. If you were Past Due, any open invoice can be settled from the Invoices tab with **Pay Now**.
You should now see an Active subscription status, current billing details, and downloadable invoices in the Invoices tab.
## Related
- [Roles and permissions](/partners/get-started/roles-and-permissions)
- [Company settings](/partners/administration/company-settings)
- [Troubleshooting](/partners/administration/troubleshooting)
---
# Company settings
URL: https://docs.thequantumclub.com/partners/administration/company-settings
> Keep the company identity candidates actually see — profile, logo, branding, and culture statement — current and convincing.
**Prerequisites:** admin-level access in your partner workspace. See [roles and permissions](/partners/get-started/roles-and-permissions).
### Open your company profile
Sign in at [os.thequantumclub.com](https://os.thequantumclub.com) and open your partner settings, then select **Company Profile**.
### Complete the core fields
Fill in the profile fields candidates and the platform rely on:
- **Company Name** — the legal or trading name shown on your jobs.
- **Description** — what your company does, written for candidates rather than customers.
- **Industry** and **Company Size**
- **Headquarters** — your primary location.
- **Website** — candidates check it; make sure it is current.
### Upload your logo and set branding
Add your **Company Logo** — it appears wherever your company is shown, including job listings and candidate-facing surfaces. Review the **Branding** settings so your presence on the platform matches your brand elsewhere. A complete visual identity measurably improves how seriously candidates treat your roles.
### Write your culture statement
The **Company Culture** field is more than marketing copy: Club AI uses your culture statement when assessing culture alignment for candidates, so a specific, honest statement produces better matching than aspirational boilerplate. Describe how your team actually works — decision style, pace, remote posture — not how you wish it worked.
Round it out with **Benefits & Perks** so candidates can weigh the full offer before they apply.
You should now see your completed profile with logo, description, culture statement, and benefits — and your published jobs carrying the updated identity.
Some intelligence features depend on a linked, completed company profile — for example, Executive Briefing Decks show "No company linked" until company setup is finished.
## Related
- [Create and publish jobs](/partners/hiring/create-and-publish-jobs)
- [Club AI matching](/partners/intelligence/club-ai-matching)
- [Billing](/partners/administration/billing)
---
# Confidential searches
URL: https://docs.thequantumclub.com/partners/administration/confidential-searches
> Run a C-suite search the market is not supposed to know about — code names, tiered disclosure, and an audit trail of who knew what, when.
## When to use a confidential search
Some searches cannot be public: replacing an incumbent executive, building a team ahead of an unannounced move, or any C-suite role where the company's intent is market-sensitive. Confidential searches let you hire for these roles while controlling exactly who learns what, and when.
## How identity masking works
A confidential search separates what a role is from what candidates are allowed to see:
- **Code Name** — every confidential search carries a code name (for example, "Project Phoenix"). At the most restricted tier, this is the only name candidates see.
- **Actual Role Title** — the real title (for example, "Chief Technology Officer") stays hidden from candidates until disclosure is granted.
- **Tiered disclosure** — you set an **Initial Disclosure Level** controlling what candidates see at each tier, then grant fuller disclosure deliberately as candidates progress and sign what they need to sign.
Inside your workspace, the search list shows code names by default; hover to reveal the actual title. Access to confidential searches is restricted within your own team as well — only teammates working the search see it.
## The audit trail
Every confidential search keeps its own **Audit Trail** recording access and disclosure events. For searches where a leak has real cost, this gives you an answer to the question that matters afterwards: who knew what, and when. It complements the workspace-wide [audit log](/partners/administration/audit-log).
## Create a confidential search
**Prerequisites:** access to the **Confidential** tab in the Partner Hub Intelligence group.
### Open Confidential Searches
In the Partner Hub, switch to the **Intelligence** group and select **Confidential**. The page is titled **Confidential Searches**.
### Start a new search
Select **New Confidential Search**.
### Set the code name and actual title
In **Confidential Search Details**, enter a **Code Name** — pick something with no semantic connection to the role — and the **Actual Role Title**, which stays hidden from candidates until you grant disclosure.
### Choose the initial disclosure level
Set the **Initial Disclosure Level**. The tier descriptions show exactly what candidates see at each level. Start restrictive: you can always disclose more later, never less.
You should now see your search listed under Confidential Searches by its code name, with the actual title revealed only on hover.
The platform masks identities inside the hiring flow, but confidentiality also depends on your team: do not name the real role in Slack messages, calendar invites, or interview notes. Use the code name everywhere until disclosure is granted.
## Related
- [Audit log](/partners/administration/audit-log)
- [Roles and permissions](/partners/get-started/roles-and-permissions)
- [Hiring Committee](/partners/intelligence/hiring-committee)
---
# Placement fees and invoicing
URL: https://docs.thequantumclub.com/partners/administration/placement-invoicing
> Follow a successful hire from placement fee to a paid invoice — what you are billed, how to read each status, and how to settle securely.
**Prerequisites:** invoices are visible to Owner and Admin roles in your partner workspace. For the subscription side of billing, see [Billing and invoices](/partners/administration/billing).
When a hire closes through your pipeline, The Quantum Club raises a placement fee and turns it into an invoice you can review, download, and pay. This page covers the placement side of billing — your subscription is separate.
## How a placement fee becomes an invoice
A placement fee is recorded when a candidate is hired through your pipeline. The fee is a percentage of the candidate's gross annual salary, including holiday allowance — your agreed rate, or 25% where no rate was agreed — applied to the offer, in the currency on your account.
The Quantum Club then issues an invoice for that fee. Each invoice carries a unique number (formatted `TQC-YYYYMM-…`), an invoice date, and a due date 14 days out, unless your signed agreement sets a different payment term. Tax is applied to your billing location: Dutch BTW or local VAT where it applies, and a 0% reverse-charge line for EU business customers who have supplied a valid VAT number. Keep your [billing details](/partners/administration/billing) current so the right entity and tax treatment land on the invoice.
Your subscription renews on its own cycle through Stripe. Placement fees are one-off invoices raised per hire. Both appear in the **Invoices** tab, so the full picture is in one place.
## Read the invoice statuses
Open the Partner Hub, select **Billing**, and open the **Invoices** tab. Each invoice shows its number, date, due date, amount, and status:
| Status | What it means | What to do |
| --- | --- | --- |
| **Draft** | Being prepared on our side | Nothing yet — it is not due |
| **Sent** | Issued to you and payable | Review and pay |
| **Viewed** | Opened, still open for payment | Pay before the due date |
| **Overdue** | Past its due date | Settle promptly to keep your account in good standing |
| **Paid** | Payment received and reconciled | Keep the PDF for your records |
| **Cancelled** | Withdrawn — no payment due | No action |
## Pay and download
Each invoice offers up to two actions:
### Download the PDF
Use **Download** to get the invoice PDF for your finance team or accounts-payable process. Available once the invoice document is generated.
### Pay an open invoice
For an invoice that is **Sent**, **Viewed**, or **Overdue**, choose **Pay Now** to open a secure Stripe checkout for that exact amount. The Quantum Club never stores your card number.
### Confirm it cleared
After payment, the status moves to **Paid** once the payment is reconciled. A paid invoice no longer offers Pay Now.
You should now see your placement fee invoices in the Invoices tab, understand what each status means, and be able to download or pay any open invoice.
## The replacement guarantee
Every placement carries a replacement guarantee — a defined window in which a candidate who does not work out is replaced. The window is shown alongside your billing terms. Track how placements are performing against it on your [SLA dashboard](/partners/intelligence/sla-dashboard).
## Related
- [Billing and invoices](/partners/administration/billing)
- [SLA dashboard](/partners/intelligence/sla-dashboard)
- [Success metrics](/partners/intelligence/success-metrics)
---
# Troubleshooting
URL: https://docs.thequantumclub.com/partners/administration/troubleshooting
> Resolve the most common partner workspace problems, organized by symptom — most turn out to be configuration, not bugs.
This is almost always role- or assignment-based, not a bug:
1. **Check their role.** Some roles only see jobs they are assigned to. Compare what the teammate should see against [roles and permissions](/partners/get-started/roles-and-permissions).
2. **Check job-level assignment.** If your workspace assigns team members per job, confirm the teammate is on the job's team.
3. **Check for confidential mode.** Confidential searches are restricted to the teammates working them; appearing "missing" is the feature working. An admin can grant access if appropriate — see [confidential searches](/partners/administration/confidential-searches).
4. **Confirm the invitation completed.** A teammate who never accepted their invite can sign in with a personal account that has no company link. Re-send the invite from team settings if needed.
1. **Confirm the calendar is still connected** in the interviewer's settings. Expired authorizations are the most common cause — reconnect Google Calendar or Outlook and re-authorize.
2. **Check which calendar was connected.** A personal calendar connected instead of the work calendar produces "missing" events that are syncing correctly to the wrong place.
3. **Reschedule inside the platform.** Changes made directly in Google or Outlook do not update the candidate's invitation. Make reschedules in The Quantum Club so both sides stay aligned — see [calendar integration](/partners/integrations/calendar).
4. **For panel interviews**, every interviewer needs their own connected calendar; one missing connection makes the panel's availability look empty.
1. **Find who owns the next action.** Open the candidate and check the stage history — most "stuck" candidates are waiting on a specific person's review, feedback, or decision.
2. **Check for a committee gate.** If the stage feeds the Hiring Committee, the candidate waits until the voting session concludes — see [Hiring Committee](/partners/intelligence/hiring-committee).
3. **Check scorecard completeness.** Stages that require feedback hold candidates until interviewers submit scorecards. Chase the missing scorecard, not the stage.
4. **Use the SLA dashboard** to spot systemic stage delays rather than one-off ones — see [SLA dashboard](/partners/intelligence/sla-dashboard).
1. **Check the integration status.** In the Integrations hub, the Slack or Microsoft Teams card must show **Active**. If it shows Inactive, reconnect it — see [Slack and Teams](/partners/integrations/slack-and-teams).
2. **Check the destination channel.** Notifications may be flowing to a channel you are not in, or one that was archived.
3. **Check personal notification settings** for in-app and email notifications — they are configured per user under notification settings.
4. **Verify with a known event.** Move a test candidate or trigger a real action; if the event appears in the [audit log](/partners/administration/audit-log) but no notification arrives, the problem is delivery, not the event.
Billing is restricted to **Owner** and **Admin** roles by design. If you need invoice access:
1. Ask a workspace Owner or Admin to either retrieve the invoice for you or upgrade your role.
2. If you believe you already have an admin role, sign out and back in, then retry — then have an Owner verify your role in team settings.
3. See [billing](/partners/administration/billing) for what each tab contains once you have access.
If none of these resolve the problem, contact your Talent Strategist or reach support through the partner workspace at [os.thequantumclub.com](https://os.thequantumclub.com) with the candidate, job, or invoice reference and the time the problem occurred — the audit log timestamp speeds up every investigation.
## Related
- [Roles and permissions](/partners/get-started/roles-and-permissions)
- [Integrations overview](/partners/integrations/overview)
- [Audit log](/partners/administration/audit-log)
---
# AI communication assistant
URL: https://docs.thequantumclub.com/partners/crm/communication-assistant
> Let Club AI draft the message and translate the thread, so your team spends its time deciding what to say rather than how to phrase it.
## What the assistant does
Reaching out well takes time your team would rather spend on decisions. Club AI handles the wording: it drafts professional messages from a short brief, and it translates any message in a thread on demand. You stay in control — nothing sends without you.
## Drafting a message
Ask Club AI to draft a message and you give it the shape, not the sentences. It writes from two choices:
- **Type** — the purpose of the message: a follow-up, an introduction, a thank-you, a negotiation note, or a networking touch.
- **Tone** — formal, friendly, or casual, to match the relationship.
Club AI returns a draft you can use as is or edit before sending. It writes the message; the decision to send is always a human one.
### Set the brief
Tell Club AI who the message is for, the type, and the tone. Add a sentence of context — what prompted the message — and the draft sharpens accordingly.
### Review the draft
Read what comes back. Edit anything that does not sound like your team. The draft is a starting point, not a final word.
### Send it yourself
Sending stays in your hands. Club AI does not send a message on your behalf without your confirmation.
You should now have a drafted message in your own voice, ready to review and send.
## Translating a thread
Working across languages is common in a curated, international membership. Any message in a conversation can be translated on demand into a wide set of languages, and the translation is saved alongside the original so the thread stays readable for everyone who reads it later.
Translation also runs live in Quantum Meetings, so a conversation that crosses languages stays legible in the moment as well as in the record — see [Run interviews](/partners/meetings/run-interviews).
## Where it applies
| Surface | What the assistant offers |
| --- | --- |
| Message threads | On-demand translation of any message, saved with the original |
| Quantum Meetings | Live translation during a call |
| Club AI | Drafted messages by type and tone, for you to review and send |
The assistant drafts and translates — it does not act for you. Every message is reviewed and sent by a person, so the relationship stays yours.
## Related
- [Relationship tracking](/partners/crm/overview)
- [Run interviews](/partners/meetings/run-interviews)
- [Understanding Club AI matching](/partners/intelligence/club-ai-matching)
---
# Relationship tracking
URL: https://docs.thequantumclub.com/partners/crm/overview
> See every candidate relationship as one timeline — messages, emails, meetings, and decisions in order, with the engagement and sentiment read alongside.
## What relationship tracking does
Every interaction your team has with a candidate lives in one place. The Quantum Club assembles messages, emails, meetings, pipeline stage changes, and submitted scorecards into a single chronological feed per candidate, so you read the relationship as a story rather than reconstructing it from scattered tools. This is **Candidate Relationship Intelligence** — the Candidate Intel tab in your Partner Hub.
Tracking is scoped to your company. You see the candidates who have applied to your roles, and only your team's view of them.
## The unified timeline
Open any candidate and you get one feed that merges every source of contact:
| Source | What appears |
| --- | --- |
| Messages | Each message to or from the candidate, with direction |
| Emails | Subject and preview, with direction |
| Meetings | Interviews and calls held in Quantum Meetings |
| Stage changes | Every advance, hold, and move on the pipeline |
| Scorecards | Submitted interview feedback |
Because the timeline pulls from the same records your pipeline and interviews already write to, it stays current without anyone maintaining a separate log.
## Engagement and sentiment
Alongside the timeline, the platform reads the shape of the relationship:
- **Engagement score** — how active and responsive the relationship is, based on the interactions above.
- **Sentiment trend** — the direction of recent contact, summarized as **warming**, **cooling**, or **stable**, with the underlying points plotted over time.
- **Optimal outreach timing** — the day and hour your past exchanges with this candidate have landed best, so a follow-up reaches them when they tend to respond.
Engagement and sentiment are a read on the relationship, not a verdict on the candidate. Use them to decide who needs attention and when — then open the timeline and read the actual exchange before you act.
## Warm reactivation
Strong candidates who went quiet are easy to lose. Warm reactivation flags a relationship that has cooled but still has signal worth re-opening — someone you invested in who deserves a deliberate check-in rather than a cold restart. The flag points you to the moment; the timeline gives you the context to pick the thread back up.
## How it ties into hiring
Relationship tracking is the connective layer under the pipeline, not a separate workflow:
- **Pipeline** writes every advance, hold, and decline into the timeline as it happens — see [Manage your pipeline](/partners/hiring/manage-your-pipeline).
- **Interviews** add meeting records and scorecards to the same feed — see [Run interviews](/partners/meetings/run-interviews).
- **Club AI matching** uses the structured signals your team records, so a richer relationship history sharpens future shortlists — see [Understanding Club AI matching](/partners/intelligence/club-ai-matching).
The result is that the decision to advance, wait, or re-engage is made with the whole relationship in view.
## Related
- [AI communication assistant](/partners/crm/communication-assistant)
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
- [Understanding Club AI matching](/partners/intelligence/club-ai-matching)
---
# Overview
URL: https://docs.thequantumclub.com/partners/get-started/overview
> See what your team gets as a partner of The Quantum Club — curated members, a full pipeline, intelligence, and a named Talent Strategist — and how it fits together.
## What you get
The Quantum Club is a premium career platform. As a partner, your company hires from a curated membership of vetted professionals rather than an open job board. Four things make that work:
- **Curated members.** Every candidate you see has been through the platform's vetting and onboarding. You spend your time deciding, not filtering noise.
- **A full hiring pipeline.** Jobs with multi-stage pipelines, a kanban view for moving candidates, structured interview scorecards, offers with approval workflows, and structured declines — all in one place, all audited.
- **Intelligence.** Club AI matches candidates to your roles and learns from every advance and decline your team records. Briefing decks, market intelligence, and success metrics turn pipeline activity into decisions.
- **A Talent Strategist.** A named human who knows your brief, shapes your shortlist, and stays involved as roles progress.
## The shape of the product
Your workspace is the **Partner Hub** — the home screen for your hiring team inside the app at [os.thequantumclub.com](https://os.thequantumclub.com). From there you reach:
| Area | What it covers |
| --- | --- |
| Jobs | Create, publish, and manage roles with custom pipeline stages |
| Pipeline | Kanban view of candidates per job — advance, hold, decline |
| Interviews | Scheduling with calendar sync, scorecards, calibration |
| Offers | Create, approve, send, and track offers |
| Team | Members, roles and permissions, invites, activity |
| Quantum Meetings | Video interviews, instant meetings, recordings, and analysis |
## How a hire flows
A typical search moves through five phases: you publish a job with the pipeline stages you want, candidates enter through applications and Club AI matching, your team reviews and advances them stage by stage, interviews produce scorecards, and the search closes with an offer — or a structured decline that feeds back into matching quality.
Every advance and decline carries feedback. That feedback is not ceremony: Club AI uses it to learn what excellent looks like for your roles, and your future shortlists improve because of it.
## Where to go next
---
# Quickstart
URL: https://docs.thequantumclub.com/partners/get-started/quickstart
> Go from a fresh partner account to a published job with a live pipeline — plan for about five minutes.
**Prerequisites:** a partner account on The Quantum Club with permission to create jobs (Owner, Admin, or Recruiter).
### Sign in and open the Partner Hub
Sign in at [os.thequantumclub.com](https://os.thequantumclub.com). The **Partner Hub** is your team's home screen — jobs, pipeline, and team management all start here.
### Create the job
From your jobs view, start a new job. The creation flow walks you through the role in steps: the role details (title, seniority, employment type, department), requirements and nice-to-haves, locations and work mode, tools, and the pipeline stages the role will use.
If your company has created roles before, choose **Create from Template** to start from an existing job instead of a blank form.
You can save as a draft at any point. Nothing is visible to candidates until you publish.
### Publish
Choose **Publish Job**. Publishing makes the role visible to candidates and starts accepting applications. The job is created atomically — the role, its locations, tools, and pipeline stages all land together, so a published job is never half-configured.
You can **Unpublish to Draft** later if you need to take the role offline without losing anything.
### Watch the pipeline appear
Open the published job. Its pipeline view is live immediately, organized by the stages you chose — the default flow runs Applied, Screening, Interview, Assessment, Offer, Hired. As candidates apply or Club AI matches them in, they appear in the first stage, ready to advance.
### Invite a teammate
From your team area, choose **Invite Member** and assign a role. A Recruiter can run pipelines and create jobs; a Member acts on candidates for the jobs they are assigned to. Roles are explained in [Roles and permissions](/partners/get-started/roles-and-permissions).
You should now see your published job in the jobs list with status **Published**, an empty pipeline organized by stage, and a pending invitation in your team view.
## Related
- [Create and publish jobs](/partners/hiring/create-and-publish-jobs)
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
- [Set up your team](/partners/get-started/set-up-your-team)
---
# Roles and permissions
URL: https://docs.thequantumclub.com/partners/get-started/roles-and-permissions
> Give every teammate the right access — four team roles, plus per-job permissions for fine-grained control.
A teammate's access has two layers: their **team role**, which sets company-wide
capability, and their **per-job permissions**, which control what they can do on
each individual search.
## The four team roles
Every member of your company holds exactly one team role.
| Role | Best for | Company-wide capability |
| --- | --- | --- |
| **Owner** | The account holder | Full control, including billing, integrations, and transferring ownership. |
| **Admin** | Operational leads | Manage the team, roles, company settings, billing, and integrations. |
| **Recruiter** | The people running searches | Create and run jobs; work candidates on jobs they are assigned to. |
| **Member** | Interviewers and hiring managers | Act on candidates for the jobs they are assigned to; no team or billing control. |
A **Talent Strategist** is a Quantum Club advisor assigned to support your
searches — not a seat you assign to a teammate. You will not find Strategist or
Viewer in the team-role picker.
## Per-job permissions
Candidate and offer access is not fixed by role — it is set per teammate, per
job, when you add them to a search. This lets a Recruiter run point on one role
while only observing another. Each job assignment carries these switches:
- **View candidates** — see the pipeline for the job.
- **Schedule interviews** — book and manage interviews.
- **Advance candidates** — move candidates forward through stages.
- **Decline candidates** — decline with feedback.
- **Make offers** — create and send offers.
A teammate set as the job's **primary contact** holds all of these for that job.
Owners and Admins always have full access to every job in the company.
## How access is enforced
Permissions apply at the action, not the menu. Someone who can view a pipeline
but not advance candidates sees the same board without the advance control. If
you attempt an action outside your role or your job assignment, the platform
tells you directly — for example: "Your current job assignment does not include
permission to advance candidates for this role."
## Related
- [Set up your team](/partners/get-started/set-up-your-team)
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
---
# Set up your team
URL: https://docs.thequantumclub.com/partners/get-started/set-up-your-team
> Bring your hiring team in and keep membership current — invites, domain auto-provisioning, role changes, and clean removals.
**Prerequisites:** Owner or Admin role in your company.
## Invite team members
### Open the Team area
From the Partner Hub, open **Team**. You see your current **Team Members** list, each with a role badge, plus **Roles & Permissions** and **Team Activity**.
### Send an invite
Choose **Invite Member**, enter the person's work email, and pick their role. Recruiters run searches and create jobs; Members act on candidates for the jobs they are assigned to, without creating jobs or managing the team. See [Roles and permissions](/partners/get-started/roles-and-permissions) for the full matrix.
### The invitee accepts
The invitee receives an email and joins your company when they accept. They appear in the Team Members list with the role you assigned.
You should now see the new member (or their pending invite) in the Team Members list with the correct role badge.
## Domain auto-provisioning
Instead of inviting colleagues one by one, you can register your company's email domain. Anyone who signs up with a verified company domain is provisioned into your team automatically with a default role.
### Request your domain
In your company's domain settings, enter your domain (for example, `yourcompany.com`) and submit the request.
### Wait for verification
Domain requests are reviewed before activation — this protects every partner from domain squatting. Once approved, the domain shows as active.
Auto-provisioned teammates join with a conservative default role. Promote them deliberately from the Team area rather than granting broad access by default.
## Change a member's role
Open the member in the Team Members list and assign the new role. Role changes take effect immediately and are visible in Team Activity.
Only Owners and Admins manage team membership and roles. Keep at least two people with Owner or Admin access so your company is never locked out by one person's absence.
## Remove a member
From the Team Members list, choose remove on the member's row and confirm. Removal revokes their access to your company's jobs, candidates, and data. Their historical activity — scorecards, decline feedback, audit entries — remains attached to your records for continuity.
## Related
- [Roles and permissions](/partners/get-started/roles-and-permissions)
- [Company settings](/partners/administration/company-settings)
- [SCIM and SSO](/partners/integrations/scim-and-sso)
---
# Club Sync requests
URL: https://docs.thequantumclub.com/partners/hiring/club-sync-requests
> How Club Sync applications reach your pipeline, what the status on a job means, and how to handle candidates who arrive this way.
Club Sync brings strongly-matched members into your pipeline automatically, so a
high-fit candidate reaches you without either side waiting on a manual step. The
candidate is in full control of whether they take part — your job is to handle
the applications that arrive.
## How Club Sync applications reach you
When a role has Club Sync enabled, members whose match score clears their own
threshold are applied to it on their behalf. Those applications land in the same
pipeline as every other one, at the first stage, and are marked as Club Sync
applications so their origin is clear. You advance, hold, and decline them with
exactly the same controls and the same feedback discipline as any other
candidate.
A Club Sync candidate is a real member who has opted in to be applied on their
behalf — not a cold or scraped contact. They are presented to you with their
profile and match factors, the same evidence you would see on a direct
application.
## The Club Sync status on a job
A job carries a Club Sync status that tells you where it stands:
- **Not offered** — the default; Club Sync is not active on this role.
- **Pending** — Club Sync has been requested for the role and is awaiting review.
- **Accepted** — Club Sync is active; matched members can be applied to the role.
- **Declined** — the request was not approved.
When a role is accepted, it shows a Club Sync badge across your jobs views, so
you can tell at a glance which roles are receiving Club Sync applications.
## Handling the candidates
Treat Club Sync applications as you treat the rest of your pipeline. Review them
against the role, advance the ones that fit, and decline the ones that do not
with structured feedback. The member sees the same status and feedback they
would on any application, so a clear, prompt response serves both sides.
---
# Create and publish jobs
URL: https://docs.thequantumclub.com/partners/hiring/create-and-publish-jobs
> Create a job with the multi-step form, configure its pipeline, and control exactly when candidates see it.
**Prerequisites:** Owner, Admin, or Recruiter role.
## Create a job
### Start a new job
From your jobs view in the Partner Hub, start a new job — or choose **Create from Template** to begin from one of your company's existing roles and edit from there.
### Describe the role
Enter the title, department, seniority (junior through VP/C-suite), employment type (full-time, part-time, contract, freelance, internship), and urgency. Write the role description here too.
### Add requirements
List the requirements and the nice-to-haves separately. Keep requirements to what genuinely disqualifies — Club AI matching and your reviewers both read these literally.
### Set locations and tools
Add one or more locations, each with its own work mode (onsite, hybrid, or remote), and mark the primary one. Add the tools and technologies the role uses.
### Configure the pipeline
Choose the stages candidates move through. Your company's **Default Pipeline Configuration** is the starting template for new jobs — the standard flow is Applied, Screening, Interview, Assessment, Offer, Hired — and you can customize stages per job, including custom interview formats. You can also choose a continuous pipeline for always-on roles.
### Save or publish
Save as a draft to keep working, or publish immediately. Job creation is atomic: the role, locations, tools, and stages are committed together, so the job is never created half-configured.
You should now see the job in your jobs list — as **Draft** if you saved, or **Published** and accepting applications if you published.
## Stealth mode
For sensitive searches, a job can run in stealth mode with a named viewer list: only the people you add can see the role. Every change is recorded in a stealth audit trail — who enabled or disabled stealth mode, and who was added or removed as a viewer. For broader confidentiality controls, see [Confidential searches](/partners/administration/confidential-searches).
## Manage publishing state
| Action | Effect |
| --- | --- |
| **Publish Job** | Makes the role visible to candidates and starts accepting applications |
| **Unpublish to Draft** | Hides the role from candidates and returns it to draft |
| **Close** | Stops accepting new applications; you can reopen later |
Bulk controls let you publish, close, or archive several jobs at once from the jobs list.
You can edit a published job at any time. Changes that affect matching cause Club AI to re-evaluate the role, so keep the description current rather than working around it.
## Related
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
- [Club AI matching](/partners/intelligence/club-ai-matching)
- [Review applications](/partners/hiring/review-applications)
---
# Decline candidates well
URL: https://docs.thequantumclub.com/partners/hiring/decline-candidates-well
> Decline with structured feedback that preserves the relationship — and compounds into sharper shortlists with every decision you record.
**Prerequisites:** a candidate in your pipeline; Member role or above.
## The structured decline
### Choose decline
Open the candidate and choose decline. You enter a structured form, not a free-text box — every field exists because something downstream consumes it.
### Record who initiated
Select who initiated the decline: your company, the candidate, a mutual decision, or — distinctly — that the position closed. A position-closed decline marks the role as the thing that ended, not the candidate, preserving their standing for future re-openings.
### Select the reason
Pick the rejection reason that best matches reality. This categorization is what makes declines comparable across hundreds of decisions. (Position-closed declines skip this step.)
### Write the feedback
Feedback text is required. Provide specific reasons — "needed deeper experience operating at our data scale; strong communicator" — rather than a restated reason code. The form's own guidance applies: specifics improve matching and help the team learn.
You should now see the candidate removed from the active pipeline, with the decline source, reason, and feedback recorded on their history.
## Why feedback quality matters
Decline feedback is read three times:
- **By Club AI.** Matching learns from your declines as much as your advances. Precise feedback teaches it what to stop sending you; vague feedback teaches it nothing, and your shortlists stay generic.
- **By your team.** The next person who encounters this candidate — possibly on a different role next year — inherits your reasoning instead of re-running the same evaluation.
- **By The Quantum Club.** Decline context shapes how the platform and your Talent Strategist treat the candidate going forward, so a "not this role" stays distinct from a "not this company."
A declined candidate today is often the right candidate for a different role later.
Feedback written with that in mind keeps the door open accurately.
## One canonical path, fully audited
Every decline — whether from a partner reviewer or a platform admin, individually or in bulk — flows through one canonical decline service. Each decline writes an audit log entry and records the feedback consistently, so your audit trail shows who declined whom, when, and why, with no side doors. See [Audit log](/partners/administration/audit-log).
A decline ends the candidacy, not the relationship or the record. History, scorecards, and feedback remain attached to the candidate for your company's continuity.
## Related
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
- [Club AI matching](/partners/intelligence/club-ai-matching)
- [Audit log](/partners/administration/audit-log)
---
# How hiring works
URL: https://docs.thequantumclub.com/partners/hiring/how-hiring-works
> The shape of a hire on The Quantum Club — from an open role to a signed offer, and the feedback loop that sharpens every search after it.
The Quantum Club gives your team a full applicant-tracking pipeline: one place to publish a role, work candidates through stages, run interviews, and close an offer — every action audited, every decision feeding the next search. This page is the map; each step links to the page that goes deep.
## The lifecycle of a hire
A search moves through six phases. They run in order by default, but the board — not a calendar — is the source of truth, so candidates move at their own pace.
| Phase | What happens | Goes deep in |
| --- | --- | --- |
| Publish | Create a role and choose its pipeline stages, visibility, and screening questions | [Create and publish jobs](/partners/hiring/create-and-publish-jobs) |
| Source | Candidates arrive by direct application, Club AI matching, and your Talent Strategist's shortlist | [Club AI matching](/partners/intelligence/club-ai-matching) |
| Review | Your team reads applications, rates them internally, and shortlists | [Review applications](/partners/hiring/review-applications) |
| Advance | Move candidates stage by stage on the kanban board, recording signals at each step | [Manage your pipeline](/partners/hiring/manage-your-pipeline) |
| Interview | Schedule the loop, run it, and capture structured scorecards | [Schedule interviews](/partners/hiring/schedule-interviews) |
| Close | Extend an offer — or decline with feedback that returns to the candidate | [Make offers](/partners/hiring/make-offers) |
## The pipeline stages
Every job has a pipeline. The default stages are Applied, Screening, Interview, Assessment, Offer, and Hired, and you can add custom stages per role. The kanban board shows one column per stage and one card per candidate, so the board is always the live state of the search — there is no separate status sheet to keep in sync.
## Where candidates come from
Candidates enter a pipeline three ways: they apply directly to a published role, Club AI recommends members whose profiles match the brief, and your Talent Strategist adds people they have vetted for you. You spend your time deciding, not filtering an open job board.
## Every decision carries feedback
This is the part that compounds. When your team advances or declines a candidate, you record the signals behind the decision — skills, culture fit, communication — and optional notes. That feedback does two jobs: it gives the next reviewer context, and it teaches Club AI what excellent looks like for your roles, so future shortlists sharpen. Internal reviews stay inside your company; candidates never see them.
## Who can do what
Hiring actions are gated by company role and by per-job assignment. If a teammate cannot advance or decline on a role, their assignment does not grant it. See [Roles and permissions](/partners/get-started/roles-and-permissions).
## Where to go next
---
# Make offers
URL: https://docs.thequantumclub.com/partners/hiring/make-offers
> Take a candidate from the Offer stage to a signed acceptance — templates, approval routing, and tracking along the way.
**Prerequisites:** a candidate at the Offer stage; Recruiter role or above to create offers, Owner or Admin to approve them.
## Create the offer
### Start from the candidate
With the candidate at the Offer stage, choose **Create Offer**. Starting from the pipeline keeps the offer tied to the right job and candidate record.
### Use a template
Pick from your **Offer Templates** so compensation structure, terms, and language stay consistent across the team, then adjust the specifics — compensation, start date, and role terms — for this candidate.
### Submit for approval
If your company uses an **Approval Workflow**, the offer routes to an approver before it can go out. Approvers see the full offer in context. This is the control that prevents an off-band offer leaving the building.
### Send
Once approved, send the offer. The candidate's pipeline stage reflects it — the offer moves through sent, and later to accepted or declined.
You should now see the offer with status **Pending** in your offers dashboard and the candidate at the offer-sent stage in the pipeline.
## Track acceptance
Your offers dashboard shows every offer across roles with its current state:
| Status | Meaning |
| --- | --- |
| Pending | Sent and awaiting the candidate's decision |
| Negotiation | The candidate has come back on terms |
| Accepted | The candidate accepted — move toward Hired |
| Declined | The candidate turned the offer down |
## When an offer is declined
Record why. Offer-decline reasons — compensation, competing offer, timing, role scope — are some of the most valuable data your hiring operation produces. Patterns across declines feed your win/loss picture and tell you whether you are losing on money, speed, or story, and your compensation benchmarking gives you market context for the answer.
Handle counter-offers inside the offer record rather than in side emails. The negotiation history stays attached to the candidate, and the final accepted terms are unambiguous.
## After acceptance
Advance the candidate to Hired to close the loop. The search's full record — scorecards, stage history, the offer itself — stays intact for your audit trail and your success metrics.
## Related
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
- [Success metrics](/partners/intelligence/success-metrics)
- [Market intelligence](/partners/intelligence/market-intelligence)
---
# Manage your pipeline
URL: https://docs.thequantumclub.com/partners/hiring/manage-your-pipeline
> Run the kanban board day to day — advance, hold, and decline candidates, work in bulk, and keep the board the live truth of the search.
**Prerequisites:** a published job with candidates; Member role or above to act on candidates.
## The kanban view
Each job's pipeline is a kanban board with one column per stage. The default stages are Applied, Screening, Interview, Assessment, Offer, and Hired; your job may use custom stages. Each card is a candidate at that stage, and the board is the live state of the search — no separate status spreadsheet to maintain.
## Advance a candidate
When you advance a candidate, you record more than a column change:
### Choose advance
Open the candidate and choose to advance. Pick the target stage.
### Record signals
Rate the signals that justified the decision — skills match, culture fit, and communication — and select the highlights that stood out. These inform future matching and give the next reviewer context.
### Add notes
Notes are optional, but Club AI uses this context to learn what excellent looks like for this role. A sentence of specifics beats a blank field.
You should now see the candidate's card in the new stage, with your signals and notes attached to their timeline.
## Hold, move back, and decline
Not every decision is forward:
- **Hold** keeps a candidate parked at their stage while you wait — on a reference, a budget decision, another candidate's loop — without losing their place or context.
- **Move back** returns a candidate to an earlier stage when a step needs redoing.
- **Decline** removes a candidate from the running with structured feedback. This flow has its own discipline — see [Decline candidates well](/partners/hiring/decline-candidates-well).
## Internal review and ratings
Your team can rate and discuss candidates internally before committing to a pipeline decision. Internal reviews stay inside your company — candidates never see them — and they surface alongside the candidate so the eventual advance or decline is informed rather than impulsive.
## Bulk actions
Select multiple items to act once instead of many times — for example, publishing, closing, or archiving several jobs together, or processing a batch of new applications in one pass. Bulk actions apply the same rules as individual ones: anything that needs feedback still gets it.
## Duplicate detection
The platform flags likely duplicates when a candidate is added — for example, a profile with the same LinkedIn URL already in your pipeline. Resolve the duplicate before working the card so feedback and history accumulate on one profile, not two.
Advance and decline are role- and assignment-gated. If you cannot act on a candidate, your job assignment does not include that permission — see [Roles and permissions](/partners/get-started/roles-and-permissions).
## Related
- [Review applications](/partners/hiring/review-applications)
- [Decline candidates well](/partners/hiring/decline-candidates-well)
- [Scorecards and feedback](/partners/hiring/scorecards-and-feedback)
---
# Review applications
URL: https://docs.thequantumclub.com/partners/hiring/review-applications
> Cut incoming applications down to what matters, process them in bulk, and learn which sources earn your attention.
**Prerequisites:** at least one published job; Member role or above to act on applications.
## Filter to what matters
The applications view aggregates candidates across your roles. Narrow it before you read a single profile:
| Filter | Use it to |
| --- | --- |
| Job | Focus on one search at a time |
| Stage | See only new arrivals, or only candidates deep in process |
| Source | Compare direct applications against Club AI matches and other channels |
| Date | Catch what arrived since your last review session |
| Recruiter | See the slice of pipeline a teammate owns |
Filters combine, so "this job, Applied stage, last seven days" is one view — a repeatable morning routine rather than a scroll through everything.
## Review a candidate
Open an application to see the candidate's profile, documents, and history with your company in one place — including previous applications, internal notes, and any interview scorecards. Decisions you take here are the same advance, hold, and decline actions as the pipeline board; you are looking at the same data from a different angle.
## Process in bulk
When a role attracts volume, work in passes rather than one-at-a-time:
### Make a first pass for clear decisions
Filter to the Applied stage and triage. Select the candidates that clearly meet the bar and advance them together; select clear declines and process them together with appropriate feedback.
### Leave the maybes for a second look
Resist deciding borderline candidates inside a bulk pass. Keep them at their stage — or place them on hold — and give them individual attention later.
You should now see an Applied column that contains only undecided candidates, with advanced candidates moved forward and declines recorded with feedback.
Declines require structured feedback even in bulk. A batch decline with a thoughtless reason pollutes the signal Club AI learns from — see [Decline candidates well](/partners/hiring/decline-candidates-well).
## Source effectiveness basics
Every application carries its source. Over time, the source filter becomes a measurement tool: filter by source and compare not the volume but how far each source's candidates travel — reaching Interview and Offer is worth more than arriving in Applied. Use that to decide where to invest, and read the fuller picture in your hiring analytics.
## Related
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
- [Club AI matching](/partners/intelligence/club-ai-matching)
- [Success metrics](/partners/intelligence/success-metrics)
---
# Schedule interviews
URL: https://docs.thequantumclub.com/partners/hiring/schedule-interviews
> Schedule interviews against real availability, assign the interviewers, and know exactly what the candidate sees.
**Prerequisites:** a candidate at an interview stage; a connected calendar if you want sync (recommended).
## Connect your calendar first
Connect Google Calendar or Outlook in your calendar integration settings. With a connection in place, interviews you schedule are written to your calendar and conflicts are visible while you pick times. Without one, scheduling still works — you maintain your calendar by hand. See [Calendar integration](/partners/integrations/calendar).
## Schedule an interview
### Open the candidate and create the interview
From the candidate at their pipeline stage, create an interview. Choose the interview type that matches the stage — your job's pipeline may define custom interview formats.
### Pick the date and time
Select the date from the calendar and set the time and duration. If your calendar is connected, you choose with your real availability in view.
### Assign interviewers
Add the teammates who will conduct the interview. Interviewers need to be on your team — interviewing is most useful from people who can also submit scorecards afterwards.
### Sync and confirm
Leave calendar sync enabled so the event lands on your connected calendar, then confirm. The interview now appears against the candidate and in your team's interview views.
You should now see the interview on the candidate's timeline and, with sync enabled, the event on your connected calendar.
## What candidates see
Candidates see the interview from their side of The Quantum Club: the scheduled time, the format, and how to join. For video interviews held on the platform, the interview runs in Quantum Meetings — candidates join from their browser, and if recording is enabled they are asked for consent before it starts. See [Run interviews](/partners/meetings/run-interviews).
Candidates do not see your internal notes, scorecards, or pipeline discussion at any point.
## Rescheduling and recorded interviews
If a time stops working, update the interview rather than creating a second one — the candidate's timeline stays coherent and the synced calendar event follows. Interviews that already happened outside the platform can be entered manually so scorecards and history stay complete.
An interview without a scorecard is a hole in your hiring record. Schedule the interview, hold it, then have every interviewer submit a scorecard — see [Scorecards and feedback](/partners/hiring/scorecards-and-feedback).
## Related
- [Scorecards and feedback](/partners/hiring/scorecards-and-feedback)
- [Run interviews](/partners/meetings/run-interviews)
- [Calendar integration](/partners/integrations/calendar)
---
# Scorecards and feedback
URL: https://docs.thequantumclub.com/partners/hiring/scorecards-and-feedback
> Record interview feedback that is still worth reading months later — evidence over adjectives, calibrated across interviewers.
**Prerequisites:** a completed interview where you were an interviewer.
## Complete a scorecard
### Open the interview
After the interview, open it from the candidate's profile or your interviewer view.
### Score and substantiate
Rate the candidate against the interview's criteria, then record the specific strengths and weaknesses you observed. Write evidence, not adjectives — "walked through a migration she led, quantified the rollback plan" travels further than "strong technically."
### Submit promptly
Submit while the interview is fresh. Scorecards written days later drift toward general impressions, which is exactly what structured scoring exists to prevent.
You should now see your submitted scorecard attached to the interview on the candidate's profile, alongside any from other interviewers.
## How scorecards aggregate
The candidate's profile rolls your team's scorecards into one view: the average interview score, the number of interviews behind it, aggregated key strengths and weaknesses across interviewers, and an AI recommendation derived from the scored evidence. One enthusiastic interviewer cannot quietly outvote three lukewarm ones — the aggregate makes the spread visible.
## Calibration basics
Scores only compare if interviewers mean the same thing by them. Three habits keep your team calibrated:
- **Score independently first.** Submit your scorecard before reading anyone else's or discussing the candidate. Anchoring is the fastest way to make five scorecards worth one.
- **Anchor the scale.** Agree as a team what a 3 means versus a 4 for each criterion, with named examples. Revisit when scores cluster suspiciously.
- **Review the spread.** Your committee and calibration analytics show how interviewers score relative to each other over time. A consistently generous or harsh interviewer is a calibration conversation, not a math problem to average away.
The aggregate score is a summary, not a verdict. When scorecards disagree, the disagreement is the signal — read the written strengths and weaknesses before the hiring decision, not only the number.
## Where feedback lives
All structured feedback stays attached to the candidate within your company:
| Feedback | Where you find it |
| --- | --- |
| Interview scorecards | The candidate's profile, per interview and aggregated |
| Advance signals and notes | The candidate's timeline, recorded at each stage move |
| Decline feedback | The candidate's record and your audit trail |
Candidates never see scorecards or internal notes. Club AI does read them — your feedback trains the matching that builds your next shortlist.
## Related
- [Schedule interviews](/partners/hiring/schedule-interviews)
- [Hiring committee](/partners/intelligence/hiring-committee)
- [Decline candidates well](/partners/hiring/decline-candidates-well)
---
# Talent pool and semantic search
URL: https://docs.thequantumclub.com/partners/hiring/talent-pool-search
> Understand the vetted talent pool your Talent Strategist searches on your behalf — and how the right candidates reach your pipeline without you running the search.
The Quantum Club maintains a curated pool of vetted candidates. You do not search it directly — your Talent Strategist does, using semantic search to read a brief by meaning rather than keywords. This page explains what that means for you and where the results land.
## Who searches the pool
Searching the talent pool, running semantic candidate search, and sourcing from it are Talent Strategist tools, operated by The Quantum Club on your behalf. This keeps candidate data, consent, and outreach governed in one place. Your role is to set a clear brief and decide on the people who reach you — not to mine a database.
## What semantic search does for your brief
Semantic search matches candidates on the meaning of a role, not exact wording. A brief for a "growth-stage RevOps lead" surfaces people whose experience fits the intent, even when their title or phrasing differs. Your Talent Strategist applies it against the vetted pool, layering filters such as seniority, location, and availability, then shares a shortlist.
## Where the candidates reach you
You meet pool candidates the same way you meet every candidate — in your pipeline:
- **Your Talent Strategist** adds vetted people to a role's pipeline, with the context behind each suggestion.
- **Club AI** recommends pool members whose profiles match an open brief. See [Club AI matching](/partners/intelligence/club-ai-matching).
From there, they are cards on your board, worked exactly like any applicant. See [Manage your pipeline](/partners/hiring/manage-your-pipeline).
When you advance or decline a sourced candidate with signals and notes, that feedback teaches Club AI what excellent looks like for your roles — so the next search returns better-fitting people.
## Make searches return better people
You do not run the query, but you shape it:
- Give a precise brief — required outcomes, not just a title — so semantic matching has intent to read.
- Record decision signals on every candidate, sourced or applied.
- Raise gaps with your Talent Strategist; an underspecified brief, not a thin pool, is the usual cause of a weak shortlist.
For sensitive roles where candidate visibility must be tightly controlled, see [Confidential searches](/partners/administration/confidential-searches).
## Related
- [Club AI matching](/partners/intelligence/club-ai-matching)
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
- [Confidential searches](/partners/administration/confidential-searches)
---
# Connect your calendar
URL: https://docs.thequantumclub.com/partners/integrations/calendar
> Connect Google Calendar or Outlook so interviews land on real availability — and conflicts surface before you pick a time.
**Prerequisites:** a Google or Microsoft work account you can authorize. Calendar connections are personal — each interviewer connects their own calendar.
### Open calendar settings
Sign in at [os.thequantumclub.com](https://os.thequantumclub.com) and open your account settings, then find the calendar sync section under your connections.
### Choose your provider
Select Google Calendar and complete the Google authorization screen. Grant calendar access so The Quantum Club can read availability and create events.
Select Outlook and complete the Microsoft sign-in. Grant calendar access so The Quantum Club can read availability and create events.
### Verify the connection
After authorizing, the calendar shows as connected in your settings. Interview scheduling now reads your availability from this calendar.
You should now see your calendar listed as connected in settings, and scheduling pages should reflect your real availability.
## What syncs
- **Interview events** — interviews scheduled through The Quantum Club, including Quantum Meetings sessions, appear on your connected calendar with the meeting details.
- **Availability** — your busy times flow back into the platform, so candidates and teammates are only offered slots you can actually take.
- **Updates and cancellations** — reschedules and cancellations made in the platform update the calendar event.
## Conflict prevention
The point of the sync is that scheduling decisions are made against your live calendar, not a stale copy:
- Slots that overlap an existing event are not offered when interviews are booked.
- If you block focus time or take a day off in your calendar, the platform respects it without any extra configuration.
- For panel interviews, availability is checked for every connected interviewer, so a slot is only offered when the whole panel is free.
If an interviewer declines or moves an event directly in their calendar without updating the platform, the candidate still sees the original time. Reschedule from within The Quantum Club so both the candidate and the calendar stay in sync.
## Related
- [Schedule interviews](/partners/hiring/schedule-interviews)
- [Run interviews](/partners/meetings/run-interviews)
- [Troubleshooting](/partners/administration/troubleshooting)
---
# Greenhouse ATS sync
URL: https://docs.thequantumclub.com/partners/integrations/greenhouse
> Connect Greenhouse once and stop reconciling by hand — candidates and pipeline updates stay consistent across both systems.
**Prerequisites:** admin-level access in your partner workspace, and a Greenhouse account with permission to create API credentials.
### Open the Integrations hub
Go to the Partner Hub and select the **Integrations** tab (`https://os.thequantumclub.com/partner/hub?tab=integrations`).
### Connect Greenhouse
Find the **Greenhouse** card — described as "ATS integration for candidate syncing" — and select **Connect Greenhouse**. Provide the credentials from your Greenhouse account to authorize the link.
### Confirm the sync is running
Once connected, the card shows **Active** along with its **Sync Frequency** and **Last Synced** timestamp. Use **Sync Now** to trigger an immediate sync, and **Configure** to adjust the connection.
You should now see the Greenhouse card marked Active with a recent Last Synced time, and synced candidates appearing in both systems.
## What imports
The Greenhouse sync moves candidate data between the two systems so your team is never reconciling spreadsheets:
- **Candidates** — candidate records sync between Greenhouse and The Quantum Club, so a candidate sourced in either system is visible in both.
- **Pipeline updates** — as candidates move through stages, updates flow on the sync schedule shown on the card. The **Last Synced** time tells you how fresh the data is; **Sync Now** forces a refresh before an important review.
## How to run both systems sanely
Two ATSs without a rule about which one decides is how candidates get lost. Pick a system of record per concern:
- If Greenhouse is your organization-wide ATS, treat it as the record for compliance and reporting, and use The Quantum Club for the work — Club AI matching, committee evaluation, Quantum Meetings interviews, and member-network sourcing.
- Make stage moves in one system per role, and let the sync carry them to the other. Editing the same candidate in both systems between syncs is the main source of confusion.
If a candidate looks out of date, check **Last Synced** on the Greenhouse card before assuming data loss — the most common cause is reading one system between sync cycles. **Sync Now** resolves it.
## Related
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
- [Integrations overview](/partners/integrations/overview)
- [Webhooks](/partners/integrations/webhooks)
---
# LinkedIn job syndication and profile import
URL: https://docs.thequantumclub.com/partners/integrations/linkedin
> Syndicate your jobs out to LinkedIn and pull candidate profiles in — one pipeline, more reach, no retyping.
**Prerequisites:** admin-level access in your partner workspace for the connection itself; any team member can use import once connected.
### Connect LinkedIn
Open the Partner Hub **Integrations** tab (`https://os.thequantumclub.com/partner/hub?tab=integrations`), find the **LinkedIn** card, and complete the connection.
### Syndicate a job
With LinkedIn connected, jobs you publish in The Quantum Club can be syndicated to LinkedIn so they reach candidates there as well as in the member network. Candidates who respond flow into the same pipeline as every other applicant — one pipeline, multiple sources.
### Import candidate profiles
When you add a candidate who exists on LinkedIn, use the LinkedIn import to pull their public profile data — role history, skills, and links — instead of retyping it. Imported profiles land in your pipeline like any manually added candidate, and Club AI scores them against your role the same way.
You should now see the LinkedIn card marked Active in the Integrations hub, your syndicated job visible on LinkedIn, and imported profiles appearing in your pipeline.
## How the two halves fit together
- **Syndication widens the top of your funnel.** Use it for roles where the member network alone is not producing enough volume, and watch source effectiveness in your analytics to confirm LinkedIn applicants actually convert.
- **Import deepens individual records.** It saves data entry and gives Club AI more signal to score with — but an imported profile is a starting point, not a vetted candidate. Review imported data for accuracy before you rely on it.
Imported profile data is personal data. Only import profiles of candidates you are genuinely considering for a role, and rely on your pipeline as the system of record rather than keeping copies elsewhere.
## Related
- [Create and publish jobs](/partners/hiring/create-and-publish-jobs)
- [Review applications](/partners/hiring/review-applications)
- [Club AI matching](/partners/intelligence/club-ai-matching)
---
# Integrations overview
URL: https://docs.thequantumclub.com/partners/integrations/overview
> Map every integration available to your team — calendars, messaging, LinkedIn, Greenhouse, identity, and webhooks — and pick what to connect first.
## The Integrations hub
Most integrations are managed from the Partner Hub: open the **Integrations** tab in the Operations group (also reachable at `https://os.thequantumclub.com/partner/hub?tab=integrations`). Each integration appears as a card with a **Connect** button, and once connected shows its **Status** (Active or Inactive), **Sync Frequency**, and **Last Synced** time, plus **Sync Now** and **Configure** actions.
Calendar connections and webhooks are personal or developer-level, so they live in account settings and the API section rather than the hub.
## Available integrations
## Choosing what to connect first
- **Calendar** has the highest immediate payoff: it removes scheduling back-and-forth and prevents double-booked interviews.
- **Slack or Microsoft Teams** keeps the team responsive without anyone living in a dashboard — response time is an SLA, and notifications are how you meet it.
- **Greenhouse** matters when your organization already runs its system of record there; connect it before migrating any process.
- **SCIM and SSO** are for IT teams managing access at scale — set them up once, then onboarding and offboarding follow your identity provider automatically.
- **Webhooks** are for engineering teams building custom automation on top of hiring events.
The Integrations hub also lists additional ATS and HRIS connectors — Lever, Workday, and SuccessFactors — alongside the integrations documented here. The connection flow (Connect, then Configure and Sync Now) works the same way for each.
## Who can manage integrations
Connecting company-wide integrations requires admin-level access in your partner workspace; personal calendar connections are available to every team member. See [roles and permissions](/partners/get-started/roles-and-permissions) for the full matrix.
## Related
- [Set up your team](/partners/get-started/set-up-your-team)
- [SCIM provisioning reference](/platform/identity/scim)
- [Webhooks API reference](/api/webhooks)
---
# SCIM and SSO for partner teams
URL: https://docs.thequantumclub.com/partners/integrations/scim-and-sso
> Give your team enterprise sign-in and directory-driven provisioning — and know exactly where IT goes to set it up.
## What you get
- **SSO (single sign-on)** — your team signs in to The Quantum Club with your company identity provider instead of separate passwords. Access policies you already enforce — MFA, device rules, session length — apply automatically.
- **SCIM 2.0 provisioning** — your identity provider creates, updates, and deactivates user accounts automatically. New hires get access on day one without an invite; leavers lose access the moment IT deactivates them, which is the part security teams care about most.
Supported identity providers for SCIM provisioning: **Okta**, **Microsoft Entra ID**, **OneLogin**, and **Google Workspace**.
## Why teams turn this on
- **Offboarding is enforced, not remembered.** Deactivation in your directory deactivates platform access — no orphaned accounts holding candidate data.
- **Group-based access.** Map directory groups to platform access so team membership follows your org structure.
- **Audit-ready.** Provisioning actions are logged, which pairs with the partner [audit log](/partners/administration/audit-log) for compliance reviews.
## Where to set it up
Setup is an IT-level task documented in the Platform section, including identity-provider-specific walkthroughs, token handling, and the supported SCIM filter syntax:
Set up SSO first, then layer SCIM provisioning on top. SSO controls how people sign in; SCIM controls which accounts exist. Most identity providers configure both from the same application entry.
## Related
- [Set up your team](/partners/get-started/set-up-your-team)
- [Roles and permissions](/partners/get-started/roles-and-permissions)
- [Audit log](/partners/administration/audit-log)
---
# Connect Slack and Microsoft Teams
URL: https://docs.thequantumclub.com/partners/integrations/slack-and-teams
> Put hiring activity in the channels your team already watches — Slack or Microsoft Teams, connected in a few steps.
**Prerequisites:** admin-level access in your partner workspace, and permission to install apps in your Slack workspace or Teams tenant (your IT team may need to approve this).
### Open the Integrations hub
Go to the Partner Hub and select the **Integrations** tab (`https://os.thequantumclub.com/partner/hub?tab=integrations`).
### Connect your messaging platform
Find the **Slack** card — described as "Real-time notifications and updates" — and select **Connect Slack**. Complete the authorization in your Slack workspace.
Find the **Microsoft Teams** card — described as "Collaboration and notifications" — and select **Connect Microsoft Teams**. Complete the authorization in your Microsoft tenant.
### Configure and verify
Once connected, the card shows **Active** with its sync details. Use **Configure** to adjust the connection, and confirm a test notification arrives where you expect it.
You should now see the Slack or Microsoft Teams card marked Active in the Integrations hub, and hiring notifications arriving in your workspace.
## Which notifications arrive where
Connected messaging platforms receive the hiring activity your team needs to act on quickly — new candidates entering the pipeline, stage changes, and team activity updates. In-app and email notifications continue to work alongside the messaging integration; the channel notification is the fast path, not a replacement for the candidate record.
A practical setup that works for most teams:
- **A shared hiring channel** for pipeline activity, so anyone can pick up an unowned candidate.
- **Direct alerts for owners** — the person responsible for first response acts on notifications immediately; response time is tracked on your SLA dashboard.
Hiring notifications can include candidate names and role details. Route them to private channels limited to your hiring team, not to company-wide channels.
## Related
- [SLA dashboard](/partners/intelligence/sla-dashboard)
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
- [Troubleshooting](/partners/administration/troubleshooting)
---
# Webhooks for partner teams
URL: https://docs.thequantumclub.com/partners/integrations/webhooks
> Push hiring events to systems you control the moment they happen — dashboards, automation, warehouse feeds — with the full reference one link away.
## What webhooks enable
Webhooks push hiring events from The Quantum Club to an HTTPS endpoint you control, as they happen. Instead of polling for changes or copying data by hand, your systems react to events in near real time.
Typical things partner teams build on webhooks:
- **Internal dashboards** — mirror pipeline activity into your own BI tooling alongside business data the platform never sees.
- **Workflow automation** — trigger downstream processes when a candidate reaches a stage, for example opening an onboarding ticket when an offer is accepted.
- **Data warehouse feeds** — append hiring events to your warehouse for long-horizon analysis.
- **Custom notifications** — route events to systems beyond the built-in Slack and Microsoft Teams integrations.
## Webhooks compared with the alternatives
- Use the **Slack and Teams integrations** when humans need to see activity — no code required.
- Use the **Greenhouse sync** when the goal is keeping two ATSs aligned.
- Use **webhooks** when software needs to react to events — they are the integration primitive the others are built from conceptually, and the right tool when nothing off the shelf fits.
## Where to go next
Webhook configuration, event types, payload schemas, signature verification, and retry behavior are documented in the API section:
Webhook payloads can contain personal data about candidates. Receive them over HTTPS only, verify signatures, and apply the same retention and access rules you apply to candidate data anywhere else in your stack.
## Related
- [Integrations overview](/partners/integrations/overview)
- [Slack and Microsoft Teams](/partners/integrations/slack-and-teams)
- [Audit log](/partners/administration/audit-log)
---
# Generate an Executive Briefing Deck
URL: https://docs.thequantumclub.com/partners/intelligence/briefing-decks
> Assemble a board-ready hiring intelligence report, choose exactly which sections it carries, and export the PDF before the meeting.
**Prerequisites:** your account is linked to a company profile, and you have access to the Partner Hub Intelligence tabs. If you see "No company linked", finish company setup first.
### Open the Briefing Deck
In the Partner Hub at [os.thequantumclub.com](https://os.thequantumclub.com), switch to the **Intelligence** group and select **Briefing Deck**. The page is titled **Executive Briefing Deck** and describes itself as a board-ready hiring intelligence report.
### Choose the sections to include
The left panel, **Include Sections**, lists the available sections:
- **Hiring Progress** — pipeline overview with total applications, hires, and active jobs
- **Time & Cost Metrics**
- **Pipeline Health**
- **Benchmarks** — anonymized averages across The Quantum Club partner network
- **Quarterly Trends**
- **Open Roles Summary**
Tick the sections you want, or use **Select All** / **Deselect All**. The preview pane updates as you select; sections without data yet show a note such as "No quarterly trend data available yet."
### Review the preview
Check the right-hand preview before exporting. This is exactly what your stakeholders will see, titled **Executive Hiring Briefing**. If a section looks thin, deselect it — a shorter, sharper deck lands better in a board meeting.
### Generate the PDF
Select **Generate PDF**. The deck downloads as `executive-briefing-YYYY-MM-DD.pdf` and a confirmation appears: "Briefing PDF generated." If you have no sections selected, the export is blocked with "No sections selected" — pick at least one and retry.
### Share with decision-makers
Send the PDF to your leadership or hiring committee, or attach it to your next review meeting. Because the export is a static snapshot, regenerate it before each meeting so the numbers reflect the current pipeline.
You should now see the downloaded PDF in your browser's downloads, dated today and containing each section you selected.
The Benchmarks section compares your hiring performance against anonymized averages across The Quantum Club partner network. No individual company is identifiable in the comparison data.
## Related
- [Success Metrics dashboard](/partners/intelligence/success-metrics)
- [Hiring Committee](/partners/intelligence/hiring-committee)
- [Market intelligence](/partners/intelligence/market-intelligence)
---
# Understanding Club AI matching
URL: https://docs.thequantumclub.com/partners/intelligence/club-ai-matching
> Read Club AI match scores with confidence — what each signal means, how skill gaps are surfaced, and where human judgment takes over.
## What Club AI matching does
When a candidate enters your pipeline, Club AI compares their profile against the role you published — the requirements, nice-to-haves, seniority, location, and salary range you set in the job. The result is a match score that appears on candidate cards, in your pipeline views, and in talent recommendations, so you can prioritize review time where it matters most.
Scores inform decisions — they do not make them. A match score is a starting point for human judgment, not a verdict. The Quantum Club expects your team to review the underlying evidence — skills, experience, and interview signal — before advancing or declining anyone. Use scores to order your queue, not to filter people out automatically.
## Signal scoring
Club AI breaks fit into named signals rather than a single opaque number. Each signal is rated on an anchored scale so two reviewers reading the same candidate see the same vocabulary:
- **Skills match** — rated from "Off brief" through "Partial" and "Solid" to "Strong" and "Exceptional".
- **Culture alignment** — how well the candidate's background and stated preferences align with your company culture statement.
Signals that lack evidence show as "Not rated yet" or "Partial signal" instead of guessing. Treat an unrated signal as a question to answer in interviews, not a negative mark.
## Skill match and gaps
The skills analysis goes beyond keyword overlap:
- **Matched skills** — requirements from your job description that the candidate demonstrably covers.
- **Skill gaps** — required skills with no supporting evidence in the profile. Gaps are listed explicitly so you can probe them in a screening call rather than assume the worst.
A candidate with one coachable gap and strong adjacent experience often outperforms a perfect keyword match.
The gap list exists to focus your interview, not to disqualify.
## Experience, location, and salary alignment
Three practical checks round out the score:
- **Experience** — seniority and years of relevant experience against the level you set for the role.
- **Location** — whether the candidate's location or remote preference fits the role's location setup. Mismatches are flagged (for example, "Location not aligned with role requirements") rather than silently lowering the score.
- **Salary** — whether the candidate's expectations sit inside the salary range you published. An out-of-range flag early saves a withdrawn offer later.
## How to work with scores
- **Sort, then read.** Use the score to order your review queue, then open the top profiles and read the signal breakdown.
- **Probe the gaps.** Bring listed skill gaps into your interview plan and scorecards.
- **Disagree openly.** If your team consistently rates a candidate differently from Club AI, record it in your scorecards — structured human feedback is the strongest signal you have.
- **Escalate strong matches.** High-scoring candidates move fastest when you respond quickly; your response time is tracked on the SLA dashboard.
## Related
- [Review applications](/partners/hiring/review-applications)
- [Scorecards and feedback](/partners/hiring/scorecards-and-feedback)
- [Success Metrics dashboard](/partners/intelligence/success-metrics)
---
# Run a Hiring Committee session
URL: https://docs.thequantumclub.com/partners/intelligence/hiring-committee
> Evaluate a candidate as a committee — live voting, consensus scoring, and a decision trail you can defend later.
**Prerequisites:** your account is associated with a company, and the candidate you want to evaluate has reached the committee review stage of your pipeline.
## How committee sessions work
The Hiring Committee lives in the Partner Hub under the **Intelligence** group, in the **Committee** tab. Voting sessions are created when a candidate reaches the committee review stage, and the portal splits them into **Active Sessions** (voting in progress) and **Past Sessions** (completed). Each session is named for the candidate and the job title, so a committee member can find their assignment at a glance.
### Open an active session
From the sessions list, select a card under **Active Sessions**. Cards show the candidate name, job title, and a status badge — **Active** while voting is in progress, **Completed** once the session ends.
### Review the aggregated scorecards
Inside the session you see the aggregated scorecard view for the candidate's application: every committee member's structured feedback rolled into one comparison, so the group debates the same evidence rather than separate impressions.
### Cast votes in the live voting panel
Each member records their evaluation in the live voting panel. Votes are tied to the application, so the consensus picture builds in real time as members submit. The committee roster panel shows who is on the committee and who has voted.
### End the session
When the committee has reached a decision, the session owner selects **End Session**. The session moves to **Past Sessions** with the status "Session completed", and the outcome feeds back into your pipeline.
You should now see the session under Past Sessions with a Completed badge, and the consensus outcome recorded against the candidate's application.
## Consensus scoring and calibration
Beyond individual sessions, the Committee tab gives you calibration analytics across reviewers: the **Team Average Score**, the total number of scorecards submitted, and **Calibration Alerts** that flag high-variance reviewers — people whose scores consistently diverge from the group. Use these alerts as a coaching prompt, not a penalty; a high-variance reviewer may be seeing something the group misses, or may need a refresher on your scoring anchors.
## Audit trail
Every committee decision is captured in a decision audit trail: who evaluated, how they scored, and when the session concluded. This protects your team in two directions — it documents that decisions followed a structured process, and it lets you revisit the reasoning months later when you review hiring quality.
If you see "No active voting sessions", no candidate has reached the committee review stage yet. Sessions appear automatically as candidates advance through your pipeline.
## Related
- [Scorecards and feedback](/partners/hiring/scorecards-and-feedback)
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
- [Audit log](/partners/administration/audit-log)
---
# Market intelligence
URL: https://docs.thequantumclub.com/partners/intelligence/market-intelligence
> Turn salary benchmarks, time-to-fill comparisons, and competitor signals into hiring decisions instead of dashboard reading.
## Where market intelligence lives
Market signals are spread across the Partner Hub rather than locked in one report:
- **Your Hiring Metrics** — a dashboard widget summarizing your own market position: average salary range across your open roles, average candidates per role with a demand-trend badge, average time to fill compared against an estimated market average, and your count of active roles.
- **Network** — anonymized benchmarks and industry trend comparisons across The Quantum Club partner network, including companies with a hiring profile like yours.
- **Alerts** — market alerts that surface notable shifts so you do not have to watch dashboards daily.
- **Brand** — competitor brand comparison for how your employer presence stacks up against companies you compete with for talent.
## Salary benchmarks
Salary benchmarks show how your published ranges compare with the market and the partner network. Compensation benchmarking also appears at offer time, so you can sanity-check a package before it goes out.
How to act on them:
- If your range sits below benchmark and roles attract few candidates, raise the range or strengthen the non-salary story in your company profile.
- If you are above benchmark but losing offers, the problem is rarely money — look at response speed and process length first.
## Time-to-fill benchmarks
Your average time to fill is shown against an estimated market average — for example, "+6d vs est. avg" means your roles take six days longer than comparable roles. Time to fill is the benchmark most within your control:
- A slow first stage usually means review bottlenecks — check who owns first response and watch the SLA dashboard.
- A slow late stage usually means scheduling friction — calendar integration and instant meetings remove most of it.
## Competitor hiring signals
Competitor signals tell you who you are competing against for the same talent:
- **Target companies** — track the companies you most often hire from or lose candidates to.
- **Competitor brand comparison** — see how your employer brand compares with named competitors.
- **Demand trend** — the candidates-per-role badge tells you whether demand for your roles is rising or cooling.
How to act on them: when a competitor ramps hiring in your space, expect candidates to hold multiple offers — shorten your process and make offers faster. When demand cools, you can afford a higher bar.
Network benchmarks are anonymized averages across The Quantum Club partner network. You see how you compare with the market; you never see another company's individual data, and they never see yours.
## Related
- [Success Metrics dashboard](/partners/intelligence/success-metrics)
- [SLA dashboard](/partners/intelligence/sla-dashboard)
- [Make offers](/partners/hiring/make-offers)
---
# SLA dashboard
URL: https://docs.thequantumclub.com/partners/intelligence/sla-dashboard
> Read the SLAs tracked on your account at a glance — and know what to do when one drifts from green toward red.
## Where to find it
Open the Partner Hub and select the **SLA** tab in the Operations group. The dashboard shows each SLA against its target, plus **Recent SLA Performance** covering the last 30 days of tracking.
## The SLAs tracked
| SLA | What it measures |
| --- | --- |
| **Response Time** | Time to first response on new candidates and requests |
| **Shortlist Delivery** | How quickly a candidate shortlist is delivered |
| **Interview Scheduling** | Time from request to a scheduled interview |
| **Replacement Guarantee** | The window for replacing a candidate when a placement does not work out |
Each SLA shows its **Target** alongside actual performance, so you always know the distance between the two.
## Reading the status colors
- **Green** — performance is meeting the target. When everything is on track you see the **All SLAs Met** badge.
- **Yellow (amber)** — performance is slipping toward the target boundary. Nothing is breached yet, but the trend needs attention this week, not this quarter.
- **Red** — performance is below target. The dashboard flags this with "Below target compliance. Review processes to improve performance."
## When an SLA goes yellow
Treat yellow as an early warning with time to act:
- **Response Time slipping** — check who owns first review of new candidates; the most common cause is an unowned inbox after a team change. Confirm assignments in your team setup.
- **Interview Scheduling slipping** — scheduling friction is usually calendar friction. Make sure interviewers have calendar sync connected, and use instant meetings for short-notice conversations.
- **Shortlist Delivery slipping** — raise it with your Talent Strategist; the cause is often an underspecified brief rather than a slow pipeline.
## When an SLA goes red
A red SLA means candidates are already feeling the delay, and candidate experience decays fast:
1. Identify the stuck items — open your pipeline and sort by time in stage to find the candidates waiting longest.
2. Clear the backlog before fixing the process — respond to the waiting candidates first.
3. Fix the structural cause — reassign ownership, adjust stage automation, or rebalance interviewer load.
4. Watch **Recent SLA Performance** over the following 30 days to confirm the fix held.
"No SLA metrics recorded yet" means tracking has not accumulated data for your account — typically because activity is new. Metrics appear as your hiring activity generates measurable events.
## Related
- [Manage your pipeline](/partners/hiring/manage-your-pipeline)
- [Schedule interviews](/partners/hiring/schedule-interviews)
- [Calendar integration](/partners/integrations/calendar)
---
# Success Metrics dashboard
URL: https://docs.thequantumclub.com/partners/intelligence/success-metrics
> Measure whether your hiring actually works — funnel and conversion before the hire, quality and retention after it.
The metrics split across two surfaces in the Partner Hub: the **Analytics** view (funnel and conversion) and the **Success Metrics Dashboard** (outcomes after the hire).
## Funnel and pipeline metrics (Analytics)
The **Analytics** tab covers everything up to the hire:
- **Hiring funnel** — applications through shortlist, interview, offer, and hire, with conversion between stages. A healthy funnel narrows gradually; a cliff at one stage points at a process problem in that stage, not the candidates.
- **Pipeline health** — how candidates are distributed across stages and where they are aging.
- **Time to hire** — how long candidates spend from application to acceptance.
- **Source effectiveness** — which channels produce candidates who actually get hired, so you invest where hires come from rather than where applications come from.
- **Offer acceptance** — the share of offers candidates accept. Falling acceptance usually signals slow processes or off-market packages before anything else.
- **Diversity view** — pipeline composition so you can spot where diverse candidates drop out, stage by stage.
## Outcome metrics (Success Metrics Dashboard)
The **Success** tab opens the **Success Metrics Dashboard**, which measures what happens after you hire:
| Metric | What it tells you |
| --- | --- |
| **Total Hires** | Placements made through the platform |
| **Avg Time to Hire** | Average days from application to hire |
| **90-Day Retention** | Percentage of hires still employed after 90 days |
| **Quality Score** | Composite quality of hire, out of 100 |
### Quality of hire composite
The Quality Score is a weighted composite of three factors:
- **90-Day Retention** — 40% weight
- **Time-to-Productivity** — 30% weight
- **Hiring Manager Satisfaction** — 30% weight
A single number hides less here than usual because the three factors correct each other: fast-to-productive hires who leave at month two drag retention; long-tenured hires who never ramp drag productivity.
### ROI per placement
The ROI panel relates your total placement fees to the value of the hires they produced over the last six months — total fees, average cost per hire, and a return multiple ("every $1 spent returns $X in hire value"). Use it to defend hiring budget with evidence rather than instinct.
### 90-Day Retention tracker
The retention tracker shows your retention rate against target with a trend direction (Improving or Declining) and a plain-language rating (Excellent, Good, or Needs attention). Retention below target is the single strongest signal that something upstream — scoping, assessment, or onboarding — needs work.
If you see "No success data yet", you have not made placements through the platform yet. Metrics populate automatically once you start hiring.
## Related
- [Market intelligence](/partners/intelligence/market-intelligence)
- [Briefing decks](/partners/intelligence/briefing-decks)
- [SLA dashboard](/partners/intelligence/sla-dashboard)
---
# Candidate signals
URL: https://docs.thequantumclub.com/partners/meetings/candidate-signals
> Read the conversation evidence a meeting produces — grounded in what the candidate actually said, never a personality read.
**Prerequisites:** a recorded, transcribed interview in Club Meet. Signals exist only where consent allowed recording.
## What candidate signals are
When an interview is recorded and transcribed, the transcript is analyzed to surface the substance of the conversation. The result is a set of signals you can use as input to a hiring decision:
- a **summary** of the conversation and its key moments,
- **skill observations** with quoted evidence — the specific phrase in the transcript that supports each observation,
- **action items** and follow-up points raised in the call,
- an overall read on **engagement** and the tone of the exchange.
These are drawn from the meeting itself. They describe what happened in the conversation, not who the candidate is as a person.
## Conversation evidence, not a personality read
This distinction is the whole point, and the product holds the line on it deliberately.
Signals report observed work-sample behavior only. They are not a clinical, psychological, or personality diagnosis.
A signal points back to evidence: a skill observation quotes the moment in the transcript that prompted it, so you can check the source rather than trust a label. The analysis scores what was demonstrated in the conversation — clarity, relevant experience, how a problem was reasoned through — and stops there. It does not infer personality traits, and it does not produce a psychometric or clinical profile.
A signal is a pointer to something the candidate said, not a score that decides the outcome. Open the quoted evidence, judge it in context, and weigh it alongside your structured scorecard. The scorecard remains the record your decision stands on.
## How to use them
### Start from the summary
Read the conversation summary the same day, while the interview is fresh. It gets a teammate who was not in the room up to speed in minutes.
### Check the evidence behind each observation
For any skill observation that matters to the decision, open the quoted transcript moment. Confirm the observation reflects what was actually said, in the context it was said.
### Feed your scorecard, not replace it
Use signals as structured input — they surface exchanges you might have missed — but record your judgment on the scorecard. Signals inform; they do not decide.
## What signals are not
- They are not a personality test. Club Meet does not turn a conversation into a personality, psychological, or clinical assessment.
- They are not a substitute for human judgment. A quoted observation still needs a person to weigh it against the role.
- They do not exist without consent. No recording means no transcript, which means no signals.
## Related
- [Meeting Intelligence](/partners/meetings/meeting-intelligence)
- [Recordings and transcripts](/partners/meetings/recordings-and-transcripts)
- [Share a dossier](/partners/meetings/share-a-dossier)
---
# External recordings
URL: https://docs.thequantumclub.com/partners/meetings/external-recordings
> Bring meetings held outside Club Meet into the same intelligence layer — through a notetaker bot or a synced recording tool.
**Prerequisites:** a partner account, and a connected calendar or recording tool depending on the path you use.
## Why this exists
Not every conversation happens in Club Meet. A first call lands on the client's Google Meet; a candidate prefers a tool their team already uses. External recordings close that gap: a meeting held elsewhere can still flow into Meeting Intelligence, so its transcript, summary, and action items sit alongside the meetings you ran natively.
There are two ways in: a **notetaker bot** that joins a live external call, and **sync** from a recording tool you already run.
## The notetaker bot
When a notetaker is enabled for a meeting, a bot joins the external call as a participant and captures it on your behalf. The bot's job is to attend, record, and produce a transcript that flows back into the platform — so a Google Meet booking ends with the same searchable transcript a native meeting would.
The bot's status is tracked end to end: you can see when it is joining, when it is in the call, and when its recording and transcription are ready. If a meeting never starts within the join window, the session is marked accordingly rather than left hanging.
A notetaker joins the call as an attendee everyone can see. Treat its presence as you would any recording: make sure participants know the meeting is being captured before you rely on the transcript, in line with the same consent expectations that govern native recordings.
## Sync from a recording tool
If your team already records with a dedicated meeting tool, you can sync those recordings in rather than re-recording. The platform pulls completed meetings from the connected tool — the transcript, the summary, and the action items — and files them as external recordings against your record.
Supported sync sources include **Fathom** and **Fireflies**, and live external calls can be captured through **Recall**. Once synced, an external recording behaves like any other: its transcript is searchable, and its summary and action items are available the same way a native meeting's are.
### Connect the source
Connect the recording tool or calendar the external meetings run on, so the platform can reach the completed recordings or join the live call.
### Run the meeting where it happens
Hold the conversation on the external platform as you normally would. The notetaker joins, or the recording tool captures it.
### Find it in the platform
After the call, the external recording's transcript and summary appear against your record, ready to search and act on alongside native meetings.
A meeting you held outside Club Meet now has its transcript and summary in the platform, searchable next to your native meetings.
## What stays the same
An external recording feeds the same Meeting Intelligence layer as a native one — the transcript is searchable, and the conversation evidence is grounded in what was said. The consent expectations are the same too: capture a conversation only when participants know it is being recorded.
## Related
- [Meeting Intelligence](/partners/meetings/meeting-intelligence)
- [Recordings and transcripts](/partners/meetings/recordings-and-transcripts)
- [Candidate signals](/partners/meetings/candidate-signals)
---
# Host controls
URL: https://docs.thequantumclub.com/partners/meetings/host-controls
> Control who gets into your meeting and what happens inside it — approval, room lock, and recording all sit with the host.
**Prerequisites:** a meeting you host in Club Meet.
## What the host controls
A host has authority over the room that a participant does not. The controls fall into two groups: who gets in, and what happens once they are in.
## Controlling who gets in
### Require approval
Turn on **Require Approval** and guests do not enter directly — they land in a waiting state and request to join. You see each pending request as it arrives and admit people one at a time, so no one reaches the room until you let them.
A signed-in member you expect can be admitted in a tap; an unrecognized name is a prompt to check before you open the door.
### Lock the room
Locking a meeting closes it to new entrants. Once a room is locked, people who are not already in — and are not the host — cannot join, even with a valid link. Use it to seal a conversation once everyone expected has arrived.
Approval screens people as they arrive; a lock shuts the door entirely. Use approval when you are still expecting people, and lock once the room is complete.
## Controlling what happens inside
- **Recording.** Recording is host-only. Participants cannot start or stop it; only the host decides whether a meeting is recorded, and recording stays consent-gated. See [Recordings and transcripts](/partners/meetings/recordings-and-transcripts).
- **The participant list.** The host sees who is in the room and manages the roster from the participants view.
- **Notetaker.** The host decides whether a notetaker captures the meeting, including for calls that run on external platforms. See [External recordings](/partners/meetings/external-recordings).
You should be able to admit guests on approval, lock the room when everyone has arrived, and start a consent-gated recording — all as host.
## Hosting an instant meeting
Instant Quick Meetings are approval-free by design: anyone with the link joins directly, without waiting to be admitted. That is the point of an instant meeting — speed over gatekeeping. If you need approval or a lock for a conversation, run it as a scheduled meeting rather than a Quick Meeting. See [Instant meetings](/partners/meetings/instant-meetings).
## Related
- [Recordings and transcripts](/partners/meetings/recordings-and-transcripts)
- [External recordings](/partners/meetings/external-recordings)
- [Instant meetings](/partners/meetings/instant-meetings)
---
# Instant meetings
URL: https://docs.thequantumclub.com/partners/meetings/instant-meetings
> Spin up a Quick Meeting in seconds and get anyone into the room with a single link — your guests need nothing, not even an account.
**Prerequisites:** a partner account on The Quantum Club. Your guests need nothing.
## When to use an instant meeting
Scheduled interviews carry process — calendar sync, interviewer assignment, scorecards. An instant meeting is for everything that should not wait for process: a screening call that came together in chat, a debrief right after an interview loop, or a quick conversation with a candidate's referee.
## Create a Quick Meeting
### Create the instant meeting
From Quantum Meetings, choose **Create instant meeting** and select **Quick Meeting (1 hour)**. The room exists immediately — no scheduling step, no calendar required.
### Share the link
Use **Copy Link** and send it through whatever channel you are already in — email, chat, or a text message. A QR code is available too, so someone next to you can scan to join instantly from their phone.
### Meet
Open the link yourself to enter the room. Quick Meetings are approval-free: participants who open the link join directly, without waiting for the host to admit them.
You should now be in the meeting room, and anyone opening your link should land in the same room within seconds.
## Guests join without an account
The share link is the entire barrier to entry. Guests join without a Quantum Club account — they open the link in a browser, enter a name (and optionally an email) so the room knows who they are, and they are in. There is no download, no signup, and no app.
This is what makes instant meetings work for people outside the platform: references, external advisors, or a candidate you have not formally added to a pipeline yet.
Anyone with the link can join an approval-free Quick Meeting while it is active. Share it only with the people you intend to meet, and create a fresh meeting per conversation rather than reusing one link.
## What instant meetings share with scheduled ones
Quick Meetings run on the same Quantum Meetings infrastructure as your scheduled interviews — the same in-browser room, controls, and quality. Recording remains host-controlled and consent-gated when you use it. For the full interview workflow with calendar sync and scorecards, schedule instead — see [Run interviews](/partners/meetings/run-interviews).
## Related
- [Run interviews](/partners/meetings/run-interviews)
- [Schedule interviews](/partners/hiring/schedule-interviews)
- [Calendar integration](/partners/integrations/calendar)
---
# Meeting Intelligence
URL: https://docs.thequantumclub.com/partners/meetings/meeting-intelligence
> Every meeting becomes a recorded, transcribed, analyzed asset — the conversation works for you long after the call ends.
Club Meet is shown in-app as Quantum Meetings. The intelligence layer described here appears in the product as Meeting Intelligence.
## What Meeting Intelligence is
A conferencing tool ends when the call ends. Club Meet does not. Every meeting you run flows through a pipeline that turns a live conversation into a durable, searchable asset: the call is **recorded**, the audio is **transcribed**, the transcript is **analyzed**, and the result is assembled into a structured **dossier** you can review, search, and share.
The room itself runs on LiveKit and opens in the browser — no installation for you or your guests. What sets it apart is not the video. It is what happens to the conversation afterward.
## The pipeline
### Recorded
With consent acknowledged in the room, the host records the meeting to the cloud. Recording is server-side, so it does not depend on anyone's local machine staying connected. See [Recordings and transcripts](/partners/meetings/recordings-and-transcripts).
### Transcribed
When the recording is ready, the audio is transcribed automatically into a written, timestamped record of who said what. The transcript makes the meeting searchable — you find the exact exchange by searching text instead of scrubbing video.
### Analyzed
The transcript is analyzed to surface the substance: a summary of the conversation, the key moments, action items, and — for interviews — skill observations with quoted evidence from what the candidate actually said. This is conversation evidence, not a personality read. See [Candidate signals](/partners/meetings/candidate-signals).
### Assembled
The outputs attach to the meeting and feed the candidate's record, so a teammate who was not in the room gets the substance in minutes rather than re-watching an hour of video.
One meeting now produces a recording, a searchable transcript, and an analyzed summary — all attached to the meeting and ready to act on.
## Why it beats a generic conferencing tool
A standard video call leaves you with, at best, a recording file someone has to watch. Club Meet closes the gap between the conversation and the decision:
- **Nothing is lost.** The transcript captures exact phrasing — the priorities an interviewer described, the commitment a candidate made — instead of relying on memory and notes.
- **Review scales.** A panel of five reads one summary; nobody has to rewatch the call to catch up.
- **Evidence is grounded.** Interview analysis quotes the transcript, so observations point back to something the candidate said rather than an impression.
- **It works beyond the room.** Meetings held on other platforms can be pulled into the same intelligence layer through a notetaker and external sync. See [External recordings](/partners/meetings/external-recordings).
## Consent comes first
The pipeline only ever processes what consent allowed. Recording is host-controlled and consent-gated: it cannot start until participants have acknowledged it in the room, and a persistent banner shows while it runs. If a participant declines, run the meeting unrecorded — the conversation still happens, it just does not feed the pipeline. The precise mechanics live in [Recordings and transcripts](/partners/meetings/recordings-and-transcripts).
## Related
- [Recordings and transcripts](/partners/meetings/recordings-and-transcripts)
- [Candidate signals](/partners/meetings/candidate-signals)
- [Share a dossier](/partners/meetings/share-a-dossier)
- [External recordings](/partners/meetings/external-recordings)
---
# Recordings and transcripts
URL: https://docs.thequantumclub.com/partners/meetings/recordings-and-transcripts
> Record a meeting to the cloud with consent enforced, then get a searchable transcript when processing finishes.
**Prerequisites:** a partner account, and a meeting you host in Club Meet.
## How recording works
Recording is server-side cloud recording. When the host starts it, the meeting is captured in the cloud rather than on anyone's laptop, so the recording survives a host dropping off and does not depend on local disk or connection. The host chooses the layout the recording captures — for example a grid of participants or a speaker-focused view.
Recording is host-only. Participants cannot start or stop it; only the host controls whether a meeting is recorded at all.
## Consent is enforced, not advisory
Consent is built into the act of recording — the host cannot quietly bypass it.
Recording cannot begin until consent is acknowledged in the room. The control is gated, not a checkbox someone can ignore.
In practice:
- When the host moves to record, participants are shown a **Recording Consent Required** prompt that states the purpose and whether their video feed is included. Recording does not start until that consent is acknowledged.
- While recording runs, every participant sees a persistent banner confirming the meeting is being recorded and that participants have agreed to it. There is no hidden recording state.
- Each consent acknowledgement is captured as a consent receipt — a dated record of who agreed, to what, and when — so the agreement is auditable after the fact.
If a participant does not consent, do not record. Run the meeting unrecorded and rely on your notes or scorecard. A meeting without consent simply does not enter the recording or transcript pipeline.
## Transcripts
Once a recording finishes processing, its audio is transcribed automatically into a written, timestamped record of the conversation. The transcript turns an hour of video into something you can read and search: find the exact exchange by searching the text, jump to that moment, and quote it precisely instead of paraphrasing from memory.
Because the transcript is generated from the recording, it exists only for meetings that were recorded with consent. No recording, no transcript.
## Where recordings and transcripts live
Recordings and transcripts attach to the meeting that produced them, so everything from one conversation stays in one place. From a finished recording the host can download it, share it through a controlled link, or cut a clip from a key segment rather than sending the whole call. Sharing controls — who can view and when access expires — are covered in [Share a dossier](/partners/meetings/share-a-dossier).
Recordings and transcripts appear after processing completes, not the moment the call ends. If a just-finished meeting shows nothing yet, give it time and reload.
## Retention and deletion
A recording and its transcript persist with the meeting until you remove them. Because the underlying recording is the source of the transcript and any analysis, deleting the recording is how you retire the conversation from the platform. Handle recordings as you would any other record containing personal data, in line with your own retention policy and the consent the participants gave.
## Related
- [Meeting Intelligence](/partners/meetings/meeting-intelligence)
- [Share a dossier](/partners/meetings/share-a-dossier)
- [Host controls](/partners/meetings/host-controls)
---
# Run interviews
URL: https://docs.thequantumclub.com/partners/meetings/run-interviews
> Run a scheduled interview in Quantum Meetings — consent-gated recording during the call, AI analysis waiting when it ends.
**Prerequisites:** a scheduled interview (see [Schedule interviews](/partners/hiring/schedule-interviews)); a browser with camera and microphone access.
## Join and run the interview
### Join from the meeting link
Open the meeting at its scheduled time. Quantum Meetings runs in the browser — no installation for you or the candidate. Candidates join from their side of the platform; external guests can join from a share link without an account.
### Check your setup
Confirm your camera and microphone before entering. In the room you have the standard controls — mute, camera, and screen share — for walking through materials or exercises.
### Run the conversation
The room is built for 1:1 and panel interviews with direct, full-resolution video. Larger group sessions are supported as well.
You should now be in the meeting room with your video tile visible and the candidate connected.
## Recording and consent
Recording is host-controlled and consent-gated:
- When recording is enabled, participants see **Recording Consent Required** before it starts, with the stated purpose — the meeting is recorded for quality and training purposes — and whether their video feed is included.
- While recording runs, everyone sees a persistent banner: the meeting is being recorded, and all participants have agreed to be recorded.
- Recording settings let the host control video quality, format, and audio options.
Do not start an interview recording without the candidate's consent acknowledged in the room. If a candidate prefers not to be recorded, run the interview unrecorded and rely on your scorecard.
## After the interview: recordings, transcripts, and AI analysis
Once the meeting ends, the platform processes what consent allowed:
- **Recordings** are available to review and to share internally with controlled links — you set who can view and when the link expires, and you can cut shareable clips from key segments.
- **Transcripts** make the conversation searchable: find the exact exchange by searching transcripts, summaries, and quotes instead of rewatching an hour of video.
- **AI analysis** summarizes the conversation, so interviewers who were not in the room get the substance quickly through your meeting intelligence views.
Use these as input to your scorecard, not a replacement for it — the scorecard remains the structured record your hiring decision stands on.
## Related
- [Instant meetings](/partners/meetings/instant-meetings)
- [Scorecards and feedback](/partners/hiring/scorecards-and-feedback)
- [Schedule interviews](/partners/hiring/schedule-interviews)
---
# Share a dossier
URL: https://docs.thequantumclub.com/partners/meetings/share-a-dossier
> Send a candidate dossier as a controlled link — watermarked, domain-locked, time-limited, and tracked.
**Prerequisites:** a partner account with permission to manage candidates, and a candidate whose dossier you want to share.
## What a shareable dossier is
A dossier is the assembled view of a candidate — the summary, career, skills, and conversation evidence drawn from their record and meetings. A shareable dossier is that view turned into a link you can send to a hiring manager or client who does not have a Quantum Club account. They open the link in a browser and read the dossier; they do not get an account, and they do not get your underlying data.
You choose which sections the recipient sees, so a client-facing share can carry the summary and skills without exposing internal notes.
## The controls on a shared link
A shared dossier is not a public document. Each link carries its own access controls.
- **Watermark.** You can stamp the dossier with watermark text — typically the recipient's name or company — so a screenshot or forward is traceable back to who it was shared with.
- **Domain lock.** Restrict viewing to specific email domains, so a link meant for one client cannot be opened by anyone outside their organization.
- **Expiry.** Every link expires. By default a share lapses after a set window (seven days), after which the link stops working until you issue a new one. You can also revoke a link at any time to cut off access immediately.
- **View tracking.** The link records how many times it has been viewed and when it was last opened, with viewer metadata captured per view — so you know whether the client actually looked at the candidate, and when.
You should now have a dossier link that is watermarked, locked to the recipient's domain, set to expire, and reporting views back to you.
## How to think about each control
### Set the watermark to the recipient
Watermark with the person or company you are sending to, not your own brand. The point is attribution: if the dossier leaks, the watermark tells you the source.
### Lock the domain to the client
If you are sharing with one company, restrict to their email domain. This is the difference between "anyone with the link" and "anyone at this client."
### Keep the expiry short
A short expiry limits how long a candidate's information stays live in someone else's inbox. Re-issue a link if the conversation runs longer than expected rather than leaving an old one open.
### Read the view data
Use the view count and last-viewed time as signal. A dossier that was never opened is a follow-up; one opened five times is interest.
You are sending a real person's information to a third party. Share only the sections the recipient needs, lock the link to their domain, set a short expiry, and revoke it when the conversation is over. Treat the candidate's consent and your retention obligations as the boundary, not the link's convenience.
## Related
- [Meeting Intelligence](/partners/meetings/meeting-intelligence)
- [Candidate signals](/partners/meetings/candidate-signals)
- [Recordings and transcripts](/partners/meetings/recordings-and-transcripts)
---
# Platform
URL: https://docs.thequantumclub.com/platform
> The security, identity, and privacy posture of The Quantum Club — written for the people who have to verify it.
GDPR rights in product, compliance posture, data residency, and subprocessors.
---
# SCIM provisioning
URL: https://docs.thequantumclub.com/platform/identity/scim
> Connect your identity provider over SCIM 2.0 so joiners, changes, and leavers propagate without a human in the loop.
## What SCIM gives you
- New hires are provisioned automatically — account created, profile populated.
- Attribute changes propagate from your directory within the IdP's sync cycle.
- Suspending a user in the IdP suspends them in The Quantum Club.
- Offboarding deprovisions the account; the profile is retained for audit.
The full endpoint and filter reference lives in the [API section](/api/scim). This page covers setup and operations.
## Tokens
Authentication uses a tenant-scoped bearer token in the format `tqc_scim_`. Key properties:
- The plaintext is shown **once** at issuance; only a PBKDF2-SHA256 hash is stored. Copy it immediately into your IdP.
- The tenant is resolved **from the token**, never from the URL — a misconfigured IdP cannot touch another tenant.
- Multiple unrevoked tokens per tenant are allowed, so rotation is overlap-free: issue the new token, swap it in the IdP, revoke the old one.
- Optional expiration dates are enforced; expired or revoked tokens receive `401`.
Tokens are issued and revoked from the SCIM administration area at [os.thequantumclub.com](https://os.thequantumclub.com). Issuing and revoking tokens are step-up-protected operations — see [MFA and sessions](/platform/security/mfa-and-sessions).
## User lifecycle
| Directory action | Effect in The Quantum Club |
| --- | --- |
| Create | Account created and activated; SCIM attributes mapped to the profile |
| Update | Name, email, and external ID changes applied |
| Suspend (`active: false`) | Account suspended; sign-in blocked |
| Reactivate (`active: true`) | Account restored |
| Deprovision (DELETE) | SCIM binding removed, account suspended; profile retained for audit. Subsequent SCIM reads return `404` |
Groups are recorded with their memberships. Group membership does not currently grant roles automatically.
## Filter examples
The list endpoints accept the filter subset that mainstream IdPs emit:
```text
userName eq "alice@acme.com"
externalId eq "00u1abcd2EFGHIJKL345"
active eq false
emails[type eq "work"].value eq "alice@acme.com"
```
Unsupported filters return `400` with `scimType: invalidFilter` — switch your IdP's matching attribute to `userName` or `externalId`.
## Connect your identity provider
On your app integration, open **Provisioning → Configure API Integration → Enable API integration**. Set the base URL to the SCIM users endpoint and paste the token, then select **Test API Credentials** — expect a `200` with an empty list. On **Provisioning → To App**, enable *Create Users*, *Update User Attributes*, and *Deactivate Users*. Okta's default attribute mappings work without changes. Assigned users are pushed within about 30 seconds.
On the enterprise application, open **Provisioning → Mode: Automatic**. Enter the SCIM users endpoint as the tenant URL and the token as the secret, then run **Test Connection**. Keep the default attribute mappings; confirm `objectId` maps to `externalId` and `mail` to the primary email. Set **Provisioning Status** to On. The initial sync runs in roughly 10 minutes; subsequent cycles run on Entra ID's fixed ~40-minute interval.
Google Workspace does not provide a native SCIM client for custom applications. Route provisioning through a SCIM-capable proxy or middleware that speaks SCIM 2.0 to the endpoints documented in the [API reference](/api/scim). SSO itself works natively — see [SSO](/platform/identity/sso).
## Monitor synchronization
Every SCIM call is recorded in a sync log with operation, resource, status, and latency, with secrets redacted from stored payloads. The log is retained for **90 days** and is browsable in the SCIM administration area, with filtering and full-payload drill-down. Every mutation also produces a security audit event.
A user provisioned into more than one tenant is suspended platform-wide if any connected IdP deprovisions them. Agree handling for shared users before connecting overlapping directories.
Your IdP's connection test returns 200, a test user appears after assignment, suspension in the directory blocks sign-in, and the sync log shows the operations you expect.
---
# Single sign-on (SSO)
URL: https://docs.thequantumclub.com/platform/identity/sso
> Connect SAML 2.0 or OIDC with domain-based discovery — your team signs in with the identity provider they already use.
## How it works
- **Protocols.** Both **SAML 2.0** and **OIDC** are supported. Pick whichever your identity provider handles best; capabilities are equivalent.
- **Domain-based discovery.** Once your email domain is verified, users who enter a matching address on the sign-in page are routed to your identity provider automatically — no tenant-specific URL to distribute.
- **Attribute and group mapping.** Assertions and claims map to profile attributes, and IdP groups can map to roles in The Quantum Club, so access follows your directory.
- **Security.** OIDC discovery and metadata URLs must be public HTTPS endpoints; internal or private-network addresses are rejected at configuration time.
SSO governs *authentication*. For automated user lifecycle (create, update, suspend, deprovision), pair it with [SCIM provisioning](/platform/identity/scim).
## Configure SSO
### Create the application in your IdP
Create a SAML 2.0 or OIDC application. The Quantum Club provides the service-provider details (ACS URL and entity ID for SAML; redirect URI for OIDC) in the admin security settings at [os.thequantumclub.com](https://os.thequantumclub.com).
### Register the connection
In the admin security settings, add your IdP metadata: the metadata URL or XML for SAML, or the issuer and discovery URL plus client credentials for OIDC.
### Verify your domain
Add your email domain so discovery can route your users. Until verification completes, SSO can be tested by direct initiation but is not auto-discovered.
### Map attributes and groups
Confirm email, given name, and family name mappings. Optionally map IdP groups to roles so role assignment is directory-driven.
### Test with one user
Sign in with a test account from your IdP before announcing the rollout. Check the resulting profile attributes and role.
## Identity provider notes
Create the app integration in the Okta admin console and choose SAML 2.0 or OIDC. Okta's default profile attributes map cleanly to the expected email and name fields. If you also plan SCIM provisioning, note that Okta configures it on the same app under **Provisioning** — see [SCIM](/platform/identity/scim).
Use **Enterprise applications → New application**. Entra ID works with either protocol; for SAML, confirm the Name ID format is the user's email. Group claims must be enabled explicitly in the token configuration if you intend group-to-role mapping. Provisioning is configured separately — see [SCIM](/platform/identity/scim).
Configure a custom SAML app from the Google Admin console. Map primary email to the email attribute and first/last name accordingly. Google Workspace has no native SCIM client for custom apps; if you need automated provisioning, route it through a SCIM-capable proxy.
## Troubleshooting
Domain verification is the usual cause. Confirm the email domain is verified and exactly matches what users type (subdomains are distinct domains).
An attribute mapping mismatch. Compare the assertion or token claims your IdP actually sends against the configured mappings, then re-test.
The discovery URL must be a publicly reachable HTTPS endpoint. URLs pointing at private or internal network ranges are blocked by design.
Verify the IdP is sending group information in the assertion or token, and that the group identifier in the mapping matches what is sent (name versus object ID differs by provider).
A test user signs in via your IdP, lands with correct name and email, and receives the expected role.
---
# Accessibility statement
URL: https://docs.thequantumclub.com/platform/privacy/accessibility
> How accessible The Quantum Club documentation is, the standard we hold it to (WCAG 2.2 AA / EN 301 549), the issues we know about, and how to tell us when something does not work.
The Quantum Club is committed to making this documentation usable by everyone,
including people who rely on assistive technology. This statement covers
**docs.thequantumclub.com** and is published in line with the European
Accessibility Act and EN 301 549.
## Conformance status
This site aims to conform to **WCAG 2.2 level AA**. It is currently **partially
conformant**: most of the experience meets AA, and the exceptions below are being
actively remediated.
## What works well
- Full keyboard operability of navigation, search, and the in-page assistant.
- Semantic headings, landmarks, and alternative text on meaningful images.
- A high-contrast monochrome design that meets AA contrast in both light and dark
themes for body text.
- Respect for `prefers-reduced-motion` for page and component transitions.
- A per-page "Copy as Markdown" and plain-text surface for assistive reading.
## Known issues (being fixed)
We are tracking these against a near-term remediation milestone:
- **Skip-to-content link** is not yet present on every page (WCAG 2.4.1).
- The **light-theme focus ring** does not yet meet the 3:1 non-text contrast
minimum on every control (WCAG 1.4.11).
- **Current-page indication** is visual but not yet exposed programmatically
(`aria-current`) in all navigation.
If you hit one of these, the workarounds are: use the search dialog (⌘K / Ctrl-K)
to jump directly to a page, and use your browser or OS high-contrast mode.
## Tell us about a barrier
If you encounter an accessibility barrier that is not listed here, please email
**accessibility@thequantumclub.com** with the page URL, what you were trying to do,
and the assistive technology you were using. We aim to respond within 5 business
days.
## How this statement was prepared
This statement is based on a self-assessment of docs.thequantumclub.com against
WCAG 2.2 AA, combined with automated checks (axe-core) and manual keyboard and
screen-reader testing. It was last reviewed on the date shown above and is
reviewed whenever the site's structure changes.
## Related
- [Security model](/platform/security/security-model)
- [GDPR](/platform/privacy/gdpr)
- [How we handle data on this site](/platform/privacy/docs-site-data)
---
# Compliance posture
URL: https://docs.thequantumclub.com/platform/privacy/compliance
> The compliance position, stated plainly — what is implemented, what is in readiness, and what is deliberately not claimed.
## GDPR
GDPR is the operating baseline, not an aspiration. Data-subject rights (export, deletion, rectification, consent withdrawal) are implemented in-product, recording consent is granular and documented, retention windows are defined, and data is hosted in the EU. Details: [GDPR and data rights](/platform/privacy/gdpr) and [trust and data residency](/platform/privacy/trust-and-data-residency).
A Data Processing Agreement (DPA) is available for customers.
## SOC 2 and ISO 27001
The Quantum Club does not currently hold a SOC 2 attestation or ISO 27001 certification. What follows describes the implemented control posture, which is built to those frameworks' expectations.
Controls in production that map to SOC 2 trust criteria and ISO 27001 Annex A:
- **Access control.** Role-based access enforced by database Row-Level Security; MFA required for elevated roles; step-up authentication for sensitive administrative operations. See the [security model](/platform/security/security-model).
- **Identity lifecycle.** SSO (SAML 2.0 / OIDC) and SCIM 2.0 provisioning give customers directory-driven joiner/leaver control with a retained audit trail — relevant evidence for user access management requirements.
- **Logging and monitoring.** Security-relevant events are recorded as audit events; authentication telemetry is scanned by automated anomaly detection every five minutes, with findings routed to the security team.
- **Cryptography.** TLS for data in transit; encryption at rest; credentials and provisioning tokens stored only as salted, iterated hashes.
- **Least privilege.** Client applications hold only anonymous-level keys; privileged keys are confined to server-side functions.
- **Change management.** Database changes ship as versioned migrations; deployments are gated and verifiable against the source repository.
Customers running their own audits can request the DPA and architecture details to support vendor assessments.
## EU AI Act readiness
The Quantum Club uses AI under the brand **Club AI**, and its positioning is deliberate:
- **Club AI assists humans; it does not decide.** Matching, recommendations, and analytics are decision support surfaced to recruiters, partners, and members — a human remains the decision-maker on hiring outcomes.
- **Assessments are screening support.** Assessment features are explicitly scoped as screening support based on observed work-sample evidence. They are not marketed or operated as standalone selection instruments, and they do not produce personality or clinical diagnoses.
- Scoring runs server-side under the same access controls as the rest of the platform, keeping outputs auditable.
This framing — assistive AI with human oversight, conservative claims about assessment validity — is the readiness posture for the EU AI Act's treatment of employment-related AI systems.
If your procurement process requires a certificate identifier or audit report reference for SOC 2 or ISO 27001, request the current status through your account contact rather than assuming one exists. The posture above is honest as of the verification date.
## Summary table
| Framework | Status |
| --- | --- |
| GDPR | Implemented in-product; EU hosting; DPA available |
| SOC 2 | Readiness posture; controls implemented, no attestation claimed |
| ISO 27001 | Readiness posture; controls map to Annex A, no certification claimed |
| EU AI Act | Readiness framing: assistive AI, human decision-makers, screening-support assessments |
You can answer a vendor questionnaire accurately: GDPR is implemented, SOC 2 and ISO 27001 are readiness postures with real controls behind them, and AI features are positioned as human-assistive.
---
# How we handle data on this site
URL: https://docs.thequantumclub.com/platform/privacy/docs-site-data
> What docs.thequantumclub.com itself collects and processes — feedback, search analytics, and the in-page assistant — kept deliberately minimal and free of tracking.
This notice covers **docs.thequantumclub.com** as a property — distinct from the
[product privacy](/platform/privacy/gdpr) pages, which describe how Club OS handles
member and partner data. The documentation site is built to collect as little as
possible.
## No tracking, no marketing cookies
This site sets **no marketing or advertising cookies** and does not track you across
sites. Your light/dark theme preference is stored locally in your browser
(`localStorage`), never sent to a server. Aggregate, **cookieless** traffic
analytics (page views, performance) are provided by Cloudflare Web Analytics, which
does not fingerprint or profile individual visitors.
## Page feedback
When you rate a page or leave a comment, we store the page URL, your up/down vote,
and the comment text — with a 180-day expiry. We do **not** store your IP address.
To count one vote per reader per day we derive a short hash from a daily-rotating
salt plus your IP; the raw IP is never persisted, and the hash cannot be reversed.
Comments are scrubbed for personal data (emails, phone numbers, and the like are
redacted) before they are ever written.
## Search analytics
When a search returns no results, we store the search term — scrubbed of personal
data the same way — so we can find and fill content gaps. These entries also expire
after 180 days and carry no identifier.
## Ask Club AI
The in-page assistant answers questions using the content of this site. Your
question is sent to **Cloudflare Workers AI** (a sub-processor) to generate an
answer; we may cache the answer briefly, keyed by a hash of the question, to keep
the feature fast and inexpensive. Do not enter personal or confidential information
into the assistant.
## Your rights
Because the site stores no identifiers, data here cannot be linked back to you, so
individual access or deletion requests do not apply to this property. For anything
concerning your Club OS account data, see [GDPR](/platform/privacy/gdpr) or contact
**privacy@thequantumclub.com**.
## Related
- [GDPR](/platform/privacy/gdpr)
- [Accessibility statement](/platform/privacy/accessibility)
- [Trust and data residency](/platform/privacy/trust-and-data-residency)
---
# Export or delete your data
URL: https://docs.thequantumclub.com/platform/privacy/export-and-delete-your-data
> Exercise your access and erasure rights from your own account settings — no ticket, no waiting on support.
Both your data export and your account deletion are self-service. You run them yourself from your account settings, against your own authenticated account. For how these map to GDPR rights more broadly, see [GDPR and data rights](/platform/privacy/gdpr).
## Export your data
From the privacy controls in your settings, you request a full export of the personal data the platform holds about you. The export is generated for your account and delivered as a single JSON file through a short-lived, private download link.
What the export covers:
- Your profile, candidate profile, and résumé records.
- Your applications, notifications, and preferences.
- Security records such as trusted devices and consent receipts.
- An inventory of your stored files across the platform's buckets.
Where you have connected an external service such as email or calendar, the export lists the connection but never includes the access or refresh tokens themselves. Secrets are deliberately excluded.
The download link is deliberately short-lived. If it expires before you save the file, request the export again.
## Delete your account
From the same privacy controls, you request deletion of your account. Because this is destructive, the flow asks you to confirm in two ways: a step-up identity check, and typing the exact phrase **DELETE MY ACCOUNT**.
A deletion request does not erase everything instantly. It opens a grace period — currently **14 days** — during which you can cancel the request and keep your account. You confirm the request through a link sent to you; the request is then processed automatically once the grace period ends.
## What deletion removes and what it keeps
Deletion is an erasure with lawful exceptions, not a blanket wipe. Personal data with no remaining retention basis is removed or anonymized:
- Your authentication identity is deleted and your profile data is anonymized.
- Messages you sent are redacted; your applications are detached from your identity.
- Security and device records are stripped of identifying fields.
Some records are minimized but retained where a legal or financial obligation requires it — for example referral earnings, payout records, and billing documents keep the transaction while clearing free-text and reference fields tied to you. This is the same retention principle described on the [GDPR](/platform/privacy/gdpr) page.
## Doing it
### Open privacy controls
Go to your account settings and open the privacy controls where export and deletion live.
### Export first if you want a copy
Run the export and save the JSON file before its download link expires. Deletion is irreversible once processed.
### Request deletion and confirm
Pass the step-up check, type the confirmation phrase, and confirm through the emailed link. Cancel any time inside the grace period.
You know where to export your data, that the download link is short-lived, and that deletion runs on a cancellable grace period after which identifying data is removed or anonymized while legally retained records are minimized.
## Related
- [GDPR and data rights](/platform/privacy/gdpr)
- [Trust and data residency](/platform/privacy/trust-and-data-residency)
---
# GDPR and data rights
URL: https://docs.thequantumclub.com/platform/privacy/gdpr
> See how data-subject rights work in the product itself — export, deletion, consent, and retention, exercised without a ticket.
## Rights exercised in-product
| Right | How it works |
| --- | --- |
| **Access / portability** | Users export their own data from account settings. The export is user-initiated and covers the personal data the platform holds about them. |
| **Erasure** | Users request deletion from account settings. Deletion is processed against retention obligations (see below); data without a retention basis is removed or anonymized. |
| **Rectification** | Profile data is user-editable directly; SSO/SCIM-managed attributes follow the organization's directory. |
| **Objection / consent withdrawal** | Consents — including meeting recording consent — can be declined or withdrawn; the corresponding processing does not occur. |
Both export and deletion are protected operations on the user's own authenticated account; they cannot be triggered anonymously against someone else's address.
## Meeting recording consent
Recording in Quantum Meetings is consent-gated before any capture begins:
- A blocking consent dialog appears before a recorded meeting starts capturing.
- Consent is **granular**: video, audio, and transcription are separate, unchecked choices — no pre-ticked boxes.
- Declining is always possible; a participant can leave the meeting instead of consenting.
- The consent decision and timestamp are recorded, so the lawful basis for each recording is auditable.
Granular, affirmative, documented consent is the GDPR Article 4(11) standard. The recording flow was designed against that definition rather than a generic "this call may be recorded" banner.
## Retention
Data is kept only as long as a defined purpose requires:
- Operational logs have explicit retention windows — for example, the SCIM synchronization log is pruned after **90 days**.
- Deprovisioned accounts (via [SCIM](/platform/identity/scim)) are suspended with the profile retained for audit, consistent with employment-related record obligations.
- Deletion requests remove or anonymize personal data that has no remaining retention basis.
## Anti-enumeration as a privacy control
Account-related flows such as recovery return identical responses for known and unknown email addresses. Whether a person uses The Quantum Club is itself treated as personal information and is not disclosed to probing third parties. See [account recovery](/platform/security/account-recovery-for-organizations).
## For organization admins
### Point data-subject requests at the product first
Export and deletion are self-service. Most Article 15 and 17 requests resolve without a support ticket.
### Brief recording hosts
Hosts should know that participants see a real consent gate and can decline. Plan meetings accordingly rather than treating recording as guaranteed.
### Use SCIM for leavers
Deprovisioning through your IdP gives you a directory-driven, auditable offboarding record — stronger evidence than manual account cleanup.
## Related
- [Compliance posture](/platform/privacy/compliance)
- [Trust and data residency](/platform/privacy/trust-and-data-residency)
You know where users export and delete their own data, how recording consent is captured, and which retention windows apply to operational logs.
---
# Trust and data residency
URL: https://docs.thequantumclub.com/platform/privacy/trust-and-data-residency
> Answer the three questions every security review asks first — where the data lives, how it is protected, and who else touches it.
## Where data lives
Customer data is hosted in the **European Union**:
- The primary database, storage, and server-side functions run on Supabase infrastructure in the EU (AWS `eu-west-1`, Ireland).
- The web application is delivered through Cloudflare's network, with the application served from [os.thequantumclub.com](https://os.thequantumclub.com).
Data residency in the EU is the default and only configuration — there is no setup step where customer data is moved to another region.
## Encryption
| Layer | Protection |
| --- | --- |
| In transit | TLS for all client, API, and inter-service traffic |
| At rest | Encrypted storage for the database, file storage, and backups |
| Credentials | Passwords and recovery codes stored as salted, iterated hashes; SCIM tokens stored as PBKDF2-SHA256 hashes — plaintext is never retained |
| Documents | Private files served through expiring signed URLs, never public buckets |
Beyond encryption, authorization is enforced inside the database itself via Row-Level Security — see the [security model](/platform/security/security-model). Encrypted data that the policy denies you is data you cannot query at all.
## Subprocessors
The Quantum Club keeps its subprocessor list short. At a high level:
| Subprocessor | Purpose | Region |
| --- | --- | --- |
| **Supabase** (on AWS) | Database, authentication, storage, server-side functions | EU (`eu-west-1`) |
| **Cloudflare** | Content delivery, DDoS protection, application hosting | Global network; EU-served traffic |
| **Stripe** | Payment processing | Payment data handled by Stripe under its own PCI DSS compliance; The Quantum Club does not store card numbers |
Supporting services (for example transactional email delivery) operate under data processing terms consistent with the DPA. The current authoritative subprocessor list is provided with the DPA.
## Data Processing Agreement
A **DPA is available** for customers and covers processing purposes, subprocessors, transfer mechanisms, and breach notification terms. Request it through your account contact during procurement or security review.
## What a reviewer should verify
### Residency
Confirm EU hosting meets your transfer requirements. Primary processing is in `eu-west-1`; edge delivery uses Cloudflare's network.
### Access model
Note that client applications never hold privileged database credentials — the anonymous key plus Row-Level Security is the entire client trust model.
### Contracts
Obtain the DPA and the current subprocessor list, and map them against your own Article 28 checklist.
For the broader control environment — MFA, step-up authentication, anomaly detection, rate limiting — see the [security model](/platform/security/security-model) and the [compliance posture](/platform/privacy/compliance).
You can state where the data is (EU, eu-west-1), how it is encrypted in transit and at rest, the three principal subprocessors, and that a DPA is available on request.
---
# Account recovery for organizations
URL: https://docs.thequantumclub.com/platform/security/account-recovery-for-organizations
> Know the five ways your users get back in when a credential is lost — and what to tell them before they lose anything.
## The five recovery paths
Recovery is layered so that losing one credential never means losing the account — and so that no single weak path undermines the rest.
| Path | When it applies |
| --- | --- |
| **Email** | Password lost; mailbox still accessible. A reset link or one-time code is sent to the account email. |
| **Recovery codes** | MFA factor lost. One-time codes issued at enrollment; each code works once. Stored only as salted PBKDF2 hashes — The Quantum Club cannot read them back. |
| **Passkey** | Password and MFA lost, but a registered passkey survives on a device. Signing in with the passkey restores access directly. |
| **SSO** | The account belongs to an SSO-connected organization. Access follows the identity provider; recover there, not here. See [SSO](/platform/identity/sso). |
| **Human concierge** | Everything else is lost. A verified human-review process, deliberately the slowest path. |
## Concierge verification
The concierge path never takes a caller's word for identity. Before a recovery link is issued, the reviewer must confirm **at least two of five** independent checks:
- Government-issued ID
- Account-knowledge questions
- A vouch from an existing organization admin
- Email domain match with the organization
- A confirmed phone number on file
The two-of-five threshold is enforced server-side; a single sympathetic support interaction cannot restore an account.
Social-engineering attacks target recovery flows precisely because they bypass strong sign-in. The concierge checklist exists to make "I lost everything, please let me in" a verifiable claim, not a persuasive one.
## Anti-enumeration
Recovery endpoints return **identical responses whether or not an email address has an account**. An attacker probing the recovery flow learns nothing about which addresses belong to The Quantum Club. Tell your users not to read meaning into a generic confirmation message — it is generic on purpose.
## What to tell your users
### Save recovery codes at enrollment
The codes are shown once. Users should store them in a password manager immediately — they cannot be re-displayed, only regenerated.
### Register a passkey on a second device
A passkey on a phone plus one on a laptop means a single lost device is an inconvenience, not an incident.
### Know who your admin vouchers are
For the concierge path, an admin vouch is one of the five checks. Decide in advance which admins are authorized to vouch, and verify out-of-band before vouching.
### SSO users recover at the identity provider
If your tenant uses SSO, account recovery is your IdP's process. Do not expect The Quantum Club to override a suspended IdP identity.
## Properties worth knowing
- Recovery sessions are short-lived and single-use; a recovery link that has been consumed cannot be replayed.
- Concierge-issued links have a slightly longer validity window to accommodate the human handoff, but remain one-time.
- Repeated recovery attempts are rate limited and feed the platform's [anomaly detection](/platform/security/security-model), which watches for recovery-flow abuse.
You can list all five recovery paths, explain the two-of-five concierge checklist, and your users know to save recovery codes and register a second passkey before they need them.
---
# MFA and sessions
URL: https://docs.thequantumclub.com/platform/security/mfa-and-sessions
> Know how MFA is enforced, when grace periods apply, and why some operations demand a fresh second factor mid-session.
## MFA enforcement
Multi-factor authentication is **required for elevated roles** — administrators, partner owners, and other accounts with privileged access. Standard member accounts are strongly encouraged but not forced to enroll.
### Grace period
When an account becomes subject to the MFA requirement (a new admin, a newly elevated role), it receives a grace period to enroll a second factor. During the grace period the account works normally and sees enrollment reminders. After it expires, access to protected surfaces requires completed enrollment.
### Recommended factors
- **Passkeys** are the preferred factor: phishing-resistant, no codes to copy, user verification enforced at the authenticator.
- TOTP authenticator apps are supported as a conventional second factor.
- Recovery codes back up both — see [account recovery](/platform/security/account-recovery-for-organizations).
## Step-up authentication
Holding a session is not enough for everything. Sensitive operations require **step-up**: a fresh second-factor proof (AAL2) completed within a short recency window, even if you authenticated earlier the same day.
Operations gated behind step-up include:
- Resetting another user's MFA
- Changing user roles
- Forcing a password reset
- Issuing or revoking SCIM provisioning tokens
- Revoking your own sessions
If the proof is missing or stale, the server rejects the request and the application prompts you to re-verify. This is enforced server-side; it cannot be bypassed by a modified client.
Step-up is why a stolen laptop with an open session cannot quietly escalate privileges. The attacker would still need your second factor, freshly.
## Session management
You can review and control your active sessions from account security settings at [os.thequantumclub.com](https://os.thequantumclub.com):
- **List** every active session with device and sign-in context.
- **Revoke** any session, including all sessions at once.
Revoking a session is itself a sensitive operation and requires a fresh step-up proof. This prevents an attacker who hijacked one session from using it to evict the legitimate owner's other sessions.
## Guidance for organization admins
### Enroll passkeys first
Direct users to enroll a passkey before relying on TOTP. Passkeys remove the most common phishing path entirely.
### Treat the grace period as a deadline
Track which elevated accounts are still inside their grace window and chase enrollment before it lapses, not after.
### Expect step-up prompts
Train admins that re-verification during sensitive actions is normal and deliberate. A step-up prompt that appears when no sensitive action was attempted is worth reporting.
You know which roles must have MFA, what the grace period does, which operations demand a fresh AAL2 proof, and how users revoke their own sessions.
## Related
- [Security model](/platform/security/security-model)
- [Account recovery for organizations](/platform/security/account-recovery-for-organizations)
---
# Security model
URL: https://docs.thequantumclub.com/platform/security/security-model
> Walk the defense-in-depth model layer by layer — authentication, database-level authorization, rate limiting, and anomaly detection containing each other's failures.
## Layered by design
No single control is trusted to hold on its own.
A request passes through independent layers, and a failure in one layer is contained by the next.
## Layer 1 — Passkey-first authentication
The strongest available method is always offered first:
- **Passkeys (WebAuthn)** with user verification required — phishing-resistant and bound to the device.
- **Magic links** and **passwords** as alternatives.
- **SSO** (SAML 2.0 and OIDC) for organizations, with domain-based identity provider discovery.
MFA is enforced for elevated roles, with a defined grace period for newly elevated accounts. See [MFA and sessions](/platform/security/mfa-and-sessions).
## Layer 2 — Step-up for sensitive operations
Authentication is risk-based, not binary. Sensitive administrative operations — MFA resets, role changes, forced password resets, session revocation — require a fresh, recent second-factor proof (AAL2) even when the actor already holds a valid session. A stolen session token alone cannot perform these actions.
## Layer 3 — Authorization at the database
Authorization is enforced by Postgres **Row-Level Security (RLS)** on more than 100 tables. Policies evaluate the authenticated identity on every query, inside the database itself:
- Client applications hold only the anonymous key; they can never bypass policy.
- Privileged (service-role) access is confined to server-side edge functions and never reaches a browser.
- A compromised client or a bug in the application layer still cannot read rows the policy denies.
## Layer 4 — Rate limiting
All authentication surfaces sit behind atomic, auth-aware rate limiting:
- A primary bucket keyed on **email plus IP address**, so one corporate network does not starve its own users.
- A separate **per-IP ceiling** that caps fan-out abuse from a single host.
- Authentication endpoints **fail closed**: if the limiter cannot be evaluated, the request is rejected rather than waved through.
The same model backs the public API; see [rate limits](/api/rate-limits).
## Layer 5 — Continuous anomaly detection
An automated detector scans authentication telemetry **every five minutes** for:
- Credential stuffing (many accounts attempted from one source)
- Password spraying (one password tried across many accounts)
- Velocity anomalies (sign-ins from multiple countries in a short window)
- Recovery-flow abuse (repeated reset attempts)
Detections currently run in alert mode: the security team is notified and investigates each finding.
Detection thresholds and response actions evolve over time. The detection categories above reflect production behavior as of the verification date.
## What this means for your organization
- You do not need to bolt on perimeter controls to use The Quantum Club safely; the controls travel with the data.
- Enforce SSO and SCIM for your tenant so joiners and leavers are governed by your identity provider — see [SCIM provisioning](/platform/identity/scim).
- Review the [privacy and residency posture](/platform/privacy/trust-and-data-residency) for where data lives and how it is encrypted.
You can name the five layers — passkey-first authentication, step-up, Row-Level Security, rate limiting, and anomaly detection — and explain why a failure in one does not compromise the others.
---
# Vulnerability disclosure
URL: https://docs.thequantumclub.com/platform/security/vulnerability-disclosure
> How to report a security vulnerability in The Quantum Club, what is in scope, and what to expect when you do — our coordinated disclosure policy and safe-harbor commitment.
The Quantum Club runs a coordinated vulnerability disclosure (VDP) program. If you
have found a security issue, we want to hear about it — and we commit to working
with you in good faith to resolve it.
## How to report
Email **security@thequantumclub.com** with enough detail to reproduce the issue:
the affected URL or endpoint, a description of the vulnerability, and the steps,
payloads, or proof-of-concept needed to confirm it. Our machine-readable contact
is published at [`/.well-known/security.txt`](https://docs.thequantumclub.com/.well-known/security.txt)
(RFC 9116).
Please report privately by email. Do not open public issues, post details on
social media, or disclose the vulnerability to third parties before we have had a
chance to remediate.
## What to expect
- **Acknowledgement** within 3 business days.
- **Triage and a severity assessment** within 10 business days, with a path to
resolution and an estimated timeline.
- **Coordinated disclosure** — we will agree a disclosure date with you once a fix
is shipped. We are happy to credit you (or keep you anonymous, your choice).
## Safe harbor
We will not pursue or support legal action against researchers who, in good faith:
- make a genuine effort to avoid privacy violations, data destruction, and service
degradation;
- only access the minimum data necessary to demonstrate a vulnerability;
- do not exploit an issue beyond what is needed to prove it, and do not exfiltrate,
retain, or share data;
- give us reasonable time to remediate before any public disclosure.
Activity conducted consistent with this policy is considered authorized, and we
will treat it as such.
## In scope
- `os.thequantumclub.com` (the Club OS application)
- `docs.thequantumclub.com` (this documentation site)
- The public API surface documented under [API](/api)
- SCIM and SSO provisioning endpoints
## Out of scope
- Findings that require a compromised device, rooted/jailbroken environment, or a
man-in-the-middle position you control
- Volumetric denial-of-service, rate-limit exhaustion, or load testing
- Social engineering of staff, members, or partners; physical attacks
- Reports from automated scanners without a demonstrated, exploitable impact
- Missing security headers or best-practice recommendations with no concrete attack
- Vulnerabilities in third-party services we do not operate
## Rewards
This is a coordinated-disclosure program, not a paid bug bounty. We recognize
researchers with public credit and, at our discretion, may offer tokens of thanks
for high-impact reports.
## Related
- [Security model](/platform/security/security-model)
- [Trust and data residency](/platform/privacy/trust-and-data-residency)
- [GDPR](/platform/privacy/gdpr)
---
# Support
URL: https://docs.thequantumclub.com/support
> How to check whether The Quantum Club is operational, how to report a problem, and what to expect when you do — routed by the kind of issue you have.
If something is not working, this page tells you where to go and what to expect.
## Is The Quantum Club down?
Check **[status.thequantumclub.com](https://status.thequantumclub.com)** first —
it shows the live status of every system and the history of past incidents. When
an incident is open, current updates appear there.
If the application at [os.thequantumclub.com](https://os.thequantumclub.com) is
unreachable or erroring for you:
1. Check [status.thequantumclub.com](https://status.thequantumclub.com) to see
whether it is a known incident.
2. If status is green, check your own connection and try a hard refresh.
3. If it persists, **report it** using the path below — include the time it
started and what you were doing.
## Report a problem
Route your report by what kind of issue it is — this gets it to the right people
fastest.
| Issue | Where to report |
| --- | --- |
| **Account, hiring, billing, or product** | Sign in at [os.thequantumclub.com](https://os.thequantumclub.com) and use in-app support. Partners can also raise it with their [Talent Strategist](/partners/get-started/overview). |
| **A security vulnerability** | Follow [Vulnerability disclosure](/platform/security/vulnerability-disclosure) — report privately to security@thequantumclub.com. |
| **An accessibility barrier** | See the [Accessibility statement](/platform/privacy/accessibility) — accessibility@thequantumclub.com. |
| **An error in these docs** | Use the **Was this helpful?** control at the bottom of any page, or open an issue if you have repository access. |
## What to expect
- **Product issues** raised through the application are triaged during business
hours (Europe/Amsterdam) and prioritized by impact.
- **Security reports** are acknowledged within 3 business days — see the
[disclosure policy](/platform/security/vulnerability-disclosure) for the full
timeline and safe-harbor terms.
- **Accessibility reports** receive a response within 5 business days.
## Escalating
If an issue is urgent — a suspected security incident, a data-protection concern,
or a complete outage — say so explicitly in your report so it can be escalated.
For anything affecting your personal data, see [GDPR](/platform/privacy/gdpr).
## Related
- [Status](https://status.thequantumclub.com) — live system status and incident history
- [Changelog](/changelog)
- [Partner troubleshooting](/partners/administration/troubleshooting)
- [How we handle data on this site](/platform/privacy/docs-site-data)