Understanding Rows: Records, Activities, and Details
Every piece of information in Teamo is stored as a row.
Whether you're managing clients, projects, employees, events, invoices, campaigns, or tasks, the information you create in Teamo will be stored as one of three row types:
- Records
- Activities
- Details
Understanding the difference between these row types is one of the most important steps in designing an effective Teamo system.
What is a Row?
A row is a single piece of information stored in Teamo.
Every Record, Activity, and Detail counts as a row and contributes to your workspace's total row allocation.
For example:
- Client Record = 1 row
- Campaign Activity = 1 row
- Task Detail = 1 row
Total = 3 rows
Unlike many platforms, Teamo does not limit the number of rows within a specific Module. Instead, row capacity is managed at the account level based on your subscription plan.
This allows businesses to keep information together in larger, more connected datasets rather than splitting it across multiple Modules.
The Three Types of Rows
Teamo uses three row types:
- Records
- Activities
- Details
Each serves a different purpose and represents a different level of information.
Records
Records represent the primary entities you manage.
These are typically the most important items within a Module and often have the longest lifecycle.
Examples
Clients Module:
- Nike
- Spotify
- Coca-Cola
Events Module:
- Annual Marketing Summit
- Product Launch Event
Employees Module:
- John Smith
- Sarah Johnson
Properties Module:
- Building A
- Building B
A Record is usually something your business actively manages over time.
Activities
Activities represent information, work, events, transactions, or objects related to a Record.
Activities help break a Record into smaller, more manageable pieces.
Example
Record:
- Nike
Activity Groups:
- Contacts
- Invoices
- Brand Assets
- Campaigns
- Reports
Activities:
- Contacts:
- John Smith
- Sarah Johnson
- Campaigns:
- Summer Product Launch
- Black Friday Campaign
- Invoices:
- January Retainer
- February Retainer
Activities provide structure and allow large Records to remain organized.
Details
Details represent the most granular level of information in Teamo.
They typically contain tasks, notes, updates, files, comments, interactions, or supporting information related to an Activity.
Example
Record:
- Nike
Activity Group:
- Campaigns
Activity:
- Summer Product Launch
Details:
- Create social media assets
- Design landing page
- Approve campaign budget
- Schedule launch meeting
Details allow teams to capture the work and information that supports an Activity.
A Complete Example
The example below demonstrates how all three row types work together.
Record:
- Nike
Activity Group:
- Campaigns
Activity:
- Summer Product Launch
Details:
- Create social media assets
- Design landing page
- Schedule launch meeting
In this example:
- Nike is a Record
- Summer Product Launch is an Activity
- Each task is a Detail
Total rows created:
- 1 Record
- 1 Activity
- 3 Details
Total = 5 rows
Which Row Type Should I Use?
When designing a system, ask yourself the following questions.
Is this a primary business entity?
If yes, it is likely a Record.
Examples:
- Client
- Employee
- Event
- Property
- Product
- Vendor
Does it belong to a specific Record?
If yes, it is likely an Activity.
Examples:
- Contact
- Campaign
- Invoice
- Attendee
- Maintenance Request
- Meeting
Is it a task, note, update, file, or piece of supporting information?
If yes, it is likely a Detail.
Examples:
- Create social media assets
- Follow-up call completed
- Proposal uploaded
- Budget approved
- Meeting notes added
Different Businesses, Same Structure
The information may vary, but the structure remains the same.
Marketing Agency
- Client Record: Nike
- Campaign Activity: Summer Product Launch
- Detail: Create social media assets
Event Company
- Event Record: Annual Marketing Summit
- Attendee Activity: John Smith
- Detail: VIP ticket purchased
Recruitment Agency
- Candidate Record: Sarah Johnson
- Interview Activity: Final Interview
- Detail: Strong communication skills noted
Property Management Company
- Property Record: Building A
- Maintenance Request Activity: HVAC Repair
- Detail: Technician scheduled for Friday
Best Practices
Keep primary entities at the Record level
Clients, projects, employees, products, properties, and events are usually best managed as Records.
Use Activities to organize related information
Activities help break large Records into logical groups of information and work.
Use Details for execution
Tasks, notes, comments, updates, files, and interactions are often best managed as Details.
Let the hierarchy provide context
One of the biggest advantages of Teamo is that every row automatically inherits context from the levels above it.
- A Detail belongs to an Activity.
- An Activity belongs to an Activity Group.
- An Activity Group belongs to a Record.
- A Record belongs to a Module.
This makes it easier to report on information, build automations, control permissions, and understand how work relates to the rest of your business.
Start simple
If you're unsure where something belongs, start with the simplest structure possible.
As your process grows, you can always add additional Activities, Details, fields, automations, and relationships.
Next Steps
Now that you understand how rows work in Teamo, continue with: