Understanding the Teamo Hierarchy
Every piece of information in Teamo lives within a structured hierarchy.
This hierarchy is what allows Teamo to remain flexible enough for different industries while keeping information organized, connected, and easy to manage.
Understanding how the hierarchy works will help you design better systems, build more effective workflows, and avoid common setup mistakes.
The Teamo Hierarchy
Organization → Unit → Module → Record → Activity Group → Activity → Detail
Each level serves a different purpose and helps organize information in a logical way.
Hierarchy and Rows
The hierarchy defines how information is organized within Teamo. At different levels of the hierarchy, information is stored as rows.
Teamo supports three row types:
- Records
- Activities
- Details
For example:
Organization → Unit → Module → Record → Activity Group → Activity → Detail
In this hierarchy:
- Record is a row type
- Activity is a row type
- Detail is a row type
To learn more about row types and when to use them, see Understanding Rows: Records, Activities, and Details.
Organization
The Organization is the highest level in Teamo. It represents your company, workspace, or business environment. Everything you create in Teamo belongs to an Organization.
Examples
- DigiMarketing LLC
- Acme Consulting
- ABC Healthcare
- XYZ Events
Most companies will only have one Organization.
Unit
Units are used to separate major areas of your business. A Unit can represent a department, business function, office location, region, business entity, or any other high-level division that makes sense for your organization.
Units help keep related systems, data, and workflows organized while still allowing them to remain connected within the same Organization.
Examples
Departments:
- Sales
- Marketing
- Operations
- Finance
- Human Resources
Office Locations:
- London
- Tokyo
- New York
- Sydney
Regions:
- North America
- Europe
- Asia Pacific
Business Entities:
- Acme Holdings
- Acme Consulting
- Acme Ventures
The best Unit structure depends on how your organization operates. Some companies organize by department, others by location or business entity, and many use a combination of these approaches.
Module
Modules are where specific business processes are managed. Each Module is designed to manage a particular type of information or workflow.
Examples
- Leads
- Clients
- Projects
- Events
- Employees
- Inventory
- Vendors
- Support Tickets
Most businesses will create multiple Modules inside each Unit.
Example
Unit: Commercial
Modules:
- Leads
- Clients
- Events
Record
Records are the primary items managed within a Module. Every Module contains Records. If a Module represents a process, a Record represents a specific item within that process.
Examples
Inside a Leads Module:
- Acme Corporation
- Johnson Manufacturing
- Global Ventures
Inside a Clients Module:
- Nike
- Coca-Cola
- Spotify
Inside an Events Module:
- Annual Marketing Summit 2026
- Product Launch Event
- Customer Workshop
Activity Groups
Activity Groups help organize related information and activities within a Record. They provide structure and allow businesses to group related work into logical categories.
Example: Marketing Agency Client Record
Record: Nike
Activity Groups:
- Contacts
- Invoices
- Brand Assets
- Campaigns
- Reports
Example: Event Record
Record: Annual Marketing Summit 2026
Activity Groups:
- Schedule
- Contractors
- Attendees
- Budget & Expenses
- Equipment
As Records grow over time, Activity Groups help keep information organized and easy to navigate.
Activities
Activities are the individual items that live inside an Activity Group. An Activity can represent a task, meeting, campaign, invoice, contact, expense, deliverable, attendee, contractor, milestone, or any other item relevant to the process being managed.
Examples
Inside the Contacts Activity Group:
- John Smith
- Sarah Johnson
- Michael Lee
Inside the Campaigns Activity Group:
- Summer Product Launch
- Black Friday Campaign
- Customer Retention Campaign
Inside the Budget & Expenses Activity Group:
- Venue Deposit
- Catering Invoice
- AV Equipment Rental
Details
Details are the most granular level of information in Teamo. They typically contain tasks, notes, updates, files, comments, interactions, or supporting information related to a specific Activity.
Examples
Activity: Summer Product Launch
Details:
- Create social media assets
- Design banner ads
- Write landing page copy
- Schedule social media posts
Activity: John Smith
Details:
- Initial discovery call completed
- Sent proposal on June 12
- Requested revised pricing
- Follow-up meeting scheduled
Details help capture the work, communication, and information that supports a specific activity.
Example: DigiMarketing LLC
The example below demonstrates how a single piece of information fits into the full Teamo hierarchy.
Organization
DigiMarketing LLC
Unit
Commercial
Module
Clients
Record
Nike
Activity Group
Campaigns
Activity
Summer Product Launch
Detail
Create social media assets
Visualized as a hierarchy:
DigiMarketing LLC
└── Commercial
└── Clients
└── Nike
└── Campaigns
└── Summer Product Launch
└── Create social media assetsBy looking at the detail "Create social media assets", we immediately know:
- It belongs to the Summer Product Launch campaign
- The campaign belongs to the Campaigns activity group
- The activity group belongs to the Nike client record
- The record belongs to the Clients module
- The module belongs to the Commercial unit
- The unit belongs to DigiMarketing LLC
This structure ensures that every piece of information has context and remains connected to the rest of your business data.
Different Businesses, Same Hierarchy
While the hierarchy always remains the same, the information stored within it can vary significantly depending on the type of business.
Marketing Agency
Client → Campaigns → Campaign → Tasks
Event Company
Event → Schedule → Session → Tasks
Recruitment Agency
Candidate → Interviews → Interview → Notes
Property Management Company
Property → Maintenance → Request → Tasks
Teamo's flexibility allows organizations to model their own processes while maintaining a consistent structure across the platform.
How to Think About the Hierarchy
A simple way to think about Teamo is:
- Organizations contain Units
- Units contain Modules
- Modules contain Records
- Records contain Activity Groups
- Activity Groups contain Activities
- Activities contain Details
Each level adds more structure and context to the information below it.
Next Steps
Now that you understand the hierarchy, continue with: