Set up the organisation and users before changing your domain's mail routing. Zoho Workplace combines business email with the applications included in your edition. Your Nabtech order determines the purchased service, while Zoho's administration console supplies the exact domain and connection settings.
IN THIS ARTICLE
01 What you need
Have your organisation's administrator account, a user list and access to the domain's authoritative DNS provider. Decide which people need licensed mailboxes and which addresses should be aliases or groups. If another provider currently hosts your email, schedule migration and keep that service active during the transition.
- Open the service or activation instructions supplied with your Nabtech order. Confirm the organisation and domain before creating users or accepting an invitation.
- Add the domain in the Zoho administration console and complete a supported ownership-verification method. Copy the unique verification value shown for your organisation; do not reuse an example token.
- Create the required users and any approved groups or aliases. Apply appropriate administrator roles so ordinary staff do not receive unnecessary control of the organisation.
- Open a test mailbox and confirm it works. Domain verification alone does not mean incoming mail has been moved.
- When ready to switch, publish the MX records shown for your Zoho organisation. Zoho data-centre settings can differ, so use those values rather than a generic list copied from another guide.
- Add the required sending-authentication records and verify them in the console. Send and receive test messages with an external account before onboarding all staff.
02 Introduce the wider workspace
Check which document, storage, chat and meeting applications your edition includes. Set organisation timezone and sharing defaults. Start with a small collaboration test rather than importing every file into an unfamiliar shared folder structure.
What should I check when Zoho Workplace setup does not complete?
If domain verification fails, confirm the public record is at the authoritative DNS provider and that the hostname has not been duplicated. If outbound mail works but inbound mail does not, review MX records and recipient creation. If an application or storage allocation differs from expectations, check the edition on your order.
Use the account's security controls and recovery options before handing out access. Keep administrator recovery details available to the business, with a second authorised recovery route where supported.