Celiq
v0.12Open app โ†—
Docs/Administration/Workspace Settings

Workspace Settings

Configure your workspace name, timezone, week start, default connection, currency, locale, and Slack webhook from Lumen Account Settings.

LuminaryUpdated June 2026 ยท 6 min read
โœฆ
In this section
Part of Celiq's semantic layer platform. Connect your warehouse, model your data once, query it everywhere.
๐Ÿ’ก
Tip
What it is โ€” The single page where a Luminary sets workspace-wide defaults: name, timezone, week start, default warehouse connection, default currency, number locale, and the Slack webhook for alerts.
When to use it โ€” Right after you create a workspace, and any time your org's reporting conventions change (new fiscal week, different currency, a new Slack channel for Signals).
Where to find it โ€” Lumen โ†’ Account โ†’ Settings (/lumen/settings).
Who can use it โ€” Luminary only. These settings affect everyone in the workspace.

Workspace Settings holds the org-level defaults that the rest of Celiq falls back to when something doesn't specify its own value. Several of these fields are not cosmetic: week start, default currency, and default locale feed value formatting and period calculations across Discover, Mosaics, the Weekly Brief, and Orion's answers. Get them right once and every chart, KPI tile, and date filter in the workspace behaves consistently.

This page covers the workspace-level settings managed by a Luminary. Per-member settings (seat usage, demo-project visibility, pending invites) live on a separate screen โ€” see Users & Roles.

Overview

The Settings page loads the current workspace record (via GET /api/admin/settings) and saves your edits back (via PUT /api/admin/settings). It is split into two cards:

  • Workspace settings โ€” the editable defaults, with a single Save changes button at the bottom.
  • Danger zone โ€” the Delete workspace action, kept separate and gated behind a confirmation.

The fields in the Workspace settings card are:

FieldWhat it controls
Workspace nameThe display name for your workspace.
Default warehouse connectionThe connection used when a domain doesn't name its own.
TimezoneThe reference timezone for date/time handling, chosen from a fixed list.
Week starts onWhether the week begins Monday or Sunday โ€” drives "This week" / "Last week" filters.
Default currencyThe fallback ISO currency code for metrics that don't set their own.
Number localeThe BCP-47 locale that controls digit grouping and currency symbol placement.
Slack webhook URLThe incoming webhook that Signals alerts are posted to.

When to use it

  • Initial setup โ€” set the workspace name, pick a default connection, and confirm timezone, week start, currency, and locale before your team starts building.
  • Currency or locale is wrong โ€” if amounts show the wrong symbol or grouping (for example commas where you expect periods), update Default currency and Number locale.
  • Your week is off by a day โ€” if "This week" / "Last week" filters don't line up with how your org reports, switch Week starts on.
  • Moving Signals to a new channel โ€” paste a new Slack webhook URL.
  • Decommissioning a workspace โ€” use the Danger zone (which routes you to support).

Concepts

