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, you can choose Cliq's native account controls or organize those accounts with the surrounding work apps in WebCatalog.
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 relationship | Access to confirm | Suggested desktop arrangement |
|---|---|---|
| Employee in your main company | Your internal account and assigned channels | A company profile and work space |
| Client gives you a separate authorized login | That account's organization and channel access | A separate profile named for the client |
| Supplier already uses Cliq | An external channel or other permitted collaboration route | Your existing account beside the supplier's project tools |
| Contractor joins a limited assignment | Guest access to the required conversations, where supported | The authorized guest context and project brief |
| Long-term partner community | Membership in a Cliq Network | The 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 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
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 WebCatalog's profile setup:
- Open Profiles and choose Add profile.
- Name the first profile for the account it will hold, such as “Company Operations.”
- Open Cliq with that profile and sign in through your organization's normal process.
- Create a second profile, such as “Client North,” and sign into the separate client-issued account there.
- 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 WebCatalog 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.
Choose a WebCatalog plan that fits the number of apps, profiles, and spaces you need. Count distinct logins separately from projects: five projects using one account do not automatically require five profiles.
Example: a delivery manager working across three relationships
Imagine a delivery manager coordinating an internal product rollout, a client implementation, and a supplier handover. The projects share a person, but they do not share every account or document.
Internal rollout: keep the team conversation beside the plan
Use the company account for the internal rollout. Place that Cliq session beside the release checklist and decision log in a “Product Rollout” space.
When a team member asks whether a milestone is ready, the plan is available in the same working context. Record the decision where the project team expects it, then respond in the appropriate channel. The benefit is an easier path from discussion to the record that supports it.
This does not require a new Cliq account just because the rollout has its own space. The company login can also be reused in an operations space if both contexts belong to the same identity.
Client implementation: keep the client's issued login separate
Suppose the client provides an account for its organization. Assign that login to the Client North profile and use it with the client's project tools.
Before the first review, confirm access to the implementation channel and the document under discussion. If the chat opens but the project file does not, identify which account the file service expects. A working Cliq session does not prove that every supporting app uses the same credentials.
Use the client space as a reminder of the active assignment. When sharing a file, check its intended audience and the destination conversation. The point is to make the normal review process easy to follow, with the relevant documents already at hand.
Supplier handover: reuse the company identity where appropriate
For the supplier, an approved external channel may be enough. Keep the company account and add the supplier handover documents to a separate project space.
The access map should show that this conversation still uses Company Operations. That distinction matters when you return after an interruption: you are an employee collaborating externally, not someone signed into the supplier's internal organization.
If the supplier cannot join, have the responsible administrators check the invitation and collaboration policies. Creating a fresh WebCatalog profile will not change the server-side permission that controls participation.
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. The useful questions are concrete: which login is used, which conversations remain necessary, and who can change that access?
A departure may require an administrator to remove organizational or guest access. Removing a desktop shortcut is a separate housekeeping action. Complete the service-level change through the organization that controls the membership, then tidy the workspace to match.
Also review the apps around the conversation. A project can finish while an old brief, calendar, or document account remains in daily view. Remove destinations that no longer support active work so the space continues to reflect its purpose.
If notifications become distracting, decide which conversation requires a response during each work block. Use the notification controls available in the relevant Cliq environment, and check the result before depending on it. Keeping more accounts accessible does not mean every account must receive equal attention all day.
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 add Zoho Cliq to WebCatalog, 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.
