> ## Documentation Index
> Fetch the complete documentation index at: https://docs.parable.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Week of March 15 – 21, 2026

> What's new this week: Salesforce support reaches production, credential error messages get clearer, and broken connectors now page the people who can fix them.

<Tabs>
  <Tab title="Platform" icon="layer-group">
    <Info>
      **Platform is the composable core of Parable.** Everything here has been seen across enough customers, long enough, that we're confident it behaves the same way for yours. We move things into Platform deliberately — a great composable platform takes patience to build, and we'd rather be right than fast at this layer. If something's in Platform, it's production, stable, and ours to keep steady.

      <br />

      **How to read Platform results:** this is the bedrock.
    </Info>

    ### <Icon icon="sparkles" /> New

    <AccordionGroup>
      <Accordion title="Salesforce is fully supported" icon="cloud" defaultOpen>
        <Badge>Direct impact</Badge>

        * The Salesforce connector is now production-ready, covering the core objects most teams rely on — users, accounts, opportunities, contracts, tasks, and more.
        * Syncs run incrementally with cursor-based pagination, so large orgs don't re-pull everything on every sync.
        * If you asked us for Salesforce and were on the waitlist, reach out to your Parable team — we can enable it for your workspace.
      </Accordion>

      <Accordion title="You'll hear about broken connectors immediately" icon="bell">
        * When a connector transitions from healthy to a problem state — expired credentials, failed syncs, invalid config — the integrator owners on your team now receive an email and a Slack notification automatically.
        * No more finding out at your next dashboard review; the right person hears about it as soon as it happens.
      </Accordion>

      <Accordion title="Large credentials (like Google service account keys) now work end-to-end" icon="lock">
        * Some integrations — most notably Google Workspace service account keys — rely on credentials that are too large for classic single-pass encryption.
        * Parable now uses a layered encryption approach that removes that size limit entirely, so these credentials are handled cleanly during setup.
        * You shouldn't notice anything different during connector setup — it just stops being an edge case.
      </Accordion>

      <Accordion title="Admins can mark connectors as Required or Suggested" icon="list-check">
        * Your Parable team can now indicate which connectors matter most for your workspace — Required (we need this to get you value) or Suggested (nice to have).
        * You'll see the priority in the connector directory, so setup feels like a checklist instead of a menu.
      </Accordion>
    </AccordionGroup>

    ### <Icon icon="arrow-trend-up" /> Improved

    <AccordionGroup>
      <Accordion title="Clearer messages when a credential issue happens" icon="circle-alert">
        * Credential-related errors used to come in four flavors that sometimes pointed in the wrong direction (for example, asking you to fix your credentials when the issue was on our side).
        * Now there's one clean **Credential issue** state with the specific reason shown on demand, a separate **Config issue** state for configuration mismatches, and a new **Internal issue** state for the rare cases where the fault is ours — so you never see "please reconnect" when reconnecting wouldn't help.
      </Accordion>

      <Accordion title="Data freshness checks understand your pipeline shape" icon="database">
        * Parable's "is this data current?" guard now knows the difference between connectors that refresh everything on every sync and connectors that load incrementally.
        * Practical effect: fewer false "this looks stale" flags on datasets that were always fine — especially for incremental loads that were being compared against the wrong benchmark.
      </Accordion>

      <Accordion title="Google Workspace service-account keys are more forgiving" icon="key">
        * If a pasted Google service account key contained escaped newline characters (common when credentials round-trip through a text editor), setup used to fail with an opaque error.
        * Parable now normalizes that automatically — the credential just works.
      </Accordion>

      <Accordion title="GitLab user sync stays inside your organization" icon="users">
        * Connecting GitLab used to trigger an extra-long first sync on large instances, because we were pulling every visible user across the platform, not just your team.
        * Defaults now scope user ingestion to members of your groups — meaningfully shorter first sync for GitLab workspaces of any size.
      </Accordion>

      <Accordion title="Small UI polish across the connector experience" icon="paintbrush">
        * Connector schedules no longer show a "next run" in the past on freshly-reconfigured integrations.
        * Breadcrumb paths with accidental duplicates (e.g. "Jira → Jira") are deduplicated.
        * Redundant timestamp clutter on connection cards removed.
      </Accordion>
    </AccordionGroup>

    ### <Icon icon="wrench" /> Fixed

    <AccordionGroup>
      <Accordion title="A batch of data-pipeline quality fixes" icon="shield-check">
        * Several underlying fixes to keep data flowing cleanly after our recent connector-metadata update — primarily for workspaces using **Zoom**, **Salesforce**, and **Google Workspace** integrations.
        * If you were seeing intermittent issues on any of those, you should see them resolved.
      </Accordion>

      <Accordion title="Form state resets cleanly when you close a setup dialog" icon="wrench">
        * A small but noticeable quality-of-life fix — closing and re-opening a connector setup flow no longer carries over stale form values from the previous attempt.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Preview" icon="flask">
    <Info>
      **Preview is where we put features we're confident in, but haven't yet seen at full scale across every organization.** The most common reason: the AI models from Google, OpenAI, and Anthropic that underpin classification update on their own schedule, and the methods we layer on top learn your organization over time. That means Preview results can shift slightly week-to-week — **within a margin of error, rarely enough to flip a decision you'd make from them.** When we've seen consistent results across enough organizations for long enough, a Preview feature graduates to **Platform**.

      <br />

      **How to read Preview results:** decision-ready with an honest caveat. We'll tell you when the methodology under a Preview feature changes.
    </Info>

    ### <Icon icon="sparkles" /> New

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      No new Preview launches this week — watch for Time Spend moving to its permanent home in early April.
    </Card>

    ### <Icon icon="arrow-trend-up" /> Improved

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      Nothing to call out in Preview this week.
    </Card>

    ### <Icon icon="wrench" /> Fixed

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      No Preview-specific fixes this week.
    </Card>
  </Tab>

  <Tab title="Labs" icon="flask-vial">
    <Info>
      **Labs is where we deliver insights tailored to your organization faster than our main roadmap would allow.** A Labs report is built for your team specifically, leans on the newest AI capabilities, and may ship with less visual polish than the rest of Parable — because the value is in the insight, not the chrome. Results may evolve as the underlying models improve; that's intentional — we're moving with the frontier, not chasing it. Once a Labs capability proves itself across several organizations, it graduates to **Preview**.

      <br />

      **How to read Labs results:** directional.
    </Info>

    ### <Icon icon="sparkles" /> New

    <AccordionGroup>
      <Accordion title="Groundwork for new Labs environments" icon="flask-vial" defaultOpen>
        * We stood up a new dedicated Labs environment this week for a customer partner, with its own secure subdomain, authenticated access, and read-only access to their data.
        * This is foundational work for the pattern we use to bring Labs capabilities to more teams — expect more environments in this shape over coming weeks.
      </Accordion>
    </AccordionGroup>

    ### <Icon icon="arrow-trend-up" /> Improved

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      All Labs polish this week went into environment stand-up (above).
    </Card>

    ### <Icon icon="wrench" /> Fixed

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      No Labs-specific fixes this week.
    </Card>
  </Tab>
</Tabs>

***

<Note>
  **How we tier releases:** [Labs](/release-tiers#labs) · [Preview](/release-tiers#preview) · [Platform](/release-tiers#platform). The world — and the AI beneath every intelligent product — is changing faster than ever. We ship you the latest and greatest. Occasionally your results will shift as models and methods refine; rarely enough to flip a decision, always with a note from us when the change is meaningful.
</Note>

<Tip>
  Want a closer look at any of these? Reach out to your Parable team — we're happy to walk you through what shipped and what's coming next.
</Tip>