New Partner Onboarding

This guide covers the full setup process for a new partner organization on the Lumieos platform. A partner is a tenant organization that uses Lumieos under their own branding — with their own app name, domain, logo, and email sender identity.

This page is for both InnovAlda staff performing the technical configuration and partner organizations who need to understand their options and what to prepare.

Before You Begin: Making Key Decisions

Before starting setup, agree on the following two choices with the partner. These decisions affect what DNS records (if any) the partner will need to add.

Domain

Email Sender

Prerequisites Checklist

Collect the following from the partner before beginning setup.

Partner provides

• Organization name and mailing address
• Billing contact email and phone number
• Website URL
• Desired app name — shown to users in the UI (e.g. CVR Robotics Portal)
• Desired key — short slug used in URLs and API paths (e.g. cvr); lowercase, no spaces, unique, max 20 characters
• Domain choice (see above):
  • Lumieos subdomain: desired prefix (e.g. portal → portal.lumieos.com)
  • Custom domain: the full domain to use (e.g. portal.partnerorg.com)
• Email sender choice (see above):
  • @lumieos.com: desired sender address (e.g. events@lumieos.com)
  • Partner domain: the domain to send from (e.g. partnerorg.com)
• Logo assets — see Step 1 for specifications

InnovAlda prepares

• Cloudflare for SaaS hostname entry (custom domain path only)
• AWS SES domain setup and sending quota confirmation (partner email path only)

Step 1 — Prepare Logo Assets

Four image files are required. They must be placed in the static assets directory before deploying, organized under the partner’s key.

All images should be PNG format. Replace {key} with the partner’s short key (e.g. cvr).

Directory structure:

images/partners/{key}/
  app_icons/
    favicon.png
    app-192.png
  email_logo.png
  menu_logo.png

Step 2 — Domain Setup

Option A: Lumieos Subdomain

Minimal setup. Set cname_host to {prefix}.lumieos.com in the partner record. InnovAlda must confirm the chosen hostname is covered by the Lumieos Cloudflare zone (a wildcard record typically covers *.lumieos.com).

No DNS action is required from the partner.

Option B: Custom Domain via Cloudflare for SaaS

Cloudflare for SaaS allows a partner’s custom domain to be routed through the Lumieos Cloudflare zone. InnovAlda manages the Cloudflare configuration; the partner adds DNS records on their end.

1. InnovAlda adds the custom hostname in the Cloudflare for SaaS dashboard under the Lumieos zone.

2. Cloudflare generates a domain ownership verification record. InnovAlda provides the details to the partner:

   Field	Value
   Record type	TXT
   Name	_cf-custom-hostname.{partner-domain}
   Value	(provided by InnovAlda from the Cloudflare dashboard)

3. Partner adds the TXT record to their DNS.

4. Partner adds the CNAME routing record to their DNS:

   Field	Value
   Record type	CNAME
   Name	{subdomain} (e.g. portal)
   Target	(provided by InnovAlda — a lumieos.com target)
   Proxy status	DNS only (do not proxy through partner’s Cloudflare, if applicable)

5. InnovAlda confirms the hostname status shows as Active in the Cloudflare for SaaS dashboard.

6. InnovAlda confirms the app loads correctly at the custom domain.

DNS propagation can take up to 24–48 hours depending on the partner’s DNS provider. TXT record verification typically completes faster once the record is live.

Step 3 — Email Sender Setup

Option A: @lumieos.com Sender (Default)

No additional setup required.

Confirm that from_email on the partner record is set to the desired address (e.g. events@lumieos.com) and that ses_sender_domain is left blank. Emails will be sent via the global Lumieos SES configuration.

Option B: Partner Domain via AWS SES

AWS SES requires the partner’s sending domain to be verified before emails can be sent from it. This involves adding DNS records to the partner’s domain.

1. InnovAlda adds the partner’s sending domain in the AWS SES console (default region: af-south-1).

2. SES generates a domain verification TXT record. InnovAlda provides the details to the partner:

   Field	Value
   Record type	TXT
   Name	_amazonses.{partner-domain} (e.g. _amazonses.partnerorg.com)
   Value	(provided by InnovAlda from the SES console)

3. SES generates three DKIM CNAME records for email authentication. InnovAlda provides all three to the partner:

   Field	Value
   Record type	CNAME (×3)
   Names	{token1}._domainkey.{partner-domain}, {token2}._domainkey.{partner-domain}, {token3}._domainkey.{partner-domain}
   Values	{token1}.dkim.amazonses.com, {token2}.dkim.amazonses.com, {token3}.dkim.amazonses.com

   (Exact token values are provided by InnovAlda from the SES console — they are unique per domain.)

4. Partner adds all four DNS records (1 TXT + 3 CNAME) to their domain.

5. InnovAlda confirms the domain status shows as Verified and DKIM shows as Success in the AWS SES console.

6. InnovAlda sets ses_sender_domain on the partner record to the verified domain (e.g. partnerorg.com).

7. Confirm from_email is set to an address at the verified domain (e.g. events@partnerorg.com).

SES verification typically completes within minutes once DNS records propagate, but can take up to 72 hours.