Skip to main content
Tasks is where you and your agents keep track of work. Open Tasks, the first item in the left sidebar, above Inbox. Every task has one person accountable for it, and optionally an agent doing it. When an agent needs something from you (an approval, an app connection, an answer or a review), it shows up in Needs you. Tasks is opinionated on purpose. Every workspace uses the same statuses, priorities and views, so a task means the same thing to everyone, people and agents alike.
Tasks is available in workspaces with agents and rooms. In other workspaces, tasks stay in Records, as before.
In chat replies, task identifiers such as LUM-42 appear as clickable mentions with the task’s status icon and title. Long titles are shortened to fit; hover to read the full title and identifier. Click a mention to open the task in a resizable panel beside the conversation. Your message draft stays in place. Close the panel to return to the conversation. Only tasks you can read show their title; unavailable references remain as written.

Find existing work

Ask an agent to find a Task by its identifier, title, or a description of the problem. Task search is available directly in the app and through Connie’s MCP connection, without first searching for a tool. For issue and duplicate investigations, an agent can search several descriptions together. It combines keyword matches with related meaning across the title and full description, including older closed Tasks unless a status filter narrows the search. The agent can then read promising Tasks and their comments before deciding whether they cover the work. Similarity does not merge or close Tasks; separate recurring assignments can remain separate. Results keep the workspace and conversation’s access rules. If indexing is still catching up or semantic search is unavailable, the result says so and keyword search remains available. An empty result during incomplete indexing does not establish that no similar Task exists. Ordinary browsing and exact identifier reads keep their existing behavior. If Task search cannot verify the workspace’s Tasks availability, it reports that the search is unavailable and can be retried. This does not mean no Tasks exist. Retry before deciding that work is missing or creating a duplicate.

A task

Release conditions

Release conditions are pending rollout. They appear only after the database capability has been activated.
Link a job Record to a Task, then choose Release conditions → Add conditions in its details. Select its saved Fields and comparisons. For example, require Paid amount ≥ Quoted amount and Written licence approved = Yes before releasing final files. All saved conditions must pass before the Task can enter In progress, In review or Done, or start delegated agent work. Task dependencies still apply separately. The detail panel refreshes the checks against current saved values. An inaccessible or deleted source blocks the Task and shows Source unavailable without disclosing its Fields or values. Missing values never count as payment or approval. Writing “paid” in a description does not satisfy a condition. Editors can change or remove conditions when their sources are available. Removing a condition removes its requirement. Conditions enforce Task transitions; they do not prevent someone delivering files outside the Task, and a source change does not automatically reopen completed work. Every Task is visible to every non-guest member of its workspace, including Tasks created earlier in rooms or agent DMs and all Tasks agents create in the future. There are no private Task visibility or sharing controls. A Task may remain associated with the conversation where it was created, but that does not change who can see the Task. Private conversations and linked Records keep their own access rules; being able to read a Task does not open its conversation. Non-guest workspace members can edit and comment on shared Tasks even when their source conversation is private. Tasks backed by a restricted Records source still require edit access to that source. Editing a Task does not grant access to its private conversation or unrelated files. Beside Subscribe or Unsubscribe in Activity, member avatars show who follows the task. Hover to read their names, or click the avatars to open the full subscriber list. Extra subscribers appear as +N in the compact stack. An empty list says No subscribers. Choose Subscribe to follow the task yourself, or Unsubscribe to stop following it. You can also ask an agent to subscribe or unsubscribe you from one specific task; it changes only your own activity subscription and confirms the saved state.

The views

Switch views using the tabs in the subheader. The subheader keeps the same height as you switch views. On narrower screens, list tools sit in a separate row and you can scroll the tabs horizontally; a fade at the edge shows there are more tabs. On a phone-sized list, rows give the title the room: the identifier and empty due-date slots are hidden (open the task to see its identifier or set a due date), and a set due date stays visible. Hover a row’s last-updated time, such as 2d, to see the exact date and time in your time zone. There is no separate Tasks navigation column. An agent can re-read saved Tasks, but its task tools cannot sign in as another member or verify that member’s account. An empty filtered search does not establish whether a Task opens for someone else or appears in All tasks. To verify this, ask an authorized member to sign in with their own account, select the same workspace and open each task link they are authorized to receive. Separately open Tasks → All tasks, clear filters and search each identifier. Record which account tested each task, whether its link opened and whether it appeared in the view. If you need to compare a room participant with a member outside the room, use a separately authorized tester in each group. Leave the tasks unchanged during the check. The Tasks item in the sidebar shows a red count when something needs you, and opens Needs you while it does. Tasks an agent files on its own wait in Triage status. Those meant for you appear in Needs you, with their suggested owner, agent, priority and reason. Accept one to move it to To do, or decline it. Use the Triage status filter in All tasks to see every triage task you can read. Lists are grouped by status by default. The icon buttons beside the tabs open Filter, Display options and Search tasks; hover or focus a button to identify it. Display switches between List and Board, groups by Status, Assignee, Agent or Priority (or not at all), and orders by Priority, Due date, Last updated, Created or Manual. You can also hide closed tasks or sub-tasks. Closed tasks show for 14 days after they close; find older ones with search. Search opens when clicked or when you press /, and matches titles, descriptions and identifiers. Pasting a long task title searches using its first 200 characters, without a loading error. In List view, click a row’s priority icon to choose a priority without opening task details. You can search the picker or use the arrow keys and Enter to select. You can also use Tab or Shift+Tab to focus an option, then Enter to choose it. Click the task title or row to open its details. In Assignee, search me to find yourself; people whose names contain those letters also match. In Filter → Labels, colored dots match the label colors shown on task cards. When you select an agent in New task, the message follows the starting status: Backlog waits until the task moves to To do, and Triage waits for acceptance into To do. The creation confirmation does not say an agent is working on a Backlog task. Needs you also supports Search tasks, Filter (F) and Display options. Search matches the tasks, request summaries, conversations and agent names in your accessible feed. Task filters apply to requests linked to matching tasks; requests without a task can match content or agent filters, but have no task status, assignee or due date. Waiting longest is the default ordering: requests you can decide come first, then the oldest waiting requests within each group. You can choose another ordering and return to Waiting longest. This view has no Board, grouping or closed-task display controls. Older saved Needs you display settings reset once to Waiting longest when this ordering update is introduced. Ordering choices made afterwards are remembered in this browser; display settings for other task views are kept. Press F or open Filter to choose a filter type, then choose its values in a separate searchable menu. You can filter by status, assignee, agent, creator, priority, labels, due date or content. Choose Creator → Created by me to find tasks you created. Typing a value such as “High” finds it directly across filter types. Type a sentence such as “high priority assigned to me” and select AI filter or press Enter to turn it into editable filters. Typing alone does not run AI. Click a filter chip’s values to change them, or its operator to exclude values. Labels support any, all or none of the selected labels. Advanced filter combines nested groups with all (AND) or any (OR). Today means your current calendar day; Next 7 days includes today and the following six days; Overdue finds still-open work before today. These dates follow your time zone. Filters are included in the address, so you can reload, go Back/Forward or share the filtered view with someone who has access. Clear removes the filters. Filters work in both List and Board. For an exact due date or a before/after date filter, edit the full date and press Enter or Tab to confirm. Changing one part of the date keeps the picker open. Leaving the picker also confirms a valid changed date; choosing a preset or search inside the picker does not confirm the draft. Escape dismisses an edited date without applying it. Board has no Cancelled or Duplicate columns. If your status filters contain only those statuses, use Switch to List in the empty state to see the matching tasks. Your filters are kept. Mixed filters still show the supported Board columns. On a Board, each card shows its status icon beside the task title. Click the status icon to choose a status, or the priority icon to choose No priority, Urgent, High, Medium or Low, without opening the task. Click the title to open the task. Priority changes appear while saving; a failed save reloads the saved value. Status changes update the card and column counts immediately while saving; a failed save restores the previous status. You can also drag a card into another status column to move it. The card follows your pointer without fading, and a placeholder shows its destination. Cards keep your selected sort order. With a card focused, press Space to pick it up, Left/Right to change column, Space to drop it, or Escape to cancel. Enter opens the task. With a status or priority button focused, Enter or Space opens its picker instead. Escape closes the picker and returns focus to its button. Read-only cards show the properties without edit controls. If a saved move cannot be refreshed, choose Retry refresh to reload the board without sending the move again. If Board cannot load task counts, it shows Could not load tasks with Retry instead of zero counts. A column that cannot load its tasks offers its own Retry, including when Show more fails. Cards already loaded stay visible when a later page fails. If a background count refresh fails, the last loaded cards and counts remain visible with a warning and Retry. Open a column’s three-dot menu and choose Hide column. It moves to Hidden columns, where its task count stays visible. Select a hidden column to show it again, or choose Show all to restore all hidden columns included by your current filters. Hidden columns are remembered with the view’s other display choices in this browser, including after switching between List and Board. Hiding a column changes only your display; its tasks and their statuses stay the same. Click a task to open it in a separate, resizable side panel, like an artifact. Drag the gutter to resize it; long titles wrap and remain fully visible as the panel narrows or widens. Close or Esc returns that space to the list. On narrow screens, the open task fills the available space. The More actions three-dot menu contains Copy link, Copy identifier and Open as page. Its address, such as https://connie.ai/<workspace-id>/tasks/LUM-42, can be shared with anyone who can see the task. Old links to tasks in Records open the same task here. Status, priority and assignee stay directly available. Choose an agent through Assignee; a selected agent and due date remain visible. Use More actions for Due date, Add sub-task, Add relation (Blocked by, Blocks, Related to) and Mark as duplicate…. The Add relation options stay open while you move the pointer onto them. The Due date picker opens beside the actions menu and switches sides when space is limited. Move between its row and the picker without closing it; a short pointer grace period protects the gap. Add sub-task is also available directly below the description. Empty relation sections stay hidden until you add one. Imported fields expands to show any read-only fields brought over from Records; Task information in a wide task view holds its creation and update times. Add sub-task opens an inline editor with a title, description, status, priority, assignee, labels and due date. The sub-task starts with the parent’s priority. It inherits the parent’s assignee when that person is you, or when every existing sub-task has that same assignee. Labels and the agent are chosen separately. The sub-task stays in its parent’s workspace and keeps its origin association. Create sub-task saves it and leaves the editor ready for the next one; hold Shift while clicking it, or press ⌘ Shift Enter / Ctrl Shift Enter, to keep the properties you chose. Cancel or Esc closes the editor without creating a task. A failed save keeps your draft available to retry. Deleting an open sub-task returns you to its parent in the same task panel or page after the deletion succeeds. The parent’s sub-task list updates to remove it. If deletion fails, the sub-task stays open so you can retry. Linked Records show their Object icons, names and links only when you can read their Object. Hovering or focusing a linked Record reveals Unlink. A Record you cannot read is left out; the task still opens if you have access to it. The comment field stays at the bottom of the task panel and grows as you type, through eight lines before scrolling. @ mentions someone or asks an agent. Enter posts the comment; Shift+Enter adds a new line. ⌘ Enter and Ctrl Enter also post. When the mention menu is open, Enter chooses the highlighted person or agent first. Enter confirms an active input-method composition without posting. Start a line with - or * for bullets, or 1. for a numbered list. Shift+Enter continues the list; press it on an empty item to leave the list. Tab nests an item, Shift Tab moves it out, and Backspace at the start of an item removes its marker or nesting. Posted comments keep their lists, including after reopening the task. Web links in a saved comment open in a new tab. To delete a task, open its More actions menu and choose Delete task. A confirmation dialog names the task: choose Delete task to confirm, or Cancel or Esc to keep it. A failed delete keeps the dialog open so you can retry. Undo on the success notification brings it back. A deleted task leaves every list, but its link still opens it, with Restore. The same goes for a task an agent deleted when you asked it to in a conversation: its reply links the task. Task comments and Request changes accept attachments. Click Attach files or paste an image directly into the field. Attach up to 10 files, up to 10 MB each. Images show a preview; documents stay as file links. Remove a draft attachment with ×. Wait for uploads to finish before commenting or sending changes; a failed upload offers Retry upload, and a failed send keeps the text and files for retry. Attachments can be sent without text. Saved files remain available when the task is reopened, only to people who can still read that task. When agent attachment delivery is enabled, mentioning an agent or sending changes back includes those files in its private conversation only when everyone there can also read the task. Editing a source comment keeps its copied files available to people who can still read the task and conversation. Changed access or a deleted source comment makes that copied context unavailable. An unavailable delivery keeps the send-back draft for retry; a newer review round requires reloading the task. Click a staged image or video to inspect it before sending. Videos in MP4, MOV or WebM format open with playback controls; if your browser cannot display the file, use Download to open it in another app. In Edit comment, use Attach files to add media or × to remove it. To replace a file, remove it and attach its replacement, then choose Save changes. Cancelling keeps the saved comment unchanged. Existing files are kept without uploading them again; an edit updates that same comment and does not ask an agent to run again. Agent comments keep their rich formatting: paragraphs and headings have space between them, and tables have padded cells, clear headers and borders. Wide tables scroll sideways inside the comment, including on small screens. This also applies when you reopen an existing task. Task descriptions, comments and Request changes use the shared rich editor. Start a line with - or 1. for a list; use ⌘ B / Ctrl B for bold and ⌘ I / Ctrl I for italic, or select text to open the formatting toolbar and add a link. Mention searches ignore case and stay open through spaces: @head of client finds Head of Client Delivery, and @delivery finds the same agent. Choose a result to save that person or agent’s identity. Lists, emphasis, links and mentions remain in the activity log and in feedback delivered to the assigned agent. Send back keeps ordinary Enter for new lines; Task comments keep Enter to post and Shift+Enter for a new line or list item. Start a comment line with [ ] followed by a space to create a checklist. Posted comments preserve checked and unchecked boxes without bullet markers. The saved boxes are display-only; use Edit comment to change their state. Task descriptions save automatically after typing pauses or when you leave the field. If a save fails, the description shows Description not saved and keeps your unsaved text while that task stays open. Restore your connection, then click Retry or click inside and leave the description again without retyping. Keep the task open until the save succeeds; unsaved text is not stored across a page reload. Open Comment actions on one of your own comments to choose Edit comment or Delete comment. Editing stays inline: Save changes or ⌘ Enter / Ctrl Enter saves the same comment, and Cancel or Esc keeps the saved version. Ordinary Enter inserts a new line while editing. Deleting asks for confirmation. A failed save keeps your draft available to retry; editing a comment does not ask an agent to work again. People and agents selected through the @mention picker while editing a comment keep their avatar and coloured name after Save changes and when the task is reopened. Editing updates the same comment and does not ask a newly mentioned agent to run. New comments posted by an agent show that agent as their author, including when several agents answer the same task. The person it works for stays separate from the author. A Workflow’s Comment as member choice and comments you post yourself keep their human authorship.

Recurring tasks

To create a fresh task on a schedule, open More properties (•••) while creating a task and choose Make recurring…. Choose the First due date, a repeat interval in days, weeks, months or years, and select a time zone from the searchable Time zone dropdown. Search by city or UTC offset, then choose a matching zone; typing a search does not change the saved selection. For an existing task, choose Make recurring… in More actions. The first task exists immediately. At 00:01 after its due date, Connie creates the next task with its next due date. Completing a task early leaves the schedule unchanged. Monthly and yearly repeats keep their calendar anchor, including month-end and leap-day dates. After an interruption, Connie creates one current occurrence instead of a backlog of missed tasks. Each occurrence has its own identifier, status, comments, review and agent work. Its description, starting status, priority, assignee, agent, labels, parent, conversation and linked Records come from the saved template. An assigned agent starts shortly after each task is created and hands its work back for review. Tasks in Triage wait to be accepted. Paused or unavailable agents never start automatically. A calendar-with-repeat-arrows icon identifies recurring tasks in lists, boards and Chat details. Click the repeat chip on a task, or choose Edit recurring task…, to change the future template and schedule. Existing tasks keep their own properties. Future edits use the schedule owner’s access. To change someone else’s schedule, choose Use my access and save to take it over; existing occurrences keep their original requester. Anyone who can edit the task’s scope can stop repeating. The Recurring tasks toolbar button also finds schedules whose earlier tasks are closed or deleted. Stop repeating leaves existing tasks intact; Resume repeating restarts the schedule. Deleting an individual task does not stop its schedule. Every occurrence is workspace-visible. Its original conversation association, source Object edit permissions and protected-file access rules are preserved. If the schedule owner loses access, an assignee or agent becomes unavailable, or a parent or label can no longer be used, the schedule shows Needs attention and retries hourly. Edit the template or stop repeating to resolve it. Recurring tasks and Routines are separate: recurring tasks create Tasks; Routines run an agent on a trigger. Scheduled routines use repeat arrows; event-triggered routines use a lightning icon.

Hand a task to an agent

Choose an agent in a task’s Assignee menu (under Agents), or ask another agent to create and assign it. An accepted To do assignment starts at once, even when its due date is later. The agent acknowledges pickup in the task’s room, or in your DM with it for a workspace task, and the task moves to In progress while it works. It reports blockers there and comments on the task. Open conversation and Stop remain available. When you stop the agent working on a task (in the chat, in Chat details or here), the task goes back to Backlog and its activity says the agent was stopped; it waits there until someone moves it to To do. Keep explicitly deferred work in Backlog; for a requested future start, ask for a routine that moves it to To do at that time. The generated assignment in a room or agent DM appears as a quiet system line, such as “Scout was assigned task CON-42.” The agent still receives the full task brief, and attached files keep their existing access. Comments you write and notes requesting changes remain your messages. When the agent requests completion, Connie checks the saved outcome and evidence. At 90% confidence or higher, verified work can move directly to Done. Otherwise it stays In review and appears in your Needs you. Missing evidence, a blocker, uncertainty or an explicit request for your review keeps human review in place. Open conversation opens the conversation where the agent worked, with the task in the panel on the right. You can read or comment on the task while keeping the conversation open. Close the task, or press Escape inside it, to return to the conversation. Waiting work keeps Open to decide, which opens its question, approval or connection card with the same permissions.
  • Approve marks it Done. Once the decision is saved, it leaves Needs you and the Needs you and sidebar counts drop with it, including when the list is filtered. A failed decision leaves the row and counts unchanged.
  • Request changes sends it back to the agent with your note, and the agent works on it again.
The agent’s own claim that it finished is not enough for automatic approval. External actions need verified receipts; a comment claiming that an email was sent or an account connected does not establish that it happened. To ask an agent something about a task without handing it over, mention it in a comment, for example @Scout can you check the attendee list?. The agent answers in the task. In a comment, a mentioned person shows their profile picture or initial and their name in blue, and an agent its avatar and name in its own color, both while you type and once posted.

Decide what waits on you

Accepting or declining a Triage task also removes its request and updates both counts after the decision is saved. Counts include all requests you can decide, even when your current search or filters hide some of them. New requests can increase the count when the list refreshes. When an agent’s work waits for an approval, an app connection or your answer, the request appears in Needs you with what it asks, for example Needs approval · Send email. Click Review & allow, Connect or Answer to open the conversation beside your list, where the card itself waits. Decide there, with the same rules as in the room: anyone who can post in a room decides its approvals, only the person whose account the agent uses connects that account, and only the person who asked answers a question. For a connection you can decide, Skip beside Connect skips that app without opening the conversation. It updates the connection card in chat and the agent continues as if you had pressed Skip there. If the request needs several connections, the others stay available until you connect or skip them. A request leaves Needs you once it’s decided, by you or by anyone else who can decide it, and when it expired or was withdrawn.

Keyboard

In Board, select a card with J/K, then use Enter/O to open it or S/P/A/Shift+D to open its property picker. These shortcuts also work after switching from List to Board. While a task dialog is open, background task shortcuts are paused. For example, J/K and P do not navigate or open a background task’s priority picker while you are in New task. Close the dialog to resume those shortcuts. In My tasks, clicking New task or pressing C assigns the new draft to you by default. You can change the assignee before creating it. In other views, both entry points leave the assignee for you to choose. Closing the new task dialog with Esc or by clicking outside keeps its draft while you stay in this workspace on the Tasks page. Reopening restores the title, description and properties you changed, including status, assignee and agent. An untouched dialog, or an empty next task after Create more, uses the new entry point’s defaults when reopened. After successfully creating a task and closing the dialog, the next draft also uses the defaults of the entry point you open it from. In the new task dialog, use More properties (the three-dot button) to set a due date. Press ⌘ Enter (or Ctrl Enter) to create, and check Create more to keep the dialog open for the next one. Close or Esc dismisses the dialog.

Agents and tasks in conversations

Ask an agent in any conversation to keep track of something, and it creates a task: “Make tasks for the follow-ups from this call”. It can also find tasks (“what’s overdue?”), change them, comment on them, link them to Records, mark duplicates, and subscribe or unsubscribe you from a specific task’s activity, using the same rules as you. In a conversation, an agent can only reach the tasks everyone there may see. Tasks you ask for directly normally start To do unless you choose another status. When an action requires a person’s own participation and an available authorized tool cannot perform it, that action belongs to the named person with no agent attached. Work an agent can perform may still be delegated and starts immediately when assigned To do. Work proposed by a routine, a responsibility or another agent still enters Triage, with its suggested assignee saved until someone accepts it. Explicit status and assignee choices are retained. What an agent is doing right now is work in progress, not a task. It creates a task for its own work only when you ask it to track something, or when the work goes beyond its reply, for example something it will come back to or that waits on someone; a quick answer leaves no task. A task it creates for itself has you accountable, and while it works on it the task is In progress. See Work in progress. An agent can put files from the conversation on a task. Send a screenshot, a screen recording or a document with your message and ask for the task: the agent copies the file onto the task, where it appears in a comment, with images shown inline. It attaches up to 10 files of up to 10 MB each (images, MP4, MOV or WebM video, PDF, text, CSV, JSON, Word, Excel or ZIP), to a new task or to an existing one. Everyone who can read the task can open them. An agent also sees who a task was created for, so it can send a task back to the person who reported it. A conversation’s tasks are listed in its Chat details, under Tasks: Tasks associated with it and Tasks an agent worked on there and, in your DM with an agent, the tasks delegated to that agent. Every open task is listed; closed ones show while there are four or fewer, and behind Show N done past that. While an agent works on one of them in the conversation, the task shows under In progress instead, with its identifier, and comes back to Tasks when that work ends. Click a task to open it in the panel, and Back to chat details to return. + beside Tasks creates a task in the conversation. Agent routines remain under Routines, with repeat arrows for schedules and a lightning icon for event triggers, in both the list and detail header. Open a routine to inspect its trigger and, where permitted, its prompt. Its active run appears under In progress. If you ask for a task when an Inbox reply arrives, the follow-up creates it in the room or agent DM where you asked and assigns it to you. Its source conversation keeps its own access rules. The Task is workspace-visible. If you no longer have access to the source conversation, the conversation is read-only, or the follow-up came from an older History chat, the Task is not created from that unavailable source. When a change needs approval, the tasks and changes shown are kept for that action. New matching tasks do not join while it waits. If a task, related task or label changes, or access is removed, the action stops so you can prepare it again. A batch either finishes together or changes nothing. Retrying the same action returns its existing result rather than applying it twice. Task history records the changes; these actions do not offer automatic undo.

Guests and privacy

Guests cannot read or change workspace Tasks. Imported Tasks retain their source Object’s edit restrictions; linked Records and protected files still require their own read permission. Notifications and routines recheck current workspace Task access. A Task associated with a private room or agent DM remains workspace-visible, while that conversation and its transcript remain private.

Tasks around Connie

A person’s, company’s or deal’s page lists the tasks linked to it, open ones first, and Create a task there opens New task with that Record linked. The Tasks column of People and Deals shows linked workspace tasks; linked Records and their grids retain their own read permissions. Search (⌘K or Ctrl+K) finds tasks by title, description or identifier, such as LUM-42 or #42. In Inbox, Create task drafts a task from the conversation. An approved meeting action creates its task here, and an approved Update task changes the task here, as you. Deleting a deal can also delete the tasks linked to that deal alone. A List built on the Records Tasks Object points here instead of showing old copies of your tasks. Workflows and agent routines start on these tasks with the Task events (Task Created, Task Updated, Task Assigned, Task Status Changed, Task Completed, Task Due Soon and Task Overdue), filtered by Status, Priority, Assignee or Agent: see Triggers. Task events also apply to Tasks associated with rooms or agent DMs.

Tasks in Records and analytics

In workspaces where Tasks still uses Records, creating a task from a Kanban status column’s + fills that status. With Create more enabled, each new blank task in the same dialog starts with that column’s status and the view’s seeded assignee too. For example, two tasks created from Backlog both start in Backlog unless you change their status before creating them. After a task has come over, change it in Tasks. Older Records controls cannot update or delete its old copy; a request that includes an already moved task stops without applying the batch. New tasks waiting to come over keep their existing import path, and workflow approvals stay approvals. Turning Tasks off does not make an old copy editable. In the Workflow builder, Update a record’s fields does not offer the Tasks Object or its Lists as targets. Use Edit task to change a task. An older step’s saved Tasks target remains visible when you open its settings; replace that step with Edit task rather than selecting the old target again. After the existing tasks have come over, Records reads current task titles, descriptions, status, priority, assignee and dates. Saved filters and sorts on those fields use the current task values. Fields outside that fixed set stay under Imported fields on the task; custom, relation and historical cell queries are unavailable in the Records task projection. Task analytics counts an open task as overdue only when its due date is before today in your time zone. Tasks due today or tomorrow are not overdue. The Tasks Object and its unfiltered default List support current count, field and percentage analytics, including grouping and filters on the fixed fields offered in the picker. Custom List analytics, history trends and task relation or traversal analytics are unavailable. Saved requests for unsupported fields report that limit instead of showing old Records values. The Tasks column and Tasks Object analytics include workspace tasks only. Next action at follows the Record’s Tasks section: it can also use an open dated task from a room or agent DM that you can currently read. Both keep the linked Record and source Object access checks.

Your existing tasks

The first time someone opens Tasks in a workspace, its tasks from Records come over automatically, with their comments, labels, linked Records, sub-tasks and blocked-by links. A large workspace’s tasks can take a few moments; the page says so while they arrive. If you try to save a change or ask an agent to work before this finishes, Connie asks you to retry shortly and starts no new work. Fields that Tasks doesn’t have are kept under Imported fields on each task. Example tasks from onboarding that nobody changed are left behind, and so are the requests of the older Human Approval workflow step: they stay approvals, decided as before. Once a task comes over, change it in Tasks or through an agent’s task tools. An older Records action that tries to change the imported copy stops and asks you to refresh, so it cannot overwrite changes made in Tasks. Records that have not come over yet keep their existing behavior. Imported labels keep their source Object’s access rules. A workspace label created separately remains shared workspace taxonomy. A same-named imported label stays separate; choosing or editing it does not make it a workspace label. An imported label can be used on tasks imported from that Object and on fresh occurrences of their recurring series. The series keeps the same source Object authority; the label never becomes workspace-wide. The label menu identifies imported and workspace labels. To use a new shared name elsewhere, choose Create workspace label explicitly; an agent does not silently turn an imported label into a workspace label. Import progress says whether tasks are still arriving without exposing counts from an Object you cannot read.