Skip to main content
All CollectionsConfigurationsGeneral
How do packs work within Tribe CRM?
How do packs work within Tribe CRM?
Updated over 2 weeks ago

In Tribe CRM, we have different types of packs. In a pack, various entities, fields, automations and the like are included, to be shared in its entirety with another Tribe environment. Basically, the system shares the necessary packs with a customer environment. However, it is also possible for you to create one or more packs so that the setup from one environment can be shared with another environment. In this article, we explain the use of packs.

  1. What types of packs are there?
    ​

  2. Schematic overview of pack usage in Tribe CRM
    ​

  3. How do I share a share pack?
    ​

  4. How do I place the device in a pack?
    ​

  5. What data cannot be included in a pack?
    ​

1 What pack types are there?

Four pack types are used in Tribe CRM.
​

Basic pack
​

Every Tribe environment is provided with a basic set-up by means of the basic pack when it is created. This pack is managed by Tribe and provides e.g. the standard activities, relations and relationships. The configuration offered in this pack cannot be modified in the customer environment.
​

Application pack
​

The set-up of the various modules is contained in various application packs. Application packs are automatically added to the customer environment by the administrator when enabling a module on the account page. Modifying and deleting the configuration from the application pack is not possible in the customer environment.
​

Environment pack
​

An environment pack is automatically created in every environment. The name of the pack is the same as the name of the Tribe environment. This pack exists only within the customer environment in question and contains the configuration added to that environment by the customer, such as a custom field, automation or view. Every employee in an environment can access this pack and their customisations are stored in it. The rights determine which customisations these are.
​

Sharepack
​

The purpose of a share pack is to share the set-up from this pack with other environments. The share packs can be found in the application under configuration > packs.
​

Packs in Tribe CRM
​

The packs in the left column are created in the environment and are managed there and can be shared, packs in the right column are shared/available in the environment.
​

Definitation of icons in packs
​

  • Option to share the pack with other environments
    ​

  • Option to set pack owners
    ​

  • Option to delete pack in the environment
    ​

Please note that the use of share pack is free, however, it is possible that additional charges may apply for any additional environments and users required.
​

2 Schematic overview of pack usage Tribe CRM

Packs in Tribe CRM
​

  1. Basic configuration: This environment contains the basic and application packs. These are managed by Tribe and shared by default with all (customer) environments.
    ​

  2. Customer management environment: This environment contains the basic configuration, the proprietary environment pack and the share packs, which can be shared with the share environments. Management of this environment lies with the customer.
    ​

  3. Customer share environment 1: This environment contains the basic configuration, the own environment packs and the share pack from the customer management environment.
    ​

  4. Customer share environment 2: This environment contains the basic configuration, the custom environment packs and the share pack from the customer management environment.
    ​

3 How do I share a share pack?

The purpose of a share pack is to share configuration and/or data entities with other environments. The setup in the customer configuration environment is in the environment pack, as mentioned earlier. In order to share this with other environments, the relevant setup needs to be moved to the share pack so that it can be shared.
​

To do this, the settings below must first be checked:
​

  • The shared pack must be created in the (configuration) environment
    ​

  • The user to be set up must have administrator rights
    ​

  • The user to be set up must be the owner of the shared pack
    ​

Then you can create the desired setup, e.g. add your own activity with fields and automations. Follow the steps in chapter 4 for an explanation of how to add facilities to the pack.
​

It is possible to add the complete setup to the pack first and then share the pack with the other environment. However, it is also possible to share the pack first and then add the device afterwards.
​

Follow the steps below to share a share pack with another environment:
​

  1. Create a new share pack in the (setup) environment.
    ​

    New share pack in Tribe CRM
    ​

  2. Share the pack with a user with administrator privileges in the share environment.
    ​

    Share pack in Tribe CRM
    ​

  3. The relevant administrator receives an email invitation with a link to accept the shared pack. If the administrator has access to multiple environments, it is necessary to open the share environment first before clicking the link. The pack may otherwise be linked to the wrong environment.
    ​

  4. Once added, the functionality of the pack will be available in the share pack environment.
    ​

Note:
​

  • If you remove a pack from an environment at a later point in time (sharing is stopped), the corresponding device will no longer be available in this environment. As a result, data linked to the setup can no longer be accessed, e.g. the data in fields or entities created in the pack and therefore disappeared.
    ​

  • Fixtures from Tribe's base pack can never be moved to another pack.
    ​

4 How do I place furnishings in a pack?

When placing furnishings in a pack, it is important to follow the correct order. The preferred order is as follows:
​

  1. Entity selection lists
    ​

  2. Selection list values
    ​

  3. Label category
    ​

  4. Label values
    ​

  5. Entities without links to other entities
    ​

  6. Entities with links to other entities in the shared pack
    ​

  7. Forms
    ​

  8. Widgets for drop-down lists/activities/relationships/etc.
    ​

  9. Widgets drop-down lists/activities/relationships/etc.
    ​

  10. Automations
    ​

  11. Templates and templates
    ​

  12. Dashboards
    ​

  13. Library files
    ​

Please note
​

  • If there are no shared packs, or the user does not own shared packs, the pack choice will not be shown.
    ​

  • If changing a pack makes this setup unavailable in another environment, the entity's data is no longer findable. Basically, it can be said that the situation that fixtures disappear in an environment should always be avoided.
    ​

Selection list entity
​

  1. Select or create the drop-down list via the Configuration drop-down list.
    ​

  2. Open the drop-down list.
    ​

  3. Click the cog for the configuration page and open the General tab.
    ​

  4. Choose the appropriate pack.
    ​

    Selection list entity
    ​

