This is Module 2 of the Tribe Administrator Training. In this module, you will configure the building blocks that determine what data your organisation captures in Tribe and how it is structured. There are three distinct tools for this, and choosing the right one for the right job is the most important skill you will develop as an administrator.
Understand the Three Building Blocks
Before diving into the configuration steps, it is worth understanding what each tool is for.
Fields | Capture structured data about a record. A field lives on a relation card or activity and stores a specific piece of information — a date, a text value, a dropdown selection. Fields are the foundation of your data model. |
Labels | Group and segment relations flexibly. A label is not a property of a record — it is a tag you assign to one or more relations to create a group. Labels are ideal for dynamic segmentation that crosses relation types. |
Products | Are what your organisation sells. They live in a catalogue and are used in opportunities and invoices. Products are not data about a relation, they are the items you add to a quotation or invoice. |
Fields
Fields are the most fundamental configuration in Tribe. Every piece of information you want to capture — beyond the standard fields that come out of the box — needs to be added as a custom field. The articles below walk you through creating, editing, and deleting fields, and through customising form layouts and list views.
Read: What is a Field?
Read: Creating a Field
Read: Editing a Field
Read: Deleting a Field
Assignment 1: Add a custom field
Identify a piece of information your organisation needs to capture that is not yet in Tribe.
Add it as a custom field to the appropriate entity (relation type or activity).
Check whether the field needs a default value, whether it should be required, and which field type fits best.
Verify that the field appears correctly on the record card.
Labels
Labels let you group relations in ways that fields cannot — across relation types, with multiple values per record, and without adding extra fields to your data model. The articles below cover when to use labels instead of fields, and how to set up a clean label structure.
Assignment 3: Create a label structure
Think of a segmentation need in your organisation that cannot be covered by a single field — for example, event attendees, newsletter subscribers, or partner categories.
Create a label category and at least two labels within it.
Assign the labels to a few test relations.
Build a filter using the label in a view or campaign selection.
Products
Products form the catalogue your team uses when creating quotations and invoices. A well-structured catalogue saves time, reduces errors, and keeps your reporting consistent. The articles below cover setting up product groups and managing your catalogue.
Assignment 4: Set up a product
Add a new product to your catalogue with the correct price, VAT setting, and user permissions (price editable yes/no).
Create a product group and assign the product to it.
Add the product to a test opportunity or invoice to verify it works correctly.
Quick Summary
This module covers the three configuration tools that define your data model: fields for capturing structured information on records, labels for flexible cross-type segmentation, and products for managing your sales catalogue. With these in place, you have the foundation you need to build the templates covered in Module 3.
Module 2 complete. Continue to Module 3: Email & Document Templates.