# Account configuration

Account configuration covers the technical setup that underpins how your UbiQuity account sends and tracks communications. Some settings can be managed directly by account admins, while others require the UbiQuity team to configure on your behalf.

***

### Registered domains

A registered domain is the sending domain your UbiQuity account uses to send emails — for example, `email.yourcompany.co.nz`. Setting up a registered domain ensures your emails are correctly authenticated and improves deliverability.

All new clients are required to configure a set of DNS records with their DNS provider before UbiQuity can send emails on their behalf. The same process applies to existing clients setting up an additional sending domain.

UbiQuity will provide the specific DNS record values for your domain. The records you will need to configure are as follows.

#### DKIM (DomainKeys Identified Mail)

DKIM adds a digital signature to your outgoing emails, allowing receiving mail servers to verify that the email genuinely came from you and has not been tampered with in transit. Three DKIM CNAME records are required per sending domain.

#### DMARC (Domain-based Message Authentication, Reporting & Conformance)

DMARC tells email providers how to handle messages that fail authentication checks — for example, whether to reject or quarantine them. It also provides reporting on messages sent from your domain. A single DMARC TXT record is required.

#### Custom MailFrom (SMTP / Return-Path)

The Custom MailFrom record changes the technical sender address used behind the scenes, so all parts of the email appear to come from your domain rather than the underlying sending service. This supports DMARC alignment and improves deliverability. A CNAME record is required.

#### DNS records summary

Once UbiQuity provides your specific values, you will need to create the following records with your DNS provider:

| What            | Type  | Name                                               | Value                                         |
| --------------- | ----- | -------------------------------------------------- | --------------------------------------------- |
| DKIM            | CNAME | `ubiquity-dkim1._domainkey.email.yourdomain.co.nz` | Provided by UbiQuity                          |
| DKIM            | CNAME | `ubiquity-dkim2._domainkey.email.yourdomain.co.nz` | Provided by UbiQuity                          |
| DKIM            | CNAME | `ubiquity-dkim3._domainkey.email.yourdomain.co.nz` | Provided by UbiQuity                          |
| DMARC           | TXT   | `_dmarc.email.yourdomain.co.nz`                    | `v=DMARC1; p=reject; pct=100; fo=1; ri=3600;` |
| Custom MailFrom | CNAME | `smtp.email.yourdomain.co.nz`                      | Provided by UbiQuity                          |

Contact UbiQuity to begin the process of registering a sending domain for your account.

***

### Custom host headers

By default, tracked links, View Online links, and form, survey, and event URLs in your UbiQuity emails use a UbiQuity domain. A custom host header replaces this with a branded domain of your choosing — for example, `email.yourcompany.co.nz` instead of `engage.ubiquity.co.nz`.

Setting up a custom host header requires two additional DNS records to be created with your DNS provider.

#### Host Header (CNAME)

A CNAME record that points your custom subdomain to the UbiQuity platform. UbiQuity maps the request to the correct account internally based on your account settings.

#### SSL/TLS Certificate

An SSL/TLS certificate encrypts the connection and proves the domain is legitimate, ensuring visitors are communicating with the real site securely. A CNAME validation record is required to issue the certificate. UbiQuity manages SSL/TLS certificates on behalf of clients through ACM (Amazon Certificate Manager).

#### DNS records summary

| What                | Type  | Name                     | Value                          |
| ------------------- | ----- | ------------------------ | ------------------------------ |
| Host Header         | CNAME | `email.yourdomain.co.nz` | `custom.engage.ubiquity.co.nz` |
| SSL/TLS Certificate | CNAME | Provided by UbiQuity     | Provided by UbiQuity           |

Custom host headers are configured entirely by the UbiQuity team once the DNS records are in place. Contact UbiQuity to get started.

***

### Single Sign-On (SSO)

UbiQuity supports Single Sign-On via OpenID Connect (OIDC), allowing your users to log in to UbiQuity using your organisation's existing identity provider.

SSO configuration requires setup on both your side and UbiQuity's side. Contact UbiQuity to discuss enabling SSO for your account.

***

### Alternate Contact Service Messaging (ACSM)

Alternate Contact Service Messaging allows you to send service messages to a contact other than the one who generated the interaction. This is useful in situations where a third party needs to receive communications on behalf of the original contact.

A common example is group accommodation bookings — the person managing the booking would typically receive all service messages, rather than each individual whose booking is being managed. ACSM allows those messages to be sent directly to the relevant individual instead.

ACSM can send to either an email address for a database contact or a relevant transactional row. Once enabled for your account, an additional **To** field appears on the Content and Preview screen of the email creation process. This field defines the alternate contact the message will be sent to, linked to the original contact via a secondary email field in the database or an additional transactional row.

ACSM requires setup by the UbiQuity team. Contact UbiQuity if you would like to enable this for your account.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ubiquity.co.nz/account-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