Default warehouse connection โ€” A workspace can have several warehouse connections. The default is used whenever a domain doesn't specify its own connection. The dropdown lists each connection by its label (or name) and warehouse type, plus a None selected option. Timezone โ€” Chosen from a fixed list of supported zones (for example UTC, America/New_York, Europe/London, Asia/Kolkata, Asia/Tokyo, Australia/Sydney). You cannot type a free-form zone; you pick one from the list. Week start โ€” Either monday or sunday. This is the only set of valid values; the backend ignores anything else and keeps the existing setting. It controls how relative date filters like "This week" and "Last week" are computed for the whole org. Default currency โ€” A 3-letter ISO 4217 code (for example USD, EUR, GBP, INR, JPY). It is the fallback for any metric that doesn't declare its own currency. Number locale โ€” A BCP-47 language tag (for example en-US, en-GB, de-DE, ja-JP). It controls digit grouping and where the currency symbol sits relative to the number. Slack webhook URL โ€” A Slack incoming webhook (https://hooks.slack.com/services/...). Signals alerts are delivered to whichever channel the webhook targets.

Getting started

Prerequisites
  • You must be signed in as a Luminary. These settings are workspace-wide.
  • To set a Default warehouse connection, at least one connection must already exist. See Warehouse connections.
  • To use the Slack webhook URL, create an incoming webhook in Slack first. See Slack alerts.
How to open it

Open Lumen, then in the left navigation go to the Account group and click Settings. The page is at /lumen/settings.

Step-by-step

1

Open Lumen โ†’ Account โ†’ Settings

From the left navigation in Lumen, expand the Account group and choose Settings. The Workspace settings card loads with your current values.

2

Set the workspace name

Type a name in Workspace name. This is how your workspace is labelled across the app.

3

Choose a default warehouse connection

Open the Default warehouse connection dropdown and pick a connection, or leave it as None selected. This is the connection Celiq uses when a domain doesn't specify its own.

4

Pick your timezone and week start

Choose a Timezone from the list, then set Week starts on to Monday or Sunday. The week start drives how "This week" / "Last week" filters are calculated for everyone in the org.

5

Set currency and number locale

Choose a Default currency (the fallback for metrics that don't set their own) and a Number locale (which controls digit grouping and currency symbol placement). Set these to match how your org reports.

6

Add the Slack webhook (optional)

Paste your Slack incoming webhook into Slack webhook URL if you want Signals alerts posted to a channel. Leave it blank to disable Slack delivery.

7

Save

Click Save changes. The button briefly shows โœ“ Saved to confirm. Your values are persisted to the workspace and take effect across the app.

Examples

A US e-commerce team standardising on a Monday-start week, US dollars, and US number formatting would save the following values:

Workspace settings (saved values)
{

"workspace_name": "Acme Analytics",

"default_timezone": "America/New_York",

"week_start": "monday",

"default_connection_id": "conn_8f12",

"default_currency": "USD",

"default_locale": "en-US",

"slack_webhook": "https://hooks.slack.com/services/T000/B000/XXXX"

}

A UK team reporting in pounds with British number formatting would instead set default_currency to GBP and default_locale to en-GB, so that amounts render with the ยฃ symbol and UK digit grouping everywhere. An India-based team would pick Asia/Kolkata, INR, and en-IN.

Best practices

  • Set defaults before your team builds. Currency, locale, and week start shape every metric and date filter, so lock them in early to avoid re-checking dashboards later.
  • Match currency and locale to each other. Pairing GBP with en-GB, or EUR with de-DE, gives consistent symbols and grouping. A mismatched pair (for example EUR with en-US) still works but can look odd.
  • Pick a default connection if most of your domains share one warehouse โ€” it saves repeating the connection in every domain.
  • Use a dedicated Slack channel for the webhook so Signals alerts don't get lost in a busy channel.

Tips

๐Ÿ’ก
Tip

Workspace currency and locale are fallbacks. A metric that declares its own currency or format overrides the workspace default โ€” so you only need to change these settings for the values that don't already format themselves.

Common mistakes

โš ๏ธ
Warning
  • Expecting Delete workspace to wipe data instantly. It doesn't. Confirming the action directs you to email support@celiq.co for manual confirmation โ€” there is no self-serve destructive delete.
  • Typing a custom timezone or week start. Timezone is a fixed list, and week start accepts only Monday or Sunday. Any other week-start value is ignored and your previous setting is kept.
  • Leaving the Slack webhook blank and expecting alerts. With no webhook saved, Signals alerts are not posted to Slack.
  • Forgetting to click Save changes. Edits aren't persisted until you save; navigating away first discards them.

Troubleshooting

SymptomCauseFix
Week start change didn't stickA value other than monday/sunday was submitted; the backend ignores it and keeps the existing settingRe-select Monday or Sunday from the dropdown and save again.
Currency change didn't stickThe code wasn't a valid 3-letter ISO code, so it was ignored and the existing currency keptChoose a valid currency (for example USD, EUR, GBP) and save.
Locale change didn't stickThe value wasn't a valid BCP-47 tag, so it was ignoredChoose a valid locale (for example en-US, de-DE) and save.
Default connection list is emptyNo warehouse connections exist yet for the workspaceAdd a connection first โ€” see Warehouse connections โ€” then return and pick it.
Signals alerts aren't reaching SlackNo webhook saved, or the webhook URL is wrong/revokedPaste a valid https://hooks.slack.com/services/... URL and save.
Settings page won't load or saveThe request to /api/admin/settings failed (server error)Reload the page; if it persists, check your connection and try again.
"Delete workspace" doesn't deleteThis is by design โ€” it surfaces a notice to contact supportEmail support@celiq.co to request manual deletion.
  • Users & Roles โ€” member-facing settings: seat usage, demo-project visibility, and pending invites.
  • Billing โ€” seats, usage, and plan for the workspace.
  • Slack alerts โ€” set up the incoming webhook used by the Slack webhook URL field.
  • Warehouse connections โ€” create the connections that appear in the Default connection dropdown.
  • Lumen overview โ€” the full admin area and where Settings sits within it.