alternate_email

Workspace & Email.

Google Workspace, Microsoft 365 for Business and Zoho Mail, set up properly. Email on your own domain for staff and students, one sign-in for every app, online classes nobody can crash, and people trained to spot the phishing mail that gets past the filter.

workspaces

Google Workspace, Microsoft 365 & Zoho Mail

Licensing, tenant setup and migration from whatever you are on now, including shared mailboxes, calendars and drives. We move the mail across without losing history and without a day of downtime, and we will tell you honestly which of the three suits your budget and your team.

Domain & DNS Mailbox Migration Shared Drives Licence Management

rocket_launch

Moving your team over?

Tell us your headcount and current setup for a migration plan.

Contact Sales

badge

Student Email Accounts

Every student on an institution-owned address, provisioned in bulk from your existing roll and rolled forward each academic year.

cast_for_education

Online Classes Nobody Can Crash

Because every student has an institutional account, class meetings can admit your own people automatically from the lobby and hold everyone else outside it. A leaked link stops being a way in, and every participant is in the room under their real, named account, so if somebody disrupts a class, there is no question who it was.

key

Single Sign-On

One identity across Workspace, Microsoft 365 and your other SaaS, with SAML, multi-factor authentication and conditional access.

mark_email_read

Email Deliverability

SPF, DKIM and DMARC configured and enforced, so your mail lands in the inbox and nobody can send as your domain.

devices

Device & Access Control

Managed enrolment, joiner and leaver workflows, and remote wipe for the laptop that walks out of the building.

phishing

Phishing Simulation

Scheduled, consent-based simulated phishing campaigns against your own staff, reported by department so you know where the risk actually sits.

school

Staff Security Awareness Training

Short, practical sessions for non-technical staff on passwords, business email compromise, invoice fraud and what to do in the ten minutes after somebody clicks. Delivered on site or remotely, with a follow-up simulation to show whether it stuck.

What is involved

Company email is the easy part.

Almost anyone can point a domain at Google Workspace and create a dozen mailboxes. What takes longer, and is what actually goes wrong later, is the part underneath: who can reach what, what happens when somebody leaves, whether your mail is being delivered or quietly spam-foldered, whether a stranger can walk into your online class, and whether your staff can tell a real invoice from a forged one. That whole picture is the job.

Google Workspace, Microsoft 365 or Zoho Mail: how to choose

If your team already lives in Excel, uses Teams, or you have Windows laptops you want centrally managed, Microsoft 365 for Business is usually the shorter path, since Entra ID and Intune come with it and you will want both eventually. If your people work mostly in a browser, collaborate heavily on documents at the same time, and nobody is attached to desktop Office, Google Workspace is simpler to run and simpler to explain to staff. Zoho Mail is the one worth taking seriously on cost: it is materially cheaper per user than either, it does the mail part properly, and for an organisation whose real requirement is professional addresses on its own domain rather than a full collaboration suite, it is often the honest recommendation. It is also an Indian company with Indian data centres, which some organisations prefer on data-residency grounds under the DPDP Act. We will tell you which way we would go for your situation and why, including when the answer is that any of the three would do and you should simply take the cheapest.

Student email, and why a campus should not run on personal Gmail

Most institutions arrive at this having quietly standardised on whatever students already had: a personal Gmail address, often created in a hurry, frequently shared with a sibling, occasionally something a prospective employer would rather not see on a CV. The costs are real even when they are invisible. Nobody can tell whether a submission genuinely came from the student who owns it, staff cannot circulate anything sensitive with confidence, there is no way to reach the cohort reliably, and when a student leaves there is no account to close because the institution never owned one. Institution-owned student addresses fix all of that at once, and both Google Workspace for Education and Microsoft 365 Education have tiers that cost qualifying institutions nothing or very little for the core accounts, which usually surprises people, and is the single most common reason this gets postponed for years longer than it needed to be.

Provisioning a whole cohort without typing it in twice

Creating four hundred accounts by hand is how this becomes a fortnight of somebody’s life. We provision in bulk from the roll you already have, and where the institution runs Vybe ERP, from the student records that are already in it, so the address is created at admission rather than as a separate administrative errand months later. Accounts are organised by year and by department, which is what makes it possible to mail one batch or restrict a resource to one course without maintaining a distribution list by hand. Each academic year the structure rolls forward: incoming students provisioned, existing students moved up, and graduating students moved to whatever the institution’s policy actually is, whether that is an alumni address, a period of read-only access, or a clean suspension. The point of writing that policy down is that it stops being a decision somebody has to make individually, four hundred times.

Online classes that do not get crashed

