Features / Tasks That Live Beside the Records They Belong To
Tasks

Tasks That Live Beside the Records They Belong To

Assign a task, set a due date, get a reminder. The task sits on the customer or job it belongs to.

Nobody should have to open a separate task app to find out what a client is waiting on.

Task management database with record task panel
A task opened from a project record. The owner, due date and reminder sit beside the data the task refers to, and the discussion stays with it.

A task about a customer should live on that customer

Teams keep their data in one place and their to-do list in another. So the task says follow up with Northwind, and finding out what Northwind is actually waiting on means opening a second app and hoping the link in the task still points somewhere.

A task in InfoLobby can be attached to the record it is about. Open the customer and the outstanding work is right there, with its owner, its due date, its reminder and whatever was said about it. Nothing to keep in sync, because there is only one copy.

The task should not become another place to maintain context.

A task like 'follow up' is only useful if the person can see what they are following up on. InfoLobby keeps the action next to the record, so ownership and context travel together.

  • Attach tasks to records or keep them standalone when needed
  • Use due dates, reminders, assignment, and comments
  • Keep due work visible from the main app header

What a task carries

  • Use tasks for personal reminders or team handoffs
  • Add due dates and optional timed reminders
  • Keep task comments with the work item itself
  • Access record-scoped tasks through the public API

Putting tasks where the work is

  1. Attach tasks to the records that need action: customers, requests, projects, assets, or approvals.
  2. Assign owners, due dates, reminders, and comments without copying context into another task app.
  3. Use the task views and header badge to keep due work visible across the team.

Where it fits

Use it for

  • Data-centric follow-up where the task only makes sense beside the record
  • Small teams that need assignments, reminders, and comments without another work app
  • Sales, client delivery, support, and ops workflows with record-linked next steps

Reach for something else when

  • Teams needing advanced project planning, sprint boards, or portfolio management
  • Personal productivity workflows that do not involve shared business records

Questions people ask

Can tasks exist without being attached to a record?

Yes. InfoLobby supports both standalone tasks and record-linked tasks.

Do tasks support reminders and comments?

Yes. Tasks support due dates, reminder timing, assignment, and their own comment thread.

Try it on your own data

Start free and build one working process around this feature, then add the records, views, tasks and automations around it.