Google Workspace Setup Guide for Indian Businesses — Step by Step

Getting Google Workspace running is straightforward at the surface — sign up, verify your domain, create accounts. But getting it running correctly requires several additional configuration steps that most businesses miss when setting up independently.

Missing these steps results in real problems: outbound emails landing in spam, phishing attacks that spoof your domain, deliverability issues with client communications and security gaps that put business data at risk.

This guide covers every step of a correct Google Workspace setup for Indian businesses — from the initial sign-up through domain verification, MX records, email security (SPF, DKIM, DMARC), user management and admin console basics.

Before You Begin

You will need the following before starting setup:

• Access to your domain's DNS settings (through your domain registrar — GoDaddy, BigRock, Namecheap, Google Domains, or your hosting provider's DNS panel)
• The login credentials for your existing email system (if migrating)
• A list of all users who need Google Workspace accounts
• Your business's GST number (if purchasing through an Indian reseller for GST invoicing)

If you are purchasing Google Workspace through Cloudfy Systems, all of the steps in this guide are handled for you as part of the setup. This guide is useful if you want to understand what is being configured and why.

Step 1 — Choose the Right Plan

Google Workspace offers three main plans for businesses in India:

Business Starter is the right starting point for most small Indian businesses — professional email, Drive and Meet at the lowest per-user cost.

Business Standard is the better choice if your team holds client video calls that need to be recorded, or if you regularly share large files that will fill a 30 GB mailbox.

Business Plus suits organisations with compliance requirements, larger teams or a need for advanced audit and eDiscovery features.

You can upgrade plans at any time. Start on the plan that fits your current team and scale up as needed.

Step 2 — Sign Up and Create Your Admin Account

Go to workspace.google.com and begin the sign-up process. You will be asked for:

• Your business name
• The number of users
• Your existing email address (for account recovery)
• Your domain name (the @yourcompany.com you want to use)

At the end of this flow, you create the first admin account — typically the business owner or IT manager. This account has full control over the Google Workspace environment.

Important: if you purchase through Cloudfy Systems, you receive an invitation to your admin account rather than creating it through Google's public sign-up flow. The process is the same from that point onward.

Step 3 — Verify Domain Ownership

Before Google routes your email or allows you to create user accounts under your domain, you must prove that you own the domain.

Google provides a TXT record — a string of characters that looks like google-site-verification=xxxxxxxxxxxxxxxxxxx — which you add to your domain's DNS.

How to add the TXT record:

1. Log in to your domain registrar or DNS provider
2. Navigate to DNS management or DNS records
3. Add a new TXT record with:
   • Host / Name: @ (or leave blank, representing the root domain)
   • Value: the verification string provided by Google
   • TTL: 3600 (or default)
4. Save the record
5. Return to the Google Workspace setup screen and click Verify

DNS changes typically propagate within a few minutes, though Google may take up to 24 hours to detect the record. In practice, verification usually completes within 15–30 minutes for most Indian registrars.

Your domain is now verified. Do not delete this TXT record — Google uses it for ongoing verification.

Step 4 — Create User Accounts

With your domain verified, create accounts for every person in your organisation from the Google Admin console at admin.google.com.

For each user, you set:

• First and last name
• Primary email address (name@yourcompany.com)
• Temporary password (users change this on first login)
• Organisational unit if you have departments

Users can be created one at a time, or bulk-imported from a CSV file if you have a large team. The CSV format requires name, email address and password fields.

At this point, accounts exist but email is not yet routing to Google — your MX records still point to your old provider. Users cannot yet receive email at their new Google addresses.

Step 5 — Configure MX Records

MX (Mail Exchange) records tell the internet where to deliver email for your domain. To start receiving email in Google Workspace, you replace your existing MX records with Google's.

Delete all existing MX records first, then add the following five records:

How to add MX records:

In your DNS management panel, for each record above:

• Host / Name: @ (root domain)
• Type: MX
• Priority: as listed above
• Value: the MX server name
• TTL: 3600

After saving, DNS propagation takes anywhere from a few minutes to a few hours depending on your registrar and previous TTL values. Once propagated, all new email sent to @yourcompany.com addresses arrives in Google Workspace.

If you are migrating from an existing email system: do not change MX records until the background migration is at least 90% complete. See the migration guide for the correct sequencing.

Step 6 — Set Up SPF Record

SPF (Sender Policy Framework) is a DNS record that lists which mail servers are authorised to send email from your domain. Without SPF, emails sent from Google Workspace on behalf of your domain may be treated as suspicious by recipient mail servers.

