How data flows between suite apps

One organization, one data plane

The biggest advantage of a connected suite over a bag of separate tools is that you don't re-enter the same information in every app. In StretchSuite, all of your apps operate on the same organization-scoped data plane through the workspace gateway. A customer, a contact, a domain, or an audience isn't trapped inside one app — it's a record belonging to your organization that multiple apps can reference.

The unit that ties everything together is your organization (tenant). Every record, connection, and entitlement is scoped to it, and the gateway guarantees that data never crosses between organizations. That single boundary is what makes sharing safe.

What "shared" actually means

It's less that apps copy data to each other, and more that they read and write against the same backend, scoped to your org:

• A customer captured at StretchShop checkout is an organization record that StretchCRM can treat as a contact and StretchMail can add to an audience.
• A verified domain you set up in StretchMail (or Domains) can serve email, while the same domain concept underpins where your StretchWP or StretchSites content lives.
• Contacts in CRM can become recipients in Mail campaigns.
• Entitlements (what you've purchased) are read the same way by every app, so access is consistent across the launcher, the app, and admin surfaces.

Because each app exposes an organization-scoped client surface through the gateway, they all speak the same tenancy language.

How the boundary is enforced

Every data request carries the caller's authenticated organization, derived server-side from the session (never from the browser). So:

• App A in Org 1 can only ever see Org 1's data.
• Switching your active workspace to Org 2 changes what every app sees, consistently.
• One tenant cannot read another's records even by tampering with requests.

This is why cross-app sharing doesn't create a privacy risk: sharing happens within a tenant, and the tenant wall is absolute.

A realistic example: a purchase becomes a relationship

A coaching business runs Shop, CRM, and Mail:

1. A customer buys the workbook in StretchShop. A Customer record is created under the organization.
2. Because it's an org-level record, that buyer shows up as a contact the business can manage in StretchCRM — no re-typing their details.
3. The business adds recent buyers to an audience in StretchMail and sends a follow-up sequence from their verified domain.
4. Replies route back through StretchMail's inbound handling into the right inbox.
5. All of this stays inside the Payne Coaching organization; a different org on the platform sees none of it.

One action (a purchase) rippled across three apps without duplicate data entry, because they share one tenant-scoped data plane.

Designing cross-app workflows

To take advantage of shared data:

1. Decide your system of record for each concept — e.g., Shop owns orders, CRM owns the relationship, Mail owns sending.
2. Set up the connections each app needs (payments for Shop, a verified domain for Mail, social connections for Social).
3. Let records flow forward rather than exporting/importing — buyers become contacts become recipients.
4. Use webhooks where you want real-time reactions (a new order triggering a follow-up).
5. Keep everything under the right organization — the whole model depends on acting in the correct workspace.

Troubleshooting

"I created a record in one app and can't see it in another" — confirm you're in the same organization in both. Cross-org expectation is the #1 cause. Also confirm the second app is actually meant to surface that record type.

Data looks empty in an app — you may have no records of that type yet, or you're viewing a different organization. Distinguish empty from error.

A teammate sees different data — their role or their selected organization differs. Check membership and active workspace.

Sync feels delayed — some propagation between apps is event-driven (webhooks); brief delays are normal, sustained ones are worth reporting.

Tips

• Pick one system of record per concept to avoid conflicting edits across apps.
• Always verify your active organization before concluding data is "missing."
• Lean on the shared model — the point of a suite is that a customer, contact, and recipient can be the same underlying person.

FAQ

Can other companies on StretchSuite see my data? No. Everything is scoped to your organization, enforced at the gateway. Cross-tenant access is not possible.

Do apps duplicate my data? They largely share org-scoped records rather than maintaining separate copies, which is why you don't re-enter the same details.

What if I belong to multiple organizations? Each is a separate tenant with its own data; switch your active workspace to move between them.