Workspace Basics

Why this area exists#

The Workspace section holds the identity settings that other parts of the platform assume are already correct.

• Workspace Name is the organization name Altrinum uses throughout the tenant experience.
• Timezone is the default timezone for time-based records that do not define their own timezone.

These look simple, but they are foundational. If they are wrong, later setup work can look inconsistent even when the feature itself is functioning.

What changes after configuration#

Workspace name#

The settings UI warns admins not to change this often. That warning is justified.

Confirmed downstream impact:

• the organization name is used in public branding
• the organization name is used in email sender naming when no explicit name overrides it
• the platform warns that the name may be used in public URLs and integration settings
• if your team has copied callback URLs or public links elsewhere, those may need to be updated after a name change

Timezone#

The workspace timezone is optional, but when it is set it becomes the default timezone for:

• events that do not define their own timezone
• programs that do not define their own timezone

This means the workspace timezone is best treated as your organization default, not as a field to change for one special event.

When admins should configure it#

Set these values immediately after workspace creation and review them again before:

• publishing your first event
• launching a program with date-based scheduling
• distributing public links widely
• configuring payment providers or callback URLs

Setup guidance#

1. Open Workspace Settings > Workspace.
2. Enter the Workspace Name exactly as your organization wants it displayed.
3. Choose the default Timezone your team expects to use most often.
4. Save the settings.

Operational notes#

• If your team runs across multiple regions, the workspace timezone should still represent the default organization assumption. Individual events or programs can still define their own timezone later.
• Name changes are safer before launch than during an active public campaign.
• If you use a custom domain, review domain-related sender previews and copied payment instructions after any name change.

Common mistakes#

• treating the workspace timezone like an event-specific field
• changing the workspace name mid-campaign without rechecking public links
• assuming feature pages will always override the workspace default when some records do not

What to test after changes#

• one event without a custom timezone
• one program without a custom timezone
• one public page using tenant branding
• one outbound email or sender preview if you changed the organization name

Related topics#

• Branding and White-Labeling
• Custom Domain Setup
• Organization Address and Contact