9. Steps 15–17 — First-time settings in the Admin Console¶
The first-time settings at a glance (Steps 15–17 below walk through them):
# |
Where |
What |
Why |
|---|---|---|---|
1 |
Admin → System → Mail |
Enter your company’s SMTP server (host, port, user, password, sender address) and send a test mail. |
Invitations, “forgot password” and notifications are sent by email. Without it, new users never receive their password. |
2 |
Admin → Identity → Users |
Add user for each person (or Groups / Directory Import for many). |
Each user receives an email with a temporary password. |
3 |
Admin → Products → Entitlements |
Check that QuantaDrive / QuantaGrid are enabled and the user limit is right. |
Controls which products users see. |
4 |
Admin → Security → Session Policy |
Adjust session length and idle time if needed (default 8 hours / 30 minutes). |
|
5 |
Admin → Authentication → Product Login |
Leave on Local credentials, or choose an SSO provider (section 10). |
|
6 |
QuantaGrid only: Admin → QuantaGrid → Storage Access |
Choose how users reach your cloud storage: Static — on AWS this is the stack’s own IAM role (no access key is entered or accepted; add other AWS accounts as role connections), on Azure a service principal — or Step-up SSO (users sign in with their own AWS / Azure account). |
QuantaGrid browses your own S3 / Azure storage. |
7 |
Check only: Admin → System → Network → Certificates |
Every service shows Installed and in use. Nothing to do: the install created the certificates (Appendix B). |
The services inside QuantaCloud talk to each other over HTTPS, with certificates. The page warns 30 days before one expires. |
Step 15 — Set up mail¶
Sign in, click the app menu (grid icon, top right) → Admin Console.
In the left menu: System → Mail → Edit.
Fill in what your mail provider gave you:
Field
Example
Server address
smtp.<your-domain>Port
587(or465)Encryption
STARTTLS for port 587, SSL / TLS for port 465
Authentication required
ticked (almost every provider)
Username
the mailbox user, often the full address
Password
that mailbox’s password or app password
From address
noreply@<your-domain>From name
QuantaCloudReply-To
optional
Click Save. QuantaCloud connects to the server first: if it cannot, it says why (for example “rejected the connection”) and saves nothing. Correct the field it names and save again.
Under Send a test email, enter your own address and send. Check your inbox (and the spam folder).
Warning
Test email in Spam? That is expected at this point — not a QuantaCloud fault. Until your domain has the DKIM, SPF and DMARC records below, Gmail and Outlook cannot confirm the mail is really from your domain and put it in Spam. Mail settings are correct if the email arrived at all. Add the records (next section), wait up to an hour, send the test again: it then lands in the Inbox. Do this before you invite users, or their invitation and password mails go to Spam too.
Keep mail out of spam: add the mail records in Route 53¶
Without these three records, Gmail and Outlook cannot tell that QuantaCloud’s mail really comes from your domain, and put it in Spam. Add them once, right after your domain’s hosted zone exists (Step 2 / Step 13), before you invite users.
Get the records from your mail provider. In its console (ZeptoMail, Microsoft 365, Google Workspace, Amazon SES, …) open the page for your sending domain (e.g. Domains →
<your-domain>→ DNS records). It lists:DKIM: a TXT (or CNAME) record whose name ends in
._domainkey, e.g.14124326._domainkey, with a long value startingk=rsa; p=….SPF / bounce: either a TXT record
v=spf1 include:… ~allon the domain itself, or (ZeptoMail) a CNAME such asbounce-zem→cluster89.zeptomail.in.
Add each record in Route 53: Route 53 → Hosted zones → your domain → Create record:
Record name: only the part before your domain, exactly as the provider shows it (e.g.
14124326._domainkey,bounce-zem). For a record on the domain itself, leave it empty.Record type: TXT or CNAME, as the provider says.
Value: paste it exactly. A TXT value goes in double quotes, all on one line (
"k=rsa; p=MIIB…").Create records.
Add DMARC (one record, same page): Record name
_dmarc, type TXT, value"v=DMARC1; p=none; adkim=r; aspf=r"→ Create records.Only one SPF record per domain. If the domain already has a TXT record starting
v=spf1, add the provider’sinclude:…to that record instead of creating a second one — two SPF records make every check fail.Wait 5–60 minutes, then click Verify next to each record in your mail provider’s console until all show Verified.
Check it worked: send the test email (step 5 above) to a Gmail address → open it → ⋮ → Show original. It must say SPF: PASS, DKIM: PASS and DMARC: PASS, and the mail must be in the Inbox.
Error |
Meaning and fix |
|---|---|
Test email lands in Spam |
The DKIM / SPF / DMARC records are missing or not verified yet. Add them (steps 1–3) and wait. |
Show original says DKIM: FAIL or neutral |
The DKIM value was changed when pasted (line break, missing quote, missing part). Copy it again in one piece. |
Show original says SPF: PERMERROR |
The domain has two |
The provider says Not verified after an hour |
The record name was typed with the domain
twice (e.g.
|
Next → Step 16 — add your users.
Step 16 — Add users¶
Admin Console → Identity → Users → Add user.
Fill in first name, last name, Email, a username, the Role (User for most people, Admin for administrators) and an initial Password.
Click Add user. The person receives an email with their sign-in details (this needs mail from Step 15) and must set a new password at first sign-in.
Repeat for each person, or use Groups / directory import for many users.
Next → Step 17 — the remaining rows of the table at the top of this chapter (entitlements, session policy, product login, QuantaGrid storage).
Step 17 — Remaining first-time settings¶
Work through rows 3–7 of the table at the top of this chapter. Row 7 (mTLS) is only a check: the install already switched it on.
Next → Step 18 — check that everything works (section 10 first for the features you use).