Related ToolsZoho OneZoho CrmZoho ProjectsZoho BooksZoho Desk

Zoho Connect Setup Guide: Build a Team Network 2026

Published May 8, 2026
Updated May 7, 2026
Read Time 19 min read
Author George Mustoe
Beginner Setup
i

This post contains affiliate links. I may earn a commission if you purchase through these links, at no extra cost to you.

Zoho Connect is an internal team network that combines the social-feed energy of a workplace messenger with the structured layers of a modern intranet. Instead of forcing your team to choose between a chat tool, a knowledge base, and a task tracker, Connect bundles all three into a single private network behind your company login.

The product sits in an interesting category. It is not a direct Slack replacement because the rhythm is different. Slack is built around fast-flowing channels, while Zoho Connect is built around persistent feeds, groups, and pages that retain context for weeks or months. It is also not a pure intranet, because the activity feed invites real conversation rather than only document publishing. Teams that want both ends of that spectrum without paying for two separate platforms tend to find Connect a strong fit. The official Zoho Connect product page covers the full feature catalog if you want a vendor reference.

This guide walks through a clean 20-minute setup for a team of 10 to 50 people. You will pick a plan, brand the network, set up your initial group structure, invite teammates, build a starter knowledge base, configure boards, connect a few outside tools, and run your first town hall or announcement. One pricing nuance to know upfront: Zoho does not display Zoho Connect prices in USD on its public pricing page in the same way it does for Zoho CRM or Zoho Projects. The actual per-user cost depends on your region and currency, so this guide focuses on tier features and points you to the official pricing page for live numbers.

Zoho Connect pricing tiers - Starter, Enterprise, Ultimate

What Zoho Connect Actually Does

Before the setup steps, it helps to understand the building blocks because the labels are not always self-explanatory.

  • Feeds: the primary activity stream. Posts, announcements, polls, and comments show up in the feed of the relevant group, and a home feed combines updates across everything you follow.
  • Groups: persistent containers for a team, department, or project, each with its own feed, members, and permission rules.
  • Channels: real-time chat rooms inside a group, designed for quick conversation that does not need to live as a permanent feed post.
  • Manuals: the wiki-style knowledge base. Organized into chapters and pages, with attachments and version history. The best place for onboarding documents, policies, and runbooks.
  • Boards: kanban-style task trackers attached to a group. Cards, due dates, assignments, custom statuses. Lighter than Zoho Projects but perfect for team-level task tracking that lives next to the conversation.
  • Forums: threaded discussion areas for longer questions, debates, and decisions you want to be searchable later.
  • Polls, announcements, and town halls: announcements are pinned high-visibility posts; polls collect quick feedback; town halls (Enterprise tier and above) are scheduled live broadcast events with Q&A and recording.

Which Zoho Connect Plan Should You Choose?

Zoho Connect has four tiers (Free, Starter, Enterprise, Ultimate), and the user minimums on each tier matter as much as the feature differences.

The Free plan is best understood as a post-trial fallback rather than a recommended starting point. The feature set is limited and most of the value of Connect (manuals, boards, integrations, branding) is constrained.

The Starter plan unlocks feeds, channels, announcements, polls, forums, 25 GB of file storage, 10-participant video conferencing, 10 boards, 10 groups, and integrations with 10 Zoho apps. The catch is the 25 paid user minimum. If your team has fewer than 25 people, Starter is not actually available to you. There is a 20 percent discount on annual billing.

The Enterprise plan is the practical floor for most small and mid-size teams. The minimum drops to 10 paid users, which is realistic for most departments. Enterprise adds town halls, surveys, external user access, the Zia Writing Assistant, unlimited groups and boards, 2 GB of file storage per user, 50-participant video conferencing, and custom domain support. Annual billing comes with the same 20 percent discount.

The Ultimate plan keeps the 10-user minimum and adds organizational charts, peer recognition workflows, gamification, live broadcast (the larger streaming version of town halls), sentiment analysis, custom roles, unlimited integrations, and 100-participant video conferencing. Ultimate is also included as part of the Zoho One bundle.

Zoho does not publish current USD prices on the Connect pricing page in the same format as other Zoho products, so check the official Zoho Connect pricing page for live numbers in your region before you commit. The tier comparison and user minimums above will not change.

For organizations already using Zoho CRM, Zoho Projects, Zoho Books, or any combination of Zoho apps, the math frequently favors Zoho One over standalone Connect Ultimate. Zoho One is available in two flavors:

  • All Employee plan: $45 per user per month monthly, or $37 per user per month on annual billing. Every employee in the company must be licensed.
  • Flexible User plan: $105 per user per month monthly, or $90 per user per month on annual billing. Only specific users need licenses.

