Glossary

Short definitions for terms the UI uses. Linked from the first mention in each guide.

Capability

A fine-grained per-module permission switch (e.g. events.manage, requests.read). See Roles & capabilities.

Campaign

A composed email send (one-shot or scheduled), with a recipient snapshot, a comms style, and consent gating. See Email Campaigns.

Campaign code

A short token attached to a campaign send. Lets you measure use (e.g. requesters whose request came in through a specific newsletter).

Comms style

Reusable template for tone, signature, and footer of an email. Every campaign picks one. See Comms styles.

A contact’s permission level for receiving CartonCrew email: None / Campaign / Marketing. See Consent tiers.

Engagement

A unit of work with a client (status: discovery / active / complete). Carries deliverables, AI-drafted documents, and history.

Extension

An optional module in CartonCrew (Website CMS, Email Campaigns, Reports, etc). Owner toggles them on per tenant from Settings → Extensions.

Hours

Volunteer time logged against an Event’s shifts. Folded into the Events module since the Shifts extension was retired.

Org / Organisation

A single CartonCrew tenant. Each org has its own subdomain, users, data, and extensions.

PII

Personally identifiable information — names, emails, phone numbers, addresses. CartonCrew encrypts certain PII fields at rest (CARTONCREW_PII_KEY) and redacts them in some flows after request completion.

Program

A named offering of the org — “After-school tutoring”, “Holiday gift drive”. Each program is a page on the public site with actions (Volunteer / Donate / Wish list).

RBAC

Role-based access control. CartonCrew uses role + capability RBAC: the role gives coarse defaults, capabilities are the per-module switches.

Recipient snapshot

A campaign’s frozen list of recipients at compose time. Stops “ghost recipients” — someone whose consent changed between drafting and sending.

Requester / Recipient

The party asking for help (Requester) and the party the help is for (Recipient — may be the same person, or e.g. a parent asking on behalf of a child).

RLS

Row-level security in Supabase. Every CartonCrew tenant table has an RLS policy that scopes reads/writes to the tenant the request came from.

Shift

A unit of an event with its own time, capacity, and signups. An event can have one or many.

Tenant

Same as Org. The “tenant” framing is more common when talking about routing + database scoping; “org” is more common in product copy.

Last updated: 2026-06-01 · Applies to: CartonCrew v1.54+