For Google Workspace, the SPF record is:

v=spf1 include:_spf.google.com ~all

How to add it:

In your DNS panel, add a TXT record with:

• Host / Name: @ (root domain)
• Type: TXT
• Value: v=spf1 include:_spf.google.com ~all
• TTL: 3600

Important: A domain can only have one SPF record. If you already have an SPF record from a previous email provider, do not add a second one — modify the existing record to include Google. For example, if your existing record is v=spf1 include:zoho.com ~all, update it to v=spf1 include:_spf.google.com include:zoho.com ~all.

The ~all at the end means emails failing SPF are treated as suspicious (soft fail) rather than rejected outright (hard fail, which is -all). Starting with ~all is recommended during initial setup.

Step 7 — Set Up DKIM

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every email your domain sends. Recipient mail servers verify this signature to confirm the email genuinely came from your domain and was not tampered with in transit.

Generating your DKIM key in Google Admin:

1. Go to admin.google.com
2. Navigate to Apps > Google Workspace > Gmail
3. Click Authenticate email
4. Select your domain from the dropdown
5. Click Generate new record
6. Choose a DKIM key length of 2048 bits (more secure, recommended)
7. Google generates a TXT record — copy the entire value

Publishing the DKIM record in DNS:

Add a TXT record in your DNS panel with:

• Host / Name: google._domainkey (exactly this — do not change it)
• Type: TXT
• Value: the long string generated by Google (starts with v=DKIM1; k=rsa; p=...)
• TTL: 3600

After the DNS record propagates (typically 30–60 minutes), return to the Google Admin DKIM screen and click Start authentication. Google verifies the record and begins signing outbound emails.

DKIM is one of the most important email security configurations. Without it, your emails can be spoofed and will score lower on spam filters at major mail providers.

Step 8 — Set Up DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. It tells recipient mail servers what to do with emails from your domain that fail authentication — and sends you reports so you can monitor your domain's email health.

Starting DMARC policy:

v=DMARC1; p=none; rua=mailto:postmaster@yourdomain.com

Replace postmaster@yourdomain.com with any email address in your domain where you want to receive reports.

How to add it:

Add a TXT record in DNS with:

• Host / Name: _dmarc
• Type: TXT
• Value: the DMARC policy string above
• TTL: 3600

What p=none means: emails that fail authentication are delivered normally, but you receive weekly aggregate reports showing which servers are sending email claiming to be from your domain. This is the correct starting point — you review the reports, confirm all your legitimate sending sources are authenticated, then tighten the policy.

The progression over time:

1. Start: p=none — monitor only, no enforcement
2. After 2–4 weeks of clean reports: p=quarantine — failing emails go to spam
3. After 2–4 weeks of clean quarantine reports: p=reject — failing emails are rejected outright

p=reject is the strongest protection against domain spoofing. It tells every recipient mail server in the world to refuse any email claiming to be from your domain that cannot pass SPF and DKIM verification. Reaching this policy means your domain cannot be effectively spoofed in phishing attacks.

Step 9 — Verify All DNS Records

After configuring MX, SPF, DKIM and DMARC, verify all records are correctly published before proceeding.

You can use Google's own MX Toolbox or any DNS lookup tool to check each record type. Specifically verify:

• MX records return Google's five servers at the correct priorities
• TXT record on @ contains your SPF policy
• TXT record on google._domainkey contains your DKIM key
• TXT record on _dmarc contains your DMARC policy
• DKIM authentication shows as Active in Google Admin

Cloudfy Systems runs a full DNS verification check as a standard step in every deployment. Any misconfiguration is caught and corrected before the setup is signed off.

Step 10 — Configure Gmail Settings in Admin Console

With email routing and authentication configured, a few additional Gmail settings are worth setting from the Admin console during initial setup.

Default language and time zone: Set to English (India) and IST (UTC+5:30) so all users see correct timestamps.

Email routing: If you have specific routing requirements — for example, copying all email sent to info@yourdomain.com to multiple users — configure this under Apps > Google Workspace > Gmail > Routing.

Spam settings: Google's spam filtering works out of the box, but you can whitelist specific senders or domains that your team always needs to receive from, even if they occasionally trigger spam signals.

Email retention: Under Rules, you can set a retention policy that keeps deleted emails for a defined period before permanent deletion. Useful for businesses with compliance requirements.

Step 11 — Set Up Mobile Access

Google Workspace works on every phone out of the box via the Gmail, Drive, Meet and Calendar apps. Share the following with your team for quick mobile setup:

On Android:

• Gmail app is typically pre-installed
• Go to Settings > Add Account > Google
• Sign in with the new @yourcompany.com address

On iPhone/iPad:

• Download Gmail from the App Store if not present
• Tap Add Account > Google
• Sign in with the new @yourcompany.com address

For businesses that need device management — the ability to remotely wipe a device, enforce screen lock policies or block certain apps — this is configured under Devices in the Admin console.

Step 12 — Admin Console Overview

The Google Admin console at admin.google.com is where you manage everything about your Google Workspace environment. Key areas to know:

Users — Add, remove, suspend or restore users. Reset passwords. Assign admin roles. Move users between organisational units.

Groups — Create mailing lists and shared inboxes. A group like team@yourcompany.com can deliver to five people's inboxes simultaneously.

Devices — Manage and monitor devices your users access Workspace from. Enforce security policies.

Apps — Configure Gmail settings, Drive sharing policies, Meet recording policies and access to third-party apps.

Reports — Usage reports showing email volume, active users, storage consumption and security events.

Security — Two-step verification settings, password policies, suspicious login alerts and data access policies.

The admin console is designed to be navigable without deep technical knowledge. Most day-to-day tasks — adding a user, resetting a password, creating a group — take under two minutes.

Common Setup Mistakes and How to Avoid Them

Adding a second SPF record instead of modifying the existing one. A domain with two SPF records fails SPF validation for all emails. Always check for an existing SPF record before adding.

Publishing DKIM key before it propagates. If you click Start Authentication in Google Admin before the DNS record has propagated, DKIM activation fails. Wait 30–60 minutes after publishing the DNS record.

Setting MX records to Google before migration is complete. If you are migrating from an existing provider, changing MX records too early splits email delivery between two systems. Always complete migration first.

Using p=reject DMARC immediately without monitoring. Starting with p=reject without a monitoring period can cause legitimate emails (from third-party senders like CRMs, invoicing tools or marketing platforms) to be rejected if they are not yet authenticated. Always start with p=none.

Leaving the DKIM selector as the default on old records. If your domain previously used a different email provider with DKIM, there may be a stale DKIM record in DNS. Old records from previous providers do not cause problems, but it is good practice to remove them during setup.

What Cloudfy Systems Handles for You

Every step in this guide is handled by Cloudfy Systems as part of every Google Workspace deployment in India. You do not need to navigate DNS panels, generate DKIM keys or configure DMARC policies yourself.

Cloudfy Systems configures:

• Domain verification
• User account creation
• MX record setup
• SPF, DKIM and DMARC configuration and verification
• Gmail admin settings
• Mobile setup briefing for your team
• Email migration from your previous provider (if applicable)

All at no additional charge beyond the Google Workspace subscription.

Frequently Asked Questions

How long does Google Workspace setup take from start to finish?

Domain verification and admin setup take 24–48 hours. If email migration from an existing provider is included, the full process takes 3–5 business days for most businesses. Your existing email continues to function throughout.

Do I need a technical background to manage Google Workspace after setup?

No. Day-to-day admin tasks — adding users, resetting passwords, creating groups — are straightforward from the admin console. Cloudfy Systems also provides ongoing support for admin tasks if needed.

What is the difference between SPF, DKIM and DMARC?

SPF lists which servers can send email from your domain. DKIM adds a verifiable signature to every outbound email. DMARC tells receiving mail servers what to do when an email fails SPF or DKIM. All three work together and all three should be configured. Skipping any one of them leaves a gap.

Can I set up Google Workspace on a domain I already use for a website?

Yes. Your website's DNS records (A record, CNAME) are unaffected by the MX, SPF, DKIM and DMARC records added for Google Workspace. Your website continues to work exactly as before.

What happens if I add the wrong MX records?

If MX records point to the wrong server, new inbound email stops being delivered. This is why Cloudfy Systems verifies MX records immediately after setup before signing off. If you are setting up independently, verify using a DNS lookup tool before considering setup complete.

Can Google Workspace be set up for a domain registered with any Indian registrar?

Yes. Google Workspace works with any domain where you have DNS management access — regardless of whether it was registered with GoDaddy, BigRock, Namecheap, Hostinger, ResellerClub or any other registrar used in India.

Cloudfy Systems is an authorised Google Workspace Partner in India. For businesses that want a correctly configured Google Workspace deployment without handling DNS records themselves, contact us at connect@cloudfysystems.com or call +91 97600 50555.