Plan a consistent customer experience.
A consistent shared experience
Customer Accounts and portable branding give a customer consistent names, assets, colours, light and dark themes and public support links across the services.
Keep account context separate from access
An account groups service resources and owns a local branding profile. Switching customer context does not grant tenant administration, certificate issuance, assessment or approval rights. Each service continues to enforce its own permissions.
Preserve the sign-in choices already in use
In dc:id, existing tenant-specific branding can remain an explicit override. Agree whether a new tenant inherits its account profile or keeps a separate appearance.
Use explicit portability
Export and import the reviewed customer profile or account package. Memberships, resource permissions, credentials and environment configuration do not travel with it, and there is no automatic background synchronization of local changes.
Plan customer domains and email properly
Names and appearance are distinct from registered domains, issuers and callbacks. Custom sending identities require environment-local provider approval. Transferring a branding profile does not verify a domain or give the other services an email-delivery capability.
Evaluate the actual customer journey
Review sign-in, account switching, both themes, mobile use and the resource permissions that should remain unchanged. Confirm the deployed release and support scope with Data Clan.