/ to search
Documentation Tenant Settings

Tenant Settings

Workspace Settings Tutorial

Use this tutorial the first time your team sets up an Altrinum workspace. The goal is not just to fill in fields, but to make sure the organization-level settings are ready before you publish donation pages, event registration, program checkout, or email campaigns.

Before you begin

Have these items ready:

  • your organization name exactly as you want staff and supporters to see it
  • the timezone your team wants as the default for events and programs
  • your logo, primary color, secondary color, and any shared public header or footer content
  • the branded subdomain you want to use for public pages
  • payment processor credentials for Stripe, Moneris, or BBMS New checkout
  • receipting details if your organization issues charitable documents
  • Google tracking ID if your team uses Google Tag Manager or a Google tag
  • your preferred campaign UTM naming convention

Step 1 - Open Workspace Settings

Go to Workspace Settings from the tenant dashboard. This page is restricted to tenant administrators.

Step 2 - Set workspace identity first

Open Workspace.

Set:

  • Workspace Name
  • Timezone

Then review the implications before you save:

  • The workspace name may be used in public URLs and integration settings.
  • The timezone becomes the default for events and programs that do not set their own timezone.

Save this step before you continue if you changed the organization name.

Step 3 - Add organization branding and public contact details

Open Branding.

Upload or enter:

  • Logo
  • Primary Color
  • Secondary Color
  • Contact Email
  • Contact Phone
  • Website
  • Header Content
  • Footer Content

These settings affect shared public layouts and tenant-branded email layouts. Public pages fall back to a simpler branded header or footer when custom header or footer content is blank.

Step 4 - Configure your custom domain

Open Domain.

Enter the exact branded subdomain you want to use, such as donate.yourorg.ca or events.yourorg.ca.

Important details confirmed in the implementation:

  • the field is for a subdomain only, not a root domain
  • you should not include https:// or a path
  • the page shows the exact DNS nameserver delegation steps
  • the default Altrinum link continues working until the custom domain is connected
  • the page also shows an email sender preview based on your workspace name and domain

Do not switch printed links, QR codes, or outbound campaign links until the branded domain works in a browser.

Step 5 - Choose and configure a payment processor

Open Payments.

Choose one processor:

  • Stripe
  • Moneris
  • BBMS New checkout (EAP)

Then complete only the matching settings section.

For Stripe:

  • add the account ID if your team tracks it
  • add the publishable key
  • add the secret key
  • copy the webhook endpoint shown in Workspace Settings into Stripe
  • enable the listed webhook events
  • paste the Stripe signing secret
  • run Test Stripe Connection

For Moneris:

  • add the store ID
  • add the API token
  • add the checkout ID
  • choose Test or Live
  • run Test Moneris Connection

For BBMS New checkout:

  • add the required environment and payment configuration values
  • treat this section as early access or beta setup unless your team has already validated it with Altrinum

Step 6 - Configure tax receipts and acknowledgments

Open Tax Receipts & Acknowledgments.

If you issue Canadian charitable receipts:

  • turn on the Canadian document eligibility
  • turn on We are a registered charity (Canada)
  • enter the CRA charity registration number
  • complete the Canada issuer profile, including the legal name, registered address, place issued, and authorized signatory
  • upload a signature image if your team uses one

If your team is using the U.S. acknowledgment path:

  • turn on the U.S. charitable acknowledgment option
  • enter the legal name
  • add the EIN if available

Use extra care here. These values are not just descriptive. They are used by the receipt and acknowledgment services for future document generation.

Step 7 - Review tracking defaults

Open Google Tracking if your team uses Google Tag Manager or a Google tag.

Open Campaign Email UTM Tracking if your team wants tenant-wide email link tagging defaults.

Set defaults only if your team wants consistency across many campaigns. Campaigns can still override UTM values later.

Step 8 - Enable Prospect Intelligence if your team wants it

Open Prospect Intelligence.

If you turn it on:

  • review the major gift and optional leadership annual thresholds
  • review advanced thresholds such as lapsed days and second-gift window
  • save the settings
  • run Refresh Prospect Scores

The settings alone do not update saved scores. The refresh step is required.

Step 9 - Enable Ask Altrinum if your team wants AI features

Open AI.

Turn on Enable Ask Altrinum if your team is ready to use tenant AI features. The settings page also shows the current shared balance and lifetime credit counters.

Step 10 - Complete the organization address

Open Organization Address.

Enter the billing address details your team wants used for invoices. This address is separate from the charitable issuer profile above.

Step 11 - Test critical public flows

After saving the full setup, test the live experience from an admin point of view and from a public-user point of view.

Test at least:

  • one public giving form on the default Altrinum URL
  • the same giving form on the branded domain if you configured one
  • one paid checkout flow for each public feature you actively use: donations, events, and programs
  • one recurring donation flow if your organization uses recurring gifts
  • one receipt or acknowledgment workflow if your organization issues charitable documents
  • one marketing email or test campaign if your team uses branded sending and UTM defaults
  • one Prospect Intelligence refresh if that feature is enabled
  • one Ask Altrinum question if AI is enabled

Common mistakes

  • changing the workspace name during an active campaign and forgetting to update copied callback URLs
  • entering a full URL instead of just the subdomain in Custom Domain
  • assuming the custom domain is ready before DNS has propagated
  • switching the payment processor without testing every public checkout path again
  • turning on charitable document settings before the issuer profile is complete
  • changing Prospect Intelligence thresholds and forgetting to refresh scores
  • assuming organization address and charitable issuer address are the same setting