How to Manage Multiple Zoho Cliq Accounts Across Organizations

Zoho Cliq's desktop app holds up to ten accounts. Map your access, then use WebCatalog Desktop to group each login with its work apps.

October 20, 2026

Khang Nguyen · Operations Specialist

How to Manage Multiple Zoho Cliq Accounts Across Organizations

Zoho Cliq conversations can cross company boundaries. You might work inside your employer's organization, collaborate with a supplier, and use a separate client-issued account for another assignment. Each relationship can require a different kind of access.

The first step to manage multiple Zoho Cliq accounts is to map those relationships. Separate logins need separate sessions. An external channel, guest invitation, or Network may let you collaborate through the account you already use. Creating another desktop profile does not decide which arrangement your organization permits.

Once the access model is clear, Cliq's own desktop app can hold up to ten separate logins, each opening in its own window. If you want each login grouped with the other web apps that relationship uses, WebCatalog Desktop can keep the accounts in separate profiles.

Separate the login question from the organization question

“Multiple organizations” can describe several different situations. An employee with another company-issued login has a different problem from a partner invited into a shared conversation.

Zoho's documentation for Cliq with CRM Plus makes this distinction explicit: a user belongs to one primary organization and can join other organizations as an external user. It documents switching between those contexts, with access that differs from internal membership.

More recently, Cliq's guest-user controls introduced access to mapped channels and contacts within another organization. Participation depends on the invitation and relevant organizational policies.

That means the same email appearing in more than one company's work does not necessarily represent two independent Cliq accounts. Ask whether you are using a separate login, an external membership, or a specific collaboration invitation. Rules for multiple organizations in other Zoho products should not be assumed to apply unchanged to Cliq.

Build an access map before adding desktop accounts

Create a small record of the work you need to do. For each destination, identify the login, access type, responsible administrator, and supporting materials.

Work relationshipAccess to confirmSuggested desktop arrangement
Employee in your main companyYour internal account and assigned channelsA company profile and work space
Client gives you a separate authorized loginThat account's organization and channel accessA separate profile named for the client
Supplier already uses CliqAn external channel or other permitted collaboration routeYour existing account beside the supplier's project tools
Contractor joins a limited assignmentGuest access to the required conversations, where supportedThe authorized guest context and project brief
Long-term partner communityMembership in a Cliq NetworkThe relevant Network beside partner resources

Treat the map as a description of actual access. A space called “Client North” is useful only if the account inside it can reach the intended conversations.

For example, record “company login, supplier external channel, procurement owner” rather than “supplier account” when no separate supplier login exists. Clear labels prevent you from creating duplicate profiles to solve a problem that belongs in the access configuration.

Understand the native options already available

Cliq's desktop app handles multiple account logins

The native Zoho Cliq desktop app already supports multiple accounts. Zoho documents Accounts → Add account for adding a login, with a maximum of ten accounts. Selecting an account from the Accounts menu opens a new Cliq window for it.

If your work is mostly inside Cliq, this is a direct option. You can use the app's account menu to reach the separate company logins you already have. WebCatalog Desktop becomes more useful when each account is one part of a larger workflow involving project records, documents, calendars, and other web apps.

External channels connect organizations around a conversation

An external channel lets people from different organizations collaborate together. The required policies and invitation determine access. Zoho also supports external-channel collaboration across specified data centers, while direct messaging across data centers has different limitations.

External-channel creation is plan-dependent: the Free plan cannot create them, and who can create them on paid plans depends on the edition and administrator permissions. Check the host organization's setup before choosing this route for a supplier relationship.

Guest access and Networks serve different relationships

Zoho's updated guest feature lets invited collaborators join existing channels. That can fit a contractor helping with a specific campaign. A Cliq Network provides a dedicated environment for broader external collaboration, such as a continuing partner community.

Check the current guest documentation before proposing the newer workflow: Zoho currently says Guest Users 2.0 is not supported in Zoho One, and it does not support inter-data-center direct messages. The available route should come from the actual organization's edition and configuration.

These native choices can remove the need for another account. Use a separate login when the work really requires one, and use the appropriate collaboration feature when the relationship is external participation.

Organize the approved setup in WebCatalog Desktop

With your access map ready, configure the desktop around it. WebCatalog Desktop lets you launch Cliq in a dedicated window and organize it with other web apps.

For two distinct logins, follow the profile setup:

  1. Open WebCatalog Desktop, go to Profiles, and choose Add profile.
  2. Name the first profile for the account it will hold, such as “Company Operations.”
  3. Open Cliq with that profile and sign in through your organization's normal process.
  4. Create a second profile, such as “Client North,” and sign into the separate client-issued account there.
  5. Confirm the account and organization in both sessions before adding more destinations.

Profiles keep cookies, sessions, and browsing data separate. They do not supply an invitation, assign a license, or change the access granted inside Cliq.

Next, create a space for each working context. The company space might include Cliq, the operations tracker, and the internal handbook. The client space might contain the client's Cliq session, project plan, and review documents.

Each space opens in its own window. Reusing the same profile in multiple spaces reuses the same login; a different space name does not establish another account identity. This reuse is appropriate when one account legitimately participates in several project conversations.

Keep the access map useful as work changes

Update the map when a client assignment begins, a contractor finishes, or responsibility moves to another colleague. Removing someone's organizational or guest access happens in Cliq, through the organization that controls the membership; deleting a profile only removes the local session.

When a project ends, remove its apps and space from your desktop so what you see matches the work that is still active.

Give the next organization a clear place on your desktop

Start with one company login and one external relationship. Decide whether that relationship needs a separate account, a guest invitation, an external channel, or a Network. Record the answer before configuring the desktop.

Then download WebCatalog Desktop, create profiles for the distinct logins, and assemble spaces around the work each relationship produces. Your account structure stays aligned with the access your organizations provide, while the conversations and tools become easier to find together.

Related articles

Related apps