That matters because many teams configure a giving form, event, or campaign and assume all of the organization details already flow through correctly. In Altrinum, those feature pages often depend on the workspace-level settings being complete first. If Workspace Settings are incomplete, the feature itself may still exist, but the public experience, payment flow, sender identity, tracking, or receipt behavior may be wrong.
What belongs here
Workspace Settings are for decisions that apply across the organization, including:
- workspace identity such as your organization name and default timezone
- organization-wide branding such as logo, colors, contact details, and shared public header or footer content
- your public custom domain
- payment processor credentials and connection checks
- receipting and acknowledgment issuer details
- default campaign UTM behavior
- Google tracking setup
- Prospect Intelligence thresholds
- Ask Altrinum access
- organization billing address details used for invoices
What does not belong here
Workspace Settings do not replace feature-specific setup.
- A giving form still controls its own donor experience, designations, recurring receipt schedule, and other form-level settings.
- An event still controls its own registration options, capacity, ticketing, and event-specific contact information.
- A program still controls its own checkout and registration behavior.
- An email campaign still controls its own content, audience, schedule, and optional UTM overrides.
The practical rule is simple: if the setting should stay consistent across the whole organization, it probably belongs here. If it changes by campaign, event, program, or form, it usually belongs on that record instead.
How changes ripple through the platform
Several Workspace Settings have downstream effects that are easy to underestimate:
- Changing the workspace name can affect public URLs and copied callback URLs.
- Changing the timezone changes the default timezone used when events or programs do not define their own timezone.
- Changing branding updates shared public layouts and tenant-branded email layouts.
- Changing the custom domain changes how public donation, event, program, and member-facing links can be generated.
- Changing the payment processor changes which credentials and checkout paths public payment flows depend on.
- Changing receipting details affects future donation receipt and acknowledgment generation.
- Changing campaign UTM defaults affects future marketing email link tagging when campaign-level overrides are blank.
- Changing Prospect Intelligence thresholds does not update saved prospect scores until a refresh is run.
- Turning Ask Altrinum on changes navigation and access to tenant AI features.
What is still platform-level
Even with a branded workspace, some parts of the experience remain platform-managed in the current implementation:
- Stripe webhooks still point to Altrinum's secure hooks domain.
- Public media files are served from the central app storage origin rather than from your custom domain.
- There is no separate favicon setting in Workspace Settings.
- The settings page does not expose advanced email-domain infrastructure controls beyond the sender preview.
Recommended reading order
Use these pages as a small settings handbook:
- Workspace Basics
- Branding and White-Labeling
- Custom Domain Setup
- Payments
- Tax Receipts and Acknowledgments
- Campaign UTM Tracking
- Google Tracking
- Prospect Intelligence
- Ask Altrinum and AI
- Organization Address and Contact