Overview
This reference lists the confirmed staff-facing areas, settings, public behaviors, and donation-record details for giving forms.
Use this page when you need a quick reminder of:
- which giving-form features are available
- how public donation behavior works
- which details are preserved on donation records
- how the form connects to receipting and follow-up workflows
Staff-facing areas
The giving area includes:
Giving formsresourceDonationsresource- public donation page
- public thank-you page
- signed receipt download links
These areas work together across public fundraising, donor experience, donation review, and receipt-related handling.
Giving form settings
Confirmed settings include:
- name and slug
- publication status
- team visibility
- banner image
- suggested giving levels
- custom amount enablement and optional min/max bounds
- goal amount and progress bar
- matching message and date window
- honor roll settings
- fee coverage settings
- one-time and monthly gift options
- AI Ask Optimization inherit-or-override controls
- monthly receipt behavior
- one-time, monthly, confirmation email, and thank-you copy
- public marketing consent settings
- tracking source and subsource defaults
- designation enablement and allowed designation list
Setting guidance
Name and slug
Used to identify the form internally and publicly.
Publication status
Controls whether the form is a staff-only draft or ready for public use.
The staff form shows one primary Publication status control:
Draftkeeps the form hidden from public donation pages.Publishedmarks the form as ready for public donation pages.
Altrinum still keeps an internal is_active flag for backward compatibility with older records and integrations. Staff do not need to manage that flag in the normal form. When a staff user saves a form as Draft, the internal active flag is turned off. When a staff user saves a form as Published, the internal active flag is turned on.
Ask Altrinum-created forms always start as drafts. Its AI-generated copy can improve the starter fundraising language, but it does not publish the form, activate the page, choose unsupported settings, or make tax/legal claims that staff have not reviewed.
Team visibility
Used when the form should be associated with a particular team operationally.
Banner image and page copy
Shape the donor’s first impression and campaign framing.
Suggested giving levels and custom amount rules
Control the baseline preset amounts for the public donation page and whether donors can enter their own amount outside those presets.
Goal amount and progress bar
Used when the campaign should show visible momentum or a public target.
Matching message and date window
Used when a matching campaign should appear only during a defined period.
Honor roll settings
Control whether donor recognition appears publicly where supported.
Fee coverage settings
Allow donors to optionally help offset processing costs.
One-time and monthly gift options
Define whether the form supports single gifts, recurring gifts, or both.
AI Ask Optimization inherit-or-override controls
Each giving form can now either inherit the workspace AI Ask Optimization defaults or override them locally for that form only.
When a form uses local overrides, staff can control:
- whether AI Ask Optimization is enabled on that form
- the maximum ask adjustment percent
- the minimum prior gift count required
Monthly receipt behavior
Determines whether recurring donors receive monthly receipts or an annual consolidated receipt.
Public copy
Includes one-time and monthly messaging shown on the public giving form.
Confirmation and thank-you copy
Controls post-gift donor messaging by context:
- one-time donation thank-you page message
- monthly donation thank-you page message
- one-time donation confirmation email message
- monthly donation confirmation email message
Blank fields use Altrinum's default copy. The thank-you page still displays operational donation details separately, including reference, receipt status or number when available, amount, gift type, date, giving form, and designation. Confirmation emails still include operational details such as amount, date, designation, giving form, source, reference, recurring status, and the note that the message is not an official charitable tax receipt or acknowledgment.
The editor includes one-time and monthly confirmation email previews. These previews use sample donor, amount, designation, date, giving form, and reference data. They render the custom confirmation message inside Altrinum's full confirmation email and do not send email, create donations, or require a payment processor.
Custom confirmation email copy is inserted after Altrinum's greeting and before the automatic donation details panel. Staff usually should not duplicate the greeting, amount, designation, reference, recurring note, or receipt disclaimer unless that repetition is intentional.
These fields are separate from official receipt and acknowledgment language. Receipt emails and downloadable receipt PDFs are controlled by the receipting workflows.
Supported tokens are:
{{ donor_name }}{{ donor_first_name }}{{ organization_name }}{{ giving_form_name }}{{ amount }}{{ currency }}{{ frequency }}{{ designation_name }}{{ donation_date }}{{ receipt_number }}{{ transaction_id }}
Unknown tokens are left unchanged for visibility during review. Rendered copy is escaped in public HTML and email contexts, with line breaks preserved.
Public marketing consent settings
Control whether public donors can opt into future communications from the form.
Tracking source and subsource defaults
Support attribution and campaign tracking when the same form is shared across channels.
Designation enablement and allowed designation list
Control whether donors can direct their gift and which designation options are available.
Public donation behavior
Confirmed public behavior includes:
- requiring the form to be both
publishedand internally active - creating a donation record in pending state before payment completion
- support for one-time and monthly gifts
- validation of designation choices against the form's allowed list
- tribute fields
- tenant-level marketing consent capture
- prefilling known supporter details for authenticated public sessions
- Stripe, Moneris, and BBMS New checkout paths based on tenant setup
Public behavior notes
Pending donation record before payment completion
The system creates a donation record in a pending state before the payment completes.
This is useful for preserving the attempt and supporting later operational review.
One-time and monthly gifts
The public flow can support both single gifts and recurring commitments depending on the form setup.
Designation validation
Donors can only choose designations that are allowed on the form and still valid.
Tribute fields
The public flow can capture tribute-related details where that giving experience is supported.
Marketing consent
Public marketing consent capture is separate from donation and receipt handling.
Authenticated prefilling
Known supporter details may be prefilled in authenticated public sessions where supported.
Checkout provider behavior
The payment path depends on the tenant’s configured processor, including Stripe, Moneris, or BBMS New where applicable.
Donation records
Donation records can include:
- donor identity and address
- amount and total amount
- gift type
- designation
- tracking source and subsource
- receipt number and receipt status
- tribute details
- fee coverage snapshot
Donation record usage notes
These fields help staff answer questions such as:
- who made the gift
- whether the gift was one-time or recurring
- which form or campaign context was involved
- whether the donor selected a designation
- whether a receipt was issued
- whether the donor chose to cover fees
- whether tribute details need follow-up
Receipting and recurring notes
- Monthly gifts use different follow-up handling depending on the form’s receipt setting.
- Progress calculations use paid donations tied to that giving form.
- Receipt-related handling should be reviewed from the donation record and related workflows rather than inferred from payment processor exports alone.
Operational notes
- A giving form is usually most effective when it supports one clear campaign or donor journey.
- Public features such as goals, matching, and honor rolls are most useful when they reinforce the campaign rather than compete with it.
- Designation choice should be curated carefully to avoid clutter and confusion.
- Tracking defaults may be overridden by public link parameters depending on how the form is shared.
Notes
BBMS Newcheckout is present in code and should be treated as beta or EAP unless your workspace has confirmed access.- Public progress is calculated from paid donations associated with the form.
- Donation records preserve important fundraising and receipt context beyond the payment result alone.
Example usage
A year-end appeal form might combine:
- a campaign banner
- one-time and monthly gifts
- a visible goal
- a matching timer
- a short thank-you message
A tribute form might instead focus on:
- simple donation flow
- tribute fields
- limited designation choice
- receipt-related clarity
- minimal public momentum features