# From a message to a Task without losing the conversation

> How a small request in chat becomes work someone can own and review in L4.

Source: https://llll.gg/blog/from-message-to-task

A lot of work begins as a message: “Can someone update the onboarding guide?” The hard part is not recognizing that it is work. It is remembering who took it, where the discussion went and what happened next.

L4 lets a Member create a Task from a message in a Channel, Direct Message or Thread. The Task form starts with information from the message, and the saved Task links back to its source. The conversation can continue while the work gets an owner and a place in a Board.

## Keep the context, respect the boundary

The link is useful when someone needs to understand why a Task exists. It does not make a private conversation public. A person who can read the Task but cannot read the source conversation sees that it came from a message, without receiving the source conversation's contents. If the original message is deleted, the Task remains and its source is shown as deleted.

A Task can be assigned to a person or used with an Agent Run. Those are different responsibilities: the Task records the work, while a Run is an attempt to carry it out. The result still needs a person to judge whether it solves the original problem.

## Find what needs you

The Server's Inbox brings together items that need the signed-in Member, including assigned Tasks and Tasks they created that are waiting for review. It also includes mentions, relevant Agent work, unread chats and accessible unread Mailboxes. The point is to make the next action visible without turning every conversation into a permanent notification.

The most useful workflow to test is a real one: create a Task from a request, assign it, discuss the result and check what a teammate with different access can see. Small details in that path matter more than how many task features fit on a list.