➕Child Accounts

Explore how to create and manage multiple ClearFeed accounts

One ClearFeed Account (Parent or Child Account) is linked to one Product Edition - External Helpdesk, Internal Helpdesk, or Internal Helpdesk (Integrations). The 3 different product editions have different pricing models.

One ClearFeed Account (Parent or Child Account) can be integrated with only one Slack or Teams workspace. Integrations with Zendesk and other ticketing/issue management systems can be shared between 2 ClearFeed Accounts.

If you have 2 different accounts (one parent and one child) with different product editions, you will receive 2 different invoices from ClearFeed.

Each ClearFeed account (Parent of Child Account) has its own set of users for admins to maintain data access and privacy.

Usecase

Creating a child account is advisable in the following scenarios:

Integrate ClearFeed with multiple Slack workspaces
Integrated CkearFeed with Slack and MS Teams workspaces
Integrate multiple domains from your ticketing system into the same Slack workspace.
Currently using ClearFeed as an External Helpdesk, and want to start using ClearFeed as an Internal Helpdesk (and vice-versa).
Currently using ClearFeed as an Internal Helpdesk, and want to start using ClearFeed for Integrations (and vice-versa).
For internal helpdesk support - creating multiple accounts can be helpful to isolate work across different teams if you don't want tickets on one account to be visible to users from another account.

To create additional ClearFeed accounts, you need to be an Admin in the primary account. This is mandatory.

Create child accounts

Navigate to your profile icon at the bottom-left corner
Click on Create New Account.
Enter a name for the new account.
Choose the required sharing option for this account:
- Share Slack workspace with your account: This allows you to connect with other ticketing integrations into the same Slack workspace (e.g. connect multiple Zendesk domains with this approach).
- Share other integrations with your account: Connect this account with a new Slack workspace but share the ticketing integrations with the primary account.
  - E.g.: Connect different Slack workspaces with the same Intercom domain using this approach.
- Share Slack workspace and all supported integrations with your account: Connect your new account with the same Slack workspace and share the ticketing integrations with the primary account.
  - E.g.: Connect existing Slack workspaces with the same Intercom domain using this approach.
Select Product Edition for the child account setup

Switch Accounts

Once you have created additional accounts, you can switch between the accounts by simply hovering over the profile icon (bottom-left corner) and you will notice all the accounts. From there, click on the account you want to switch to and you'll be redirected to that account.

Rename Accounts

You can rename your account name at any time on ClearFeed.

Slack workspace

Connect your new ClearFeed account to the same Slack workspace as your primary account, sharing channels and conversations for seamless collaboration.
Maintain independent integrations for your new account, separate from those of your primary account.
Set unique SLA policies, business hours, users, and collections for your new account.

Other integrations

Only Zendesk, Intercom, and Atlassian are supported as shared integrations as of now. If you want to request support for additional integrations, please reach out to us via Slack or at support@clearfeed.ai.

Create a new ClearFeed account to connect with a different Slack workspace sharing the same email domain as your primary account.
Share integrations between your primary ClearFeed account and the new account across multiple Slack workspaces.
Use the same integrations connected to your primary account across various Slack workspaces.
The new account can set its own SLA policy, business hours, users, and collections.

Note:

If an integration is shared, the child account cannot reconnect or delete it.
However, users are allowed to independently connect any other (non-shared) integration to a child account .
If any new ticketing integration is configured as shared, behavior #2 will apply.

Slack workspace & other integrations

By selecting this option, your new account will be linked to the same Slack workspace and use the same integrations as your primary account.
Since multiple teams use Zendesk ticketing and forms, creating a child account with this configuration allows users to customize screen options for forms. For example, some teams might want to hide the "Solve" button, while others prefer to remove the "View Form" button.

Note:

If an integration is shared, the child account cannot reconnect or delete it.
However, users are allowed to independently connect any other (non-shared) integration to a child account .
If any new ticketing integration is configured as shared, behavior #2 will apply.

Relationship with Primary Account

Dependent

The whitelisted bots are shared between primary and secondary account(s). That means, that when a new account is created, it carries forward the whitelisted bot configuration from the primary account. Any change in this configuration from any of the accounts (primary or secondary) will be reflected across all accounts.
Whitelisted domains allow users from a list of domains to join the ClearFeed Account automatically. Only the admin user’s email domain is copied over to the child account. Any other whitelisted domains are not copied. Gmail is an exception and is never copied, even for admins. To whitelist more domains, users need to manually add them to the child accounts.
If you choose to share the integrations and connect the new account to a different Slack workspace, then the integrations will be dependent on the primary account. You will be unable to reconnect or delete them from the new account.

Independent

Account-level settings such as SLAs, business hours, data retention, and user management are independent of the new account(s).
Collection and channel management settings are independent and isolated for the new account.
Objects (forms and fields), Announcements and Knowledge Sources are independent and isolated for the new account.