Either Zoho One plan includes Connect Ultimate plus 50+ other Zoho applications, Zia AI features (covered in our Zoho AI / Zia overview guide), single sign-on, and mobile device management. For a 25-person team that already uses three or more Zoho apps, Zoho One usually wins on total cost compared to Connect Ultimate alongside separate licenses for the other apps. The latest pricing is on the Zoho One pricing page.

Start a 30-day free trial of Zoho One if you want to test the bundle including Connect Ultimate before committing.

Prerequisites for Zoho Connect Setup

Gather these before you start so you do not have to pause partway through.

  • A Zoho account with admin access. If your organization already uses any Zoho product, sign in with the existing admin account so Connect inherits your organization profile.
  • An admin email address (a shared mailbox or role-based address like admin@yourcompany.com is better than an individual employee account).
  • A CSV of team members with email addresses, separated by department or team if you can.
  • A clear network name and short URL slug (the subdomain naming reference covers conventions for memorable hostnames).
  • Optional: a custom domain you control (Enterprise tier and above) if you want the network to live at connect.yourcompany.com.
  • Optional: credentials for tools you want to integrate (Microsoft Teams, Asana, Google Calendar, Google Drive, Office 365, Zoho Cliq).
  • A logo file (PNG or SVG, square) and your brand color hex codes.

If you are migrating from Workplace from Meta or a SharePoint intranet, export documents into Word or PDF first. Connect supports file attachments inside Manuals, which is the easiest migration path.

Step 1: Sign Up and Create Your Network

Visit the Zoho Connect homepage and click “Get Started.” You can sign up with a fresh Zoho account or use an existing one. If your organization already uses Zoho CRM or Zoho Projects, use that account so the new Connect network is created inside the same organization tenant.

During signup, choose your plan. If you are unsure, start with the Enterprise free trial because it gives you access to the full feature set including town halls, custom domain, and Zia (covered in our Zoho AI overview guide). You can downgrade or upgrade after the trial ends without losing your setup. Enter your organization name (shown in the header), a short network URL slug (becomes the subdomain on the default Zoho domain), and confirm the admin email address. You can add additional admins later.

After signup you land in an empty network. Do not start inviting people yet. The next two steps will make a much better first impression for your team.

Step 2: Brand Your Network

A blank, default-themed network signals “experimental tool” to your team. Five minutes of branding turns it into something that looks like a real internal product.

In admin settings, navigate to Network Settings > Branding. Upload your company logo (PNG or SVG, square aspect ratio, at least 200 pixels per side). Set your brand colors: Connect supports a primary color (used for buttons and active states) and a secondary color (used for accents).

If you are on Enterprise or Ultimate and want a custom domain, configure it now under Network Settings > Custom Domain. You will need DNS access to add a CNAME record pointing your chosen subdomain to a Zoho-provided endpoint. DNS propagation usually takes 15 to 60 minutes. If you also use Zoho Mail, our Zoho Mail custom domain setup guide covers DNS configuration in more depth.

Finally, write a short welcome message new members see when they accept their invitation. Keep it to two or three sentences: what this network is for, what they should do first, and who to contact with questions.

Step 3: Set Up Groups and Channels

This is the step where most networks go wrong. The temptation is to create a group for every conceivable team, project, and topic on day one. Resist this urge. Empty groups feel dead, and a network with twenty empty groups looks abandoned.

Start with three or four groups maximum:

  • All-Hands (public, all members auto-joined): the company-wide feed for announcements, kudos, and high-visibility updates.
  • Random or Watercooler (public, opt-in): the casual channel for non-work conversation. Every successful internal network has one.
  • One department-specific group per major function (Engineering, Sales, Operations): private to that team, used for daily work conversation and team-specific announcements.

Inside each group, create one or two channels for real-time chat. A typical Engineering group might have a #general channel and a #incidents channel. Do not pre-create dozens of channels. Let the team add channels as concrete needs emerge.

Set the group privacy correctly the first time. Public groups appear in the directory and any member can join. Private groups require an invite and are invisible to non-members. Once a group has activity in it, changing the privacy setting can confuse members.

For each group, designate at least one moderator other than yourself. This distributes the maintenance work and means the network does not depend on a single person - the bus factor applies to community moderation as much as to engineering.

Step 4: Invite Team Members and Configure Roles

Now invite your team. Navigate to Members > Invite and choose bulk invite. Paste in email addresses or upload a CSV. You can include the role assignment in the same step.

Connect has three primary roles:

  • Admin: full access to network settings, billing, branding, and all groups. Limit this to one or two people.
  • Moderator: can create groups, manage channel membership, pin posts, and moderate content. Assign moderators per major group.
  • Member: standard user. Can post, comment, react, and join public groups. This is the default for most invitees.

If you are on Enterprise or Ultimate, you can also invite external users (vendors, contractors, or clients who need access to specific groups but should not see the rest of the network). External users are licensed separately and have restricted permissions by default.

When invitations go out, members receive an email with a link to set their password and complete their profile. Send a separate company-wide email or chat message in parallel telling people to expect the Connect invitation. Adoption is much higher when people know the invitation is coming - covered in greater depth in HBR’s employee engagement research.

Step 5: Build Your First Manual (Knowledge Base)

Manuals are the Connect feature most teams underuse, and the one with the highest long-term return on setup time. A well-structured Manual becomes the institutional memory of your team and dramatically reduces “how do I” questions in chat.

Create your first Manual under Apps > Manuals > New Manual. Title it “Team Handbook” or “Onboarding Guide” (something general enough to grow into). A starter structure that works for most companies:

  • Welcome and How to Use This Network: one page explaining the network’s purpose and where to ask questions.
  • Onboarding: chapter with one page per onboarding step (accounts, mandatory training, who to meet).
  • Policies: HR policies, expense rules, time-off process.
  • Tools and Logins: tools your team uses with links and access instructions.
  • Frequently Asked Questions: one growing page where you add answers as questions come up in chat.

Manuals support rich formatting, embedded images, file attachments, and page version history. Pin a link to the Onboarding chapter in your All-Hands group so new joiners can find it without asking. The Shopify employee onboarding playbook is a useful reference for structuring an onboarding manual.

Step 6: Set Up Boards for Task Tracking

Boards give you a kanban-style task tracker attached to a group. They are not a replacement for a dedicated project management tool like Zoho Projects or Asana, but for lightweight team task tracking that lives next to the team conversation, they are excellent.

Create a board under your team’s group: Group > Apps > Boards > New Board. Pick a template (Kanban, Sprint, or Custom) or start from blank. A standard Kanban board has columns for To Do, In Progress, In Review, and Done.

For each card: set a clear, action-oriented title (“Update Q3 forecast” rather than “Q3 forecast”), assign at least one owner, set a due date even if approximate, and add a description with enough context that someone other than the assignee could pick up the work.

Boards work best for short-cycle work (one to two weeks per card). For larger initiatives that span months and need Gantt charts, dependencies, or time tracking, point your team to Zoho Projects and link the project from a Manual page. The Atlassian Kanban primer is a useful reference for setting up board workflows that scale.

Step 7: Configure Integrations

Integrations turn Connect from a standalone tool into a hub. Configure these under Network Settings > Integrations.

The most useful integrations for most teams:

  • Microsoft Teams: cross-post Connect announcements to a Teams channel, useful during the transition period when some teams still default to Teams.
  • Google Calendar / Office 365 Calendar: surface team events and town halls in members’ personal calendars.
  • Google Drive / OneDrive: attach documents to feed posts and Manual pages without re-uploading.
  • Asana: link Asana tasks to Connect feed posts so progress updates appear in the relevant group.
  • Zoho Cliq: tightly integrated chat product that complements Connect’s channels with persistent direct messaging.
  • Zoho CRM, Zoho Projects, Zoho Desk: the native Zoho integrations are the deepest. CRM contacts, project updates, and support tickets can all surface in Connect feeds.

The Starter tier limits you to 10 Zoho app integrations. Enterprise expands the integration catalog. Ultimate removes the limit entirely.

Configure two or three integrations on day one. Adding more later is easier when team members are asking for them than guessing at what they will use.

Step 8: Run Your First Town Hall (or Announcement)

The fastest way to make a new internal network feel real is to put real content in it on day one.

If you are on Enterprise or Ultimate, schedule a town hall for the end of week one. Town halls are scheduled live broadcast events with Q&A, polls, and recording. The Ultimate tier upgrades town halls to live broadcast capability for larger audiences. Town halls work because the recording stays in the network as a searchable artifact for anyone who could not attend.

If you are on Starter or Free (or simply do not want a live event yet), publish an announcement in your All-Hands group. Announcements are pinned, high-visibility posts that show up at the top of every member’s home feed. A good first announcement covers:

  • Why the team is moving to Zoho Connect
  • What goes where (groups, channels, manuals)
  • The expectation for the first week (introduce yourself, complete the onboarding manual, post one update)
  • Where to ask questions

Pair the announcement with a poll asking what people want to see in the network next. Polls drive early engagement because they require only a click and they signal that admin actually wants input.

