The four building blocks
Everything in Beebole revolves around four kinds of items:| Building block | What it represents | Examples |
|---|---|---|
| Projects | The work your team tracks time against | Client engagements, internal initiatives, departments |
| People | The users and team members in your account | Employees, managers, contractors, administrators |
| Tasks | The work items you plan, schedule, and assign | Deliverables, milestones, planned work |
| Tags | Labels that group and classify people, projects, and tasks | Departments, teams, locations, cost centers |
How everything fits together
The four building blocks don’t exist in isolation — they connect to create a complete picture of your organization’s work:- People work on projects — and tasks. When someone logs time, they select a project (and optionally a subproject), or a task: time can be tracked on tasks as well as projects. This is the core relationship in Beebole.
- Tasks are independent planning items, not parts of a project. Where projects model what hours go into, tasks model the work to be done. A task can optionally be linked to a project — which connects your planning and time tracking — but it exists on its own, with its own dates, owner, and status, managed in the Gantt chart and Kanban board.
- Projects have hierarchies. Categories contain projects, which can contain subprojects, nested as deep as you need.
- Tags group people, projects, and tasks. A tag like “Engineering” can contain the engineering team members, the engineering projects, and engineering tasks, making it easy to filter and report by department.
- Tags have hierarchies too. Tags can be organized into parent/child structures (e.g., “Europe” > “France” > “Paris office”).
Think of projects as what your team tracks time against, tasks as what you plan and schedule, people as who does the work, and tags as how you organize everything for reporting and management.
Shared configuration
Several features in Beebole aren’t tied to a single kind of item — they apply across projects, people, and tags. Understanding this pattern is key to configuring Beebole effectively.Billing and cost rates
Billing and cost rates can be set at multiple levels:| Level | What it controls |
|---|---|
| Organization | Default rates for the entire account |
| Tag | Rates for everyone and everything in a department or team |
| Project | Rates specific to a client or engagement |
| Person | Rates for an individual team member |
Work schedules
Work schedules define expected working hours per day across a repeating cycle. Like rates, they can be assigned at the organization, tag, or person level, and the most specific assignment applies. Learn more about work schedules.Custom fields
Custom fields let you add your own data to Beebole’s built-in records. You can create fields that appear on:- People (e.g., Employee ID, Office Location)
- Projects (e.g., Priority, Contract Type)
- Tasks (e.g., Sprint, Story Points)
- Time entries (e.g., Activity Type, Deliverable)
Assignments
You control which projects, tasks, absence types, and expense types are available to each person in their timesheet. These assignments can be managed at the organization, tag, or individual level. Learn more about assignments.How it all comes together
Here’s a typical setup to illustrate how these concepts connect:- You create projects organized by category (e.g., Clients or Internal) and engagement (e.g., Acme Corp or Website Redesign).
- You add people and assign them roles that control their permissions.
- You create tags for departments and teams, then tag both people and projects.
- You set billing rates on projects (what you charge clients) and cost rates on people (what they cost internally). Tags can provide default rates for entire departments.
- You assign work schedules to define expected working hours — at the organization level for most people, with overrides on specific tags or individuals.
- People log time against projects on their timesheets. Each entry captures who, what, when, and how long.
- Reports combine all of this — showing time, costs, billing, and budgets across any combination of projects, people, and tags.
Platform-wide features
A few features in Beebole apply globally, regardless of which section you’re working in.Search
Each list in Beebole — people, projects, tasks, tags, roles, custom fields, and other lists — has a Search by name field at the top of its panel. Beebole uses fuzzy matching, so typing characters that appear in order anywhere in a name returns a hit even when they’re not consecutive. Matched characters are highlighted in the results so you can confirm you’ve found the right record. Use the search field to:- Find anything by partial name. Typing
alibrmatches “Alice Brooks” and “Aliso Bridges”. - Filter long lists. Searching narrows hierarchies like the project tree, expanding only the branches that contain matching entries.
- Move through results with the keyboard. Press the up and down arrow keys to step through the filtered list, and Escape to clear the search and restore the full list.
Fast loading
Beebole caches your account data locally in your browser, so lists and timesheets appear near-instantly when you open a page. Beebole shows the cached data right away, then refreshes it from the server in the background. The local cache clears itself automatically when you switch organizations or when a new version of Beebole is deployed — you never need to clean it up manually.Real-time sync
Beebole keeps everyone in your account in sync without requiring a refresh. When a teammate creates, edits, archives, or deletes something — a project, a task, a time entry, an approval action, a journal message — the change appears for all other connected users within seconds. Real-time sync covers:- Record changes — Adds, edits, archives, deletes, renames.
- Approval actions — Submitted, approved, and rejected timesheets update for the approver and the submitter at the same time.
- Planning and Gantt updates — Task changes propagate to the planning view and the Gantt chart in real time.
- Journal messages and notifications — New mentions, replies, and notifications appear without polling.
Real-time sync uses a persistent connection between your browser and Beebole. If your network drops temporarily, Beebole reconnects automatically and catches up on any changes you missed while offline.
Undo and redo
Beebole lets you undo and redo most changes. Press ⌘+Z (Ctrl+Z on Windows/Linux) to undo, and ⌘+Shift+Z (Ctrl+Shift+Z) to redo. Undo and redo buttons also appear in the top bar whenever there is something to undo or redo. Bulk changes are grouped into a single operation, so one undo reverts the whole change rather than one piece at a time.Duplication
Most records in Beebole support a Duplicate action that creates a copy with the same configuration as the original. Use it to bootstrap a new project from a template or set up a person record similar to an existing one. To duplicate something, open the ⋯ action menu next to its name and select Duplicate. For example, duplicating a project copies its subprojects, settings, and relations, and places the copy under the same parent as the original. Historical data such as logged time stays with the original.Duplicating a person opens a small dialog where you enter a new name and email and choose a role before the copy is created. This is because each person needs unique identity fields.
Attribute copy and paste
In addition to duplicating an entire record, Beebole lets you copy a specific configuration block — billing rates, cost rates, budgets, or time-off allowances — from one record and paste it onto another. Use it to keep configurations consistent across similar projects, or to transfer one person’s allowance structure to a new hire. The basic flow:Open the source
Open the record whose configuration you want to copy (for example, a project with the right billing rate setup).
Copy the attribute
Click Copy on the configuration block. Beebole keeps it on an internal clipboard until you paste it.
Open the target
Open the destination — a different project, person, or tag, whichever supports the same kind of configuration.
You can only copy values set directly on a record. Inherited values can’t be copied — copy from the record where the value is actually defined.
Color coding
Beebole assigns each person, project, tag, and task a color used as a visual identifier across the interface. Avatars, list rows, planning blocks, and journal references share the same color, making it easy to scan a list, the planning view, or a Gantt chart and recognize who or what you’re looking at. The default color is generated automatically when a record is created. To change it, open the record and click its picture — or its colored initials — at the top of the detail panel, then pick a color from the palette. The same panel lets you upload a picture instead.Color is purely a visual aid — it does not affect access, permissions, billing, or reporting. Use it to make at-a-glance scanning easier, especially in shared views like planning, Gantt, or the journal.
Version update notifications
When a new version of Beebole is deployed, a banner labeled Update available appears in the interface. Click the banner (Click to reload) to reload the app and apply the latest version. This ensures you always have access to new features and fixes without needing to clear your cache manually.Related content
Quickstart
Set up your first project, team, and report in six steps.
Projects
Create and organize projects for your team to track time against.
People
Add and manage the team members in your account.
Timesheets
Track time on your projects and submit timesheets.
Open the source entity
Open the entity whose configuration you want to copy (for example, a project with the right billing rate setup).
Copy the attribute
Open the source’s action menu and select Copy. Beebole stores the attribute configuration on the clipboard until you paste it.
Open the target entity
Open the destination entity (a different project, person, or tag — whichever supports the same attribute).
Frequently asked questions
Do I need to set up all four building blocks before my team can track time?
Do I need to set up all four building blocks before my team can track time?
No. In Beebole you need at least one project and one person to start tracking time. Tags and tasks are optional — tags unlock powerful reporting, and tasks add planning on top of time tracking. See the Quickstart for the minimum setup.
What's the difference between a subproject and a task?
What's the difference between a subproject and a task?
Subprojects are part of Beebole’s project hierarchy — they subdivide a larger project for time tracking. Tasks are independent planning items with their own dates, owner, and status. A task can be linked to a project but exists separately, and is managed visually on the Gantt chart and Kanban board.
What's the difference between a tag and a project category?
What's the difference between a tag and a project category?
A project category is part of Beebole’s project hierarchy — it groups projects together. A tag is a cross-cutting label that can be applied to people, projects, and tasks. Use categories for your project structure and tags for organizational dimensions like departments, locations, or cost centers.
If rates are set at several levels, which one applies?
If rates are set at several levels, which one applies?
Beebole applies the most specific rate available for each time entry. For example, a rate set directly on a project overrides a default set on the organization. See Billing rates for how rates are resolved.
Can I change my structure after my team has started tracking time?
Can I change my structure after my team has started tracking time?
Yes. In Beebole you can reorganize projects, update tags, and change rates at any time. Historical time entries are preserved. However, structural changes may affect how existing data appears in filtered reports.