Remote and hybrid teaching has a specific failure mode that has nothing to do with bandwidth: someone who is not in the class gets hold of the link and joins to disrupt it. The link travels, because it only takes one student to forward it, and once an uninvited participant is in a session with forty teenagers the lesson is effectively over. Admitting people manually is not a fix either, because it makes the teacher a doorman for the first ten minutes of every period. Institutional student accounts solve it properly. Meetings are configured so that signed-in members of your own domain are admitted automatically from the lobby, while anyone outside it is held there and never reaches the room. The leaked link stops being a way in, because possession of the link is no longer what grants entry.

Accountability, which is the part that actually changes behaviour

The other half of the problem is anonymity. A participant who joined as "Guest" or under an invented name can disrupt a session and simply rejoin under a different one, and there is nothing for the institution to act on afterwards. When every participant is in the room under a named, institution-owned account, that stops. Each join is attributable, the attendance record is a genuine record rather than a list of nicknames, and if somebody does cause a problem the follow-up is a straightforward disciplinary matter instead of an investigation. In practice the deterrent does most of the work: the incidents largely stop once students understand the room knows exactly who they are. We also set up recording and retention in line with whatever the institution has decided about consent and storage, rather than leaving each teacher to improvise it.

Email on your own domain, set up so it gets delivered

Mail from a new domain is treated with suspicion by default, and the fix is three DNS records that are widely skipped. SPF states which servers may send as you. DKIM signs each message so it cannot be altered in transit. DMARC ties the two together and tells receiving servers what to do when a message fails. Crucially, it also sends you reports on who is attempting to send as your domain. We configure all three and move DMARC to enforcement once the reports are clean, rather than leaving it permanently on the monitoring setting that protects nobody.

Migrating without losing the last six years of mail

The mail history is usually the thing people are most nervous about, and reasonably so: for a lot of businesses the mailbox is the filing system. We migrate existing mail, contacts and calendars across with folder structure intact, run the new tenant in parallel while DNS propagates, and cut over once delivery is confirmed working in both directions. Shared mailboxes such as accounts@ or info@ get set up as shared mailboxes rather than as a personal account four people share a password to, which is where most of the access problems start.

Single sign-on: one identity, everywhere

Single sign-on means your staff have one account, protected by one strong authentication step, that gets them into Workspace or Microsoft 365 and into the other SaaS tools you pay for (your ERP, your accounting package, your CRM) over SAML or OIDC. The benefit people notice is fewer passwords. The benefit that matters is that access is now centralised: multi-factor authentication is enforced in one place, conditional access rules can require a managed device or block sign-ins from countries you do not operate in, and when somebody leaves, disabling one account closes every door at once instead of leaving a forgotten login live for two years.

Joiners, leavers and the accounts nobody closed

Most organisations have a decent process for creating accounts and no process at all for removing them, because creating one is somebody’s urgent problem and removing one is nobody’s. We set up the offboarding side properly: access revoked on the last day, the mailbox converted or delegated to a manager so the work does not vanish with the person, and company data removed from personal devices. Device enrolment through Intune or Google endpoint management makes remote wipe possible for the laptop that gets lost or the phone that does not come back.

Phishing simulation, run against your own staff

A simulated phishing campaign sends your people a realistic but harmless lure and records who clicks, who submits credentials and who reports it. It is done with the organisation’s authorisation and it is not a trap laid for individuals. The useful output is the pattern, broken down by department and by role, showing where the real exposure sits. Finance and reception are usually the answer, because they are the two functions whose job is to open attachments from strangers. Campaigns are run on a schedule rather than once, because the number that matters is whether the click rate falls over the year, not what it was in January.

Training that is worth an hour of your staff’s time

Security awareness training fails when it is a compliance video nobody watches. Ours is short, in-person or live remote, and built around the attacks that actually reach Indian businesses: business email compromise, where an attacker impersonates a director and asks for an urgent transfer; invoice fraud, where a genuine supplier’s bank details are silently changed; credential harvesting pages that look exactly like your own login screen. We also cover the part most training skips, which is what to do in the ten minutes after somebody has clicked, because the difference between an incident and a breach is usually how fast it was reported, and staff who expect to be blamed do not report.

Why this sits next to our security work

Workspace setup is often treated as an IT admin errand and security as a separate, later purchase. In practice the identity layer is the security perimeter for most small and mid-size organisations: the overwhelming majority of intrusions begin with a valid credential rather than an exploit. The same team that configures your tenant also does our penetration testing and managed SecOps, so the configuration is built by people who spend the rest of their week attacking configurations.

Partner programmes & startup support

Programmes we are enrolled in and a grant we received. None of these is an accreditation, a certification or a vendor endorsement of our work.

Reseller programme

Ingram Micro

Distribution partner

Registered partner. How we source and license the hardware and software we resell.
Vendor programme

AWS Partner Network

Registered partner

Entry tier. Gives us Amazon Web Services support channels for the infrastructure we run.
Vendor programme

Google Cloud Partner Advantage

Programme member

Covers Google Cloud Platform and Google Workspace deployments we set up for customers.
Startup support

Microsoft for Startups

Azure credits grant

A credits grant awarded to us as a startup. Not a partnership, and not a Microsoft endorsement.

FAQ

Questions, answered.

Should we use Google Workspace, Microsoft 365 or Zoho Mail?

Microsoft 365 for Business usually wins if your team already relies on desktop Office and Teams, or if you have Windows laptops to manage centrally, since Entra ID and Intune come with it. Google Workspace is usually simpler if your people work mainly in a browser and collaborate live on documents. Zoho Mail is the value option and a genuinely good one: noticeably cheaper per user, Indian-owned with Indian data centres if data residency matters to you, and the right answer when what you actually need is professional email on your own domain rather than a full collaboration suite. We will recommend one for your specific setup and explain why.

Do you set up Zoho Mail?

Yes. Zoho Mail is one of the three suites we deploy, and we handle it the same way as the others: domain verification, DNS, mailbox creation, migration of your existing mail, and SPF, DKIM and DMARC configured properly. It is often what we recommend to smaller teams and cost-sensitive institutions, since the per-user cost is well below Google Workspace or Microsoft 365 for what is, for many organisations, the same practical outcome.

Can you migrate our existing email without losing anything?

Yes. We migrate existing mail, contacts and calendars with folder structure intact, run the new tenant in parallel while DNS propagates, and cut over only once delivery is confirmed working both ways. Shared addresses like accounts@ or info@ are set up as proper shared mailboxes rather than a personal account with a shared password. Migrations between Google Workspace, Microsoft 365 and Zoho in any direction are all routine.

Can you set up email accounts for students, not just staff?

Yes, and it is a large part of what we do. Every student gets an institution-owned address on your domain, provisioned in bulk from your existing roll, or created automatically at admission where the institution runs Vybe ERP, and organised by year and department so you can mail a single batch without maintaining lists by hand. Each academic year the structure rolls forward, with graduating students moved to whatever your policy says: an alumni address, read-only access, or suspension. Both Google Workspace for Education and Microsoft 365 Education have tiers that cost qualifying institutions nothing or very little for the core student accounts.

How do you stop strangers joining our online classes?

Once students have institutional accounts, class meetings can be configured to admit signed-in members of your own domain automatically from the lobby and hold everybody else outside it. A leaked link stops being a way in, because having the link is no longer what grants entry, and the teacher is not stuck admitting forty people by hand at the start of every period.

What if a student disrupts an online class?

Because every participant joins under a named, institution-owned account rather than as an anonymous guest, disruption is attributable. Nobody can misbehave under an invented name and rejoin under another one, the attendance record is a real record, and the follow-up is an ordinary disciplinary matter rather than an investigation. In practice most of the benefit is deterrence. The incidents largely stop once students know the room can identify everyone in it.

What is SPF, DKIM and DMARC, and do we need all three?

They are the three DNS records that decide whether your mail reaches the inbox and whether anyone else can send mail pretending to be you. SPF lists which servers may send as your domain, DKIM cryptographically signs each message, and DMARC tells receiving servers what to do when a message fails either check, and reports attempted impersonation back to you. Yes, you need all three, and DMARC needs to be moved to enforcement rather than left on monitoring.

What does single sign-on actually give us?

One account per employee, protected by one multi-factor step, that signs them into Workspace or Microsoft 365 and into your other SaaS tools over SAML or OIDC. It centralises access control: MFA is enforced in one place, conditional access can require a managed device or block sign-ins from countries you do not operate in, and disabling one account when somebody leaves closes every door at once.

What is a phishing simulation and is it safe to run on our staff?

It is an authorised, harmless test: we send your employees a realistic phishing lure and record who clicks, who submits credentials and who reports it. Nothing is installed and no real credentials are captured. It is run with the organisation’s consent and reported as departmental patterns rather than as a list of individuals to punish. The point is to find where training is needed, and staff who expect to be blamed stop reporting real incidents.

What does the staff security training cover?

Short, practical, live sessions for non-technical staff on the attacks that actually arrive: business email compromise, invoice fraud where a supplier’s bank details are quietly changed, credential-harvesting pages that copy your own login screen, and password and MFA hygiene. We also cover what to do in the first ten minutes after somebody clicks, since how fast an incident is reported usually decides whether it becomes a breach.

How do we get started?

Email sales@vybe.net.in with your headcount, your domain and what you are running today, and we will come back with a migration plan and a quote.