Zoho Connect vs Slack vs Microsoft Teams

The most common comparison teams make when evaluating Connect is against Slack and Microsoft Teams. They are different products solving overlapping but distinct problems.

Slack is built around fast-flowing channel chat with a deep integration ecosystem. What it does not give you natively is a structured intranet, a wiki-style knowledge base, polls and surveys with reporting, or a kanban task board. Teams that use Slack heavily often layer in Notion, Confluence, or Trello to fill those gaps.

Microsoft Teams is built around video meetings and channel chat with deep integration into the Microsoft 365 stack. If your organization is fully on Microsoft 365, Teams is the path of least resistance. Like Slack, it does not include a wiki layer or social-feed experience natively (SharePoint sits next to it for that).

Zoho Connect sits in a different shape. It is weaker than Slack on real-time chat and weaker than Teams on video meetings, but it gives you feeds, groups, manuals, boards, polls, and forums in a single product with a single login. For organizations that want a true internal network rather than a chat tool, and especially for organizations already using other Zoho apps, Connect is the most cohesive option. Where it falls short: a smaller integration ecosystem than Slack, a functional rather than polished mobile app, and slightly slower real-time chat.

What Are the Common Zoho Connect Setup Mistakes?

After watching teams roll out Connect, the same handful of mistakes show up repeatedly. Avoid these and your launch will land much better.

Creating too many groups upfront. A network with 20 empty groups looks abandoned. Start with three or four and add groups when there is concrete demand.

Not designating a clear admin model. If only the founder is admin and the founder is busy, the network stagnates. Assign at least one moderator per major group on day one and document who owns what in a Manual page.

Ignoring Manuals. Teams that use Connect only for feeds and chat get a chat tool. Teams that invest 30 minutes in a starter Onboarding Manual get an institutional memory layer. The Manual is what differentiates Connect from a pure chat product.

Treating it like Slack-only. If you only use channels and never use feeds, polls, town halls, manuals, or boards, you are paying for features you are ignoring. Schedule one town hall, run one poll, and publish one Manual chapter in the first month.

Skipping branding. A default-themed network signals “experimental tool” and adoption suffers. Five minutes of branding (logo, colors, custom domain on Enterprise+) makes the network feel like a real internal product.

Inviting everyone before content exists. Invite three or four pilot members first, populate at least one feed post, one Manual page, and one Board card, then bulk-invite the rest. People who land in an empty network do not come back. The Zia AI features included with Zoho Connect Ultimate are covered in our Zoho AI / Zia overview guide.

Frequently Asked Questions

What is Zoho Connect used for?

Zoho Connect is used as an internal team network that combines a social-style activity feed, real-time chat channels, a wiki-style knowledge base (Manuals), a kanban task tracker (Boards), polls, surveys, town halls, and forums into a single private workspace for a company or department. Teams use it as a modern intranet, an alternative to combining a chat product with a separate wiki and project tool, and as a centralized home for announcements, onboarding, and team-wide collaboration.

Is Zoho Connect free?

Zoho Connect has a Free plan with limited features that works for very small teams or post-trial fallback use. Most teams will outgrow the Free plan quickly because it limits the most valuable parts of the product (Manuals, Boards, integrations, branding). The paid tiers (Starter with a 25-user minimum, Enterprise with a 10-user minimum, and Ultimate with a 10-user minimum) unlock the full feature set. Zoho does not publish current USD prices on its pricing page, so check the official Zoho Connect pricing page for live numbers in your region.

How is Zoho Connect different from Slack?

Slack is built around fast real-time channel chat with a large integration ecosystem. Zoho Connect is built around persistent feeds, groups, and pages, with chat as one of several layers alongside Manuals (wiki), Boards (kanban), Forums, and Town Halls. If you want a pure chat tool with a deep app marketplace, Slack is the stronger choice. If you want a single product that combines chat, intranet, knowledge base, and task tracking, Zoho Connect is the more cohesive option.

Is Zoho Connect included in Zoho One?

Yes. Zoho Connect Ultimate is included as part of the Zoho One bundle along with 50+ other Zoho applications, Zia AI features, single sign-on, and mobile device management. Zoho One is priced at $45 per user per month (monthly) or $37 per user per month (annual) on the All Employee plan, and $105 per user per month (monthly) or $90 per user per month (annual) on the Flexible User plan. For organizations already using three or more Zoho apps, Zoho One frequently costs less than buying Connect Ultimate plus the other apps separately.

For current plan details, see Zoho Books pricing or Zoho Desk pricing.

Want to learn more about Zoho One?

External Resources

Related Guides