Packs in Tribe CRM help you organise, manage, and share configuration between different Tribe environments. They allow setups such as entities, fields, automations, and views to be grouped together and reused in a controlled way. You might use packs when you manage multiple environments or want to share a consistent setup with another Tribe environment. By following this guide, you will understand what packs are, the different pack types, and how to use share packs safely and effectively.
Table Of Contents
What Does This Feature Do?
What Types Of Packs Are There?
Why Or When Should You Use Packs?
How Do You Share A Share Pack?
How Do You Place Configurations In A Pack?
What Data Cannot Be Included In A Pack?
Tips Or Best Practices
What Does This Feature Do?
Packs in Tribe CRM group configuration elements so they can be managed and shared as a single unit. A pack can contain entities, fields, drop-down lists, automations, templates, dashboards, and other configuration items. This makes it easier to keep environments consistent and reduces the need to recreate setups manually. Packs also control ownership and permissions, ensuring changes are managed in a structured way.
What Types Of Packs Are There?
Tribe CRM uses four different types of packs, each with a specific purpose.
A Basic Pack is included automatically when a Tribe environment is created. It contains standard activities, relations, and relationships managed by Tribe. This pack cannot be modified in a customer environment.
An Application Pack is added automatically when a module is enabled. These packs contain the configuration required for specific modules and are managed by Tribe. They cannot be changed or deleted in a customer environment.
An Environment Pack is created automatically for each environment and has the same name as the environment. It stores all configuration created by users, such as custom fields, views, and automations. All employees in the environment can access this pack, depending on their rights.
A Share Pack is used to share configuration with other Tribe environments. Share packs are created by administrators and can be shared with other environments where administrators accept the pack invitation.
Why Or When Should You Use Packs?
You may want to use packs when you manage more than one Tribe environment and want to reuse the same setup. Packs are useful for sharing standardised configuration between environments while keeping ownership clear. Share packs are especially helpful when rolling out new functionality across multiple environments. They also help reduce configuration errors by ensuring the same setup is used consistently.
How Do You Share A Share Pack?
Before sharing a pack, make sure the pack exists in the configuration environment, you have administrator rights, and you are the owner of the share pack.
Follow these steps to share a share pack with another environment:
Create a new share pack in the configuration environment under Configuration > Packs.
Select the share pack and choose the option to share it with another administrator.
Enter the details of the administrator in the target environment.
Ask the receiving administrator to open the correct environment before accepting the invitation link from the email.
Confirm the pack has been accepted and is now available in the share environment.
Once shared, the configuration contained in the pack becomes available in the target environment.
Note: If sharing is stopped later, the configuration from the pack will no longer be available in that environment. Any data linked to that configuration can no longer be accessed.
How Do You Place Configurations In A Pack?
When adding configuration to a pack, the order is important to avoid broken references. The recommended order is:
Drop-down list entities
Drop-down list values
Label categories
Label values
Entities without links
Entities with links to other entities
Forms
Widgets
Automations
Templates
Dashboards
Library files
To place an item in a pack, open the configuration item, go to the General or Details tab, and select the appropriate pack. Save your changes and repeat this process for all related items, following the correct order.
Did you know?
If no share packs exist or you do not own any share packs, the option to select a pack will not be shown.
What Data Cannot Be Included In A Pack?
Some data and settings cannot be included in a share pack. These include organisation settings, sales settings, imports, API applications, employees, mailboxes, roles, teams, products, price lists, and event-related settings. These elements remain environment-specific and must be managed separately.
Tips Or Best Practices
Avoid removing packs from environments where data is actively used, as this can make information inaccessible. Always add linked configuration in the correct order to prevent missing references. Test share packs in a controlled environment before using them widely. Keep share packs focused and clearly named to make their purpose easy to understand.
Quick Summary
Packs in Tribe CRM allow you to group and manage configuration in a structured way. Share packs make it possible to reuse setups across multiple environments while keeping ownership clear. By using packs correctly, you can maintain consistent configuration and reduce manual setup work across your Tribe environments.