Connecting StretchTasks Across the Suite

Overview

StretchTasks isn't an island. Because it's part of StretchSuite, a task can be linked to the thing it came from — a CRM client or contact, a platform project, a meeting, or a conversation. That connection means a task carries its context, and work created elsewhere in the suite can land in StretchTasks automatically.

What a task can connect to

A task can hold links to other parts of your suite, including:

• Client and contact — the customer or person a task relates to (from your CRM).
• Platform project — a project defined elsewhere in the suite that this task rolls up to.
• Meeting — the meeting a task came out of (for example, an action item from a call).
• Conversation — a message thread a task was raised in.
• Source app — which app the task originated in, so you can tell a manually-created task from one generated by another suite app.

How tasks arrive from other apps

Work doesn't only get typed into StretchTasks. Other suite apps can create tasks on your behalf and stamp them with where they came from — a follow-up generated from a CRM contact, an action item captured from a meeting, or a step created from a project. When that happens, the task appears in your normal views with its source recorded, so you always know its origin.

Tenancy note: These cross-app links are set by your team through the suite and admin integrations. The customer workspace deliberately keeps direct task creation simple and scoped to your own organization — you create plain tasks there, while richer cross-app linkage is established on the admin/integration side. This is a security boundary: it ensures one organization can never read or write another organization's tasks.

Steps: work with a connected task

1. Open a task that originated in another app (look for its source indicator).
2. Use the linked contact, project, meeting, or conversation to jump back to the full context.
3. Triage it like any other task — set status, priority, due date, and a project home.
4. Complete it in StretchTasks; the completion is recorded here as the system of record for the task itself.

Concrete example

During a client call in your suite's meeting app, someone captures the action item "Send Acme the revised SOW." It arrives in StretchTasks as a task linked to the meeting it came from and the Acme contact. Your account manager opens it, sees it's tied to that meeting, sets it to Today with High priority, sends the SOW, and completes it — all without re-typing the context or losing the thread back to the call.

Tips

• When a task's origin matters, keep its suite links intact — they're your shortcut back to the full story.
• Use the source stamp to tell auto-generated tasks from ones you created by hand.
• Because StretchTasks is the system of record for task state, complete and update tasks here rather than in the originating app.

FAQ

Can I link a task to a contact myself from the customer workspace? The workspace focuses on straightforward, org-scoped task creation. Rich cross-app linking (to contacts, projects, meetings, conversations) is established through your team's admin and suite integrations.

Will other orgs see my tasks because they're connected to the suite? No. Tasks are strictly organization-scoped — every read and write is filtered to your organization, so cross-app connections never expose your tasks to another tenant.

What is the "source app" on a task? It records which app created the task. A task you type in StretchTasks shows StretchTasks as its source; a task generated elsewhere shows that app, so its origin is always clear.