Selection list values
​

With a selector list in a pack, it is also possible to define the default values in the setup and share them in the pack. This gives all environments the same drop-down list values with the same IDs
​

  1. Navigate to configuration > selection lists > click on the selection list
    ​

  2. Click on the drop-down list value to be added in it
    ​

  3. Adjust the field pack
    ​

  4. Repeat for all values.

    Drop-down list value in pack B
    ​

Label category
​

  1. Navigate to configuration > labels > click a label category or create one
    ​

  2. Adjust the pack
    ​

  3. Repeat for the other labels
    ​

    Label category in pack B
    ​

Label values
​

  • Navigate to configuration > labels > click a label or create one
    ​

  • Customise the pack
    ​

  • Repeat for all labels
    ​

    Label in pack B
    ​

Label values
​

  • Navigate to configuration > labels > click a label or create one
    ​

  • Customise the pack
    ​

  • Repeat for all labels
    ​

    Label in pack B
    ​

Entity without links to other entities
​

If the entity contains links to other entities, such as drop-down lists, relations, activities, etc., please read the following section on how to perform the actions in the correct order. If the entity does not contain any links, follow the steps below.
​

  1. Navigate to the entity (relation/activity/own entity)
    ​

  2. Open the entity
    ​

  3. Click on the general tab
    ​

  4. Adjust the pack
    ​

    Entity in pack 2
    ​

  5. Then navigate to the fields tab
    ​

  6. Select a field to place in the appropriate pack and save it
    ​

  7. Repeat this step for the other fields

    Field in pack B
    ​

Entity with link to entities
​

If the entity contains a link to other entities, such as drop-down lists, relationships, activities, etc., follow the sequence in the steps below.
​

  1. Navigate to the entity (relationship/activity/own entity).
    ​

  2. Open the entity.
    ​

  3. Click on the general tab.
    ​

  4. Adjust the pack.
    ​

  5. Does the entity contain links to choice lists? If so, navigate to configuration > selection lists.
    ​

  6. On the choice list entity on the general tab and adjust the pack.
    ​

  7. Then close the entity and open a choice list value and customise the pack.
    ​

  8. Repeat step 7 for all choice list entities.
    ​

  9. Does the entity contain a link to a phase? If so, navigate to configuration > drop-down lists.
    ​

  10. On the phase entity on the general tab and adjust the pack.
    ​

  11. Then close the entity and open a phase value and customise the pack.
    ​

  12. Repeat step 11 for all phase values.
    ​

  13. Navigate again to the (main) entity (relationship/activity/own entity).
    ​

  14. Open the entity.
    ​

  15. Click on the fields tab.
    ​

  16. Select a field to place in the appropriate pack and save it.
    ​

  17. Repeat this step for the remaining fields.
    ​

Forms
​

Follow the steps below to place a web form in a pack.
​

  1. Navigate to configuration > forms.
    ​

  2. Open the entity.
    ​

  3. Click on the general tab.
    ​

  4. Customise the pack.

    Web form in pack 2
    ​

If the form contains links to other entities, such as drop-down lists, relationships or activities, perform the actions in the correct order.
​

  1. Select list entity
    ​

  2. Value list
    ​

  3. Fields
    ​

Views
​

Follow the steps below to place a view in a pack.
​

  1. Navigate to appropriate entity.
    ​

  2. Click on the view tab.
    ​

  3. Create a view or select a view.
    ​

  4. Customise the pack.
    ​

    View in pack B
    ​

Widgets
​

Follow the steps below to place a widget in a pack.
​

  1. Navigate to appropriate entity.
    ​

  2. Click on the widget tab.
    ​

  3. Create a widget or select a widget.
    ​

  4. Customise the pack.
    ​

    Widget in pack B
    ​

Automations
​

Follow the steps below to place an automation in a pack.
​

  1. Navigate to appropriate entity.
    ​

  2. Click on the automation tab.
    ​

  3. Create an automation or select an automation.
    ​

  4. Customise the pack.
    ​

    Automation in pack B
    ​

(Part) Templates
​

Follow the steps below to place a template in a pack.
​

  1. Navigate to the appropriate template.
    ​

  2. Customise the pack in the details
    ​

    Template in pack B
    ​

Dashboards
​

Follow the steps below to place a dashboard in a pack.
​

  1. Create a new dashboard or open an existing one.
    ​

  2. Open the dot menu on the right of the dashboard.
    ​

  3. Customise the pack in the details.
    ​

    Dashboard in pack B
    ​

Library files
​

Follow the steps below to place a library existence in a pack.
​

  1. Navigate to configuration > library.
    ​

  2. Open a file and customise the pack.
    ​

5 What data cannot be included in a pack?

A number of entities are restricted from being included in a share pack.
​

Not in share pack

The entities below cannot be included in a share pack.

  • Organisation settings such as language and currency sign

  • Sales settings such as offer validity period

  • Imports

  • API applications or webhooks

  • E-mail clicks

  • Domain validations

  • Employees

  • Mailboxes

  • Teams

  • Roles

  • Hours types

  • Kilometre registration types

  • Products

  • Event locations

  • Event types

  • Email senders

  • Product groups

  • Products

  • Price lists

Management at Tribe CRM

It is possible for a Tribe CRM consultant to add a custom customer portal to a share pack. This action cannot be performed by the customer environment administrator. Before adding the portal to a pack, it is necessary that all the setup the portal refers to has been added in the pack. If it is desired to include a portal in a share pack, please contact Tribe CRM for an inventory of the work.

Did this answer your question?