Creating Your First Module
Modules are the foundation of every system built in Teamo.
A Module is used to manage a specific business process, such as sales, projects, events, inventory, recruitment, support tickets, customer relationships, or employee management.
This guide will walk you through creating your first Module and explain the key decisions you'll make along the way.
Before You Begin
Before creating a Module, ask yourself:
What process am I trying to manage?
Examples:
- Managing leads and opportunities
- Managing clients
- Managing projects
- Managing events
- Managing employees
- Managing support requests
Each major business process should typically have its own Module.
Step 1: Choose a Unit
Every Module belongs to a Unit.
Navigate to the Unit where you'd like to create the Module.
Examples:
- Operations
- Commercial
- Marketing
- Finance
- London Office
- Tokyo Office
If you haven't created a Unit yet, see: Understanding the Teamo Hierarchy.
Step 2: Create the Module
Click Add Module.
Choose:
- Module Name
- Icon
- Color (if enabled)
- Permissions (optional)
Examples:
- Leads
- Clients
- Projects
- Events
- Employees
- Inventory
Once created, your Module will appear in the left navigation menu.
Step 3: Define Your Records
Think about the primary items you'll be managing.
These will become your Records.
Examples
Module: Clients
- Nike
- Spotify
- Coca-Cola
Module: Events
- Annual Conference 2026
- Product Launch Event
- Customer Workshop
Module: Employees
- John Smith
- Sarah Johnson
- Michael Lee
Step 4: Add Record Fields
Fields help you store information about each Record.
Common examples include:
- Name
- Status
- Owner
- Priority
- Budget
- Start Date
- End Date
- Category
The fields you create should reflect the information your team needs to track.
Step 5: Create Activity Groups
Activity Groups help organize related information inside each Record.
Example: Clients Module
Activity Groups:
- Contacts
- Invoices
- Brand Assets
- Campaigns
- Reports
Example: Events Module
Activity Groups:
- Schedule
- Contractors
- Attendees
- Budget & Expenses
- Equipment
Step 6: Add Activities
Activities are the individual items that live inside an Activity Group.
Example
Client: Nike
Activity Group: Campaigns
Activities:
- Summer Product Launch
- Black Friday Campaign
- Product Awareness Campaign
Step 7: Start Collaborating
Invite team members, assign work, upload files, add updates, build dashboards, create automations, and start managing your process.
As your business evolves, your Module can evolve with it.
Example: Building a Simple Client Management Module
- Unit: Commercial
- Module: Clients
- Record: Nike
- Activity Group: Campaigns
- Activity: Summer Product Launch
- Detail: Create social media assets
Within minutes, you have a structured system for managing client work inside Teamo.
Best Practices
Think in systems, not isolated lists
Modules are designed to represent complete business processes and datasets, not individual projects, teams, locations, or short-term initiatives.
In many platforms, businesses end up creating multiple boards, databases, or workspaces to manage the same type of information because of record limitations, permission restrictions, or performance concerns.
Teamo is designed differently.
A single Module can contain all of your clients, projects, events, employees, properties, products, or other business records while still supporting reporting, permissions, automation, and collaboration at scale.
Less is more
One of the most common mistakes when setting up a new system is creating too many Modules.
Before creating a new Module, ask yourself:
"Is this a different business process, or simply another record within an existing process?"
For example
Recommended:
- Leads Module
- Clients Module
- Events Module
Usually not recommended:
- London Clients Module
- Tokyo Clients Module
- Enterprise Clients Module
- Small Business Clients Module
These would typically be better managed through records, views, filters, permissions, teams, or custom fields within a single Clients Module.
A smaller number of well-designed Modules almost always leads to a better system.
Use Modules as connected datasets
Modules become most powerful when they are connected to one another.
Examples:
- Leads linked to Clients
- Clients linked to Events
- Employees linked to Time Off Requests
- Projects linked to Invoices
- Properties linked to Maintenance Requests
Building fewer, more connected Modules creates a more complete operational system and makes reporting, automation, and collaboration significantly easier.
Record limits are managed at the account level
Teamo does not impose limits on the number of records within a Module.
Instead, capacity is managed at the account level through your allocated rows.
This means there is rarely a need to split information across multiple Modules simply because a dataset has grown.
Organize information for discoverability
A good rule of thumb is that anyone on your team should know exactly where to find a specific type of information.
If client information exists in five different Modules, reporting becomes harder and information becomes fragmented.
If all client information exists in a single Clients Module, it becomes easier to search, report on, automate, secure, and maintain.
Build for the future
When designing your system, think about how it will look when you have:
- 10 users instead of 2
- 1,000 records instead of 100
- Multiple teams working together
- More automation
- More reporting requirements
In most cases, a smaller number of well-structured, connected Modules will scale far better than a large number of isolated ones.
Teamo Tip: If you're creating a new Module because of location, department, client type, record volume, or permissions, there is often a better solution using fields, views, permissions, teams, linked records, or portals.
Next Steps
Now that you've created your first Module, continue with: