> ## 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 29 – 31, 2026

> A short 3-day week focused on reliability behind the scenes: steadier data transformations, a new Slack connection check, faster admin triage when you reach out for help, and quieter plumbing across the board.

<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="Steadier data transformations, with quieter failure modes" icon="workflow" defaultOpen>
        <Badge>Reliability</Badge>

        * The layer that turns your raw data into the reports you see got a significant reliability pass this week.
        * Transformations that quietly half-succeeded used to be invisible; now they surface clearly and recover predictably.
        * You should see fewer "data looked OK, but a column was missing" surprises in the weeks ahead.
      </Accordion>

      <Accordion title="Slack connections now tell you up front when a token is wrong" icon="circle-check">
        * When you set up a Slack connector, Parable now checks the credential before handing it off to sync.
        * If the token isn't valid, you'll see a clear error in the connector wizard immediately — no more spinning "Pending."
      </Accordion>

      <Accordion title="Faster triage when you ask our team for help" icon="headset">
        * Behind the scenes, our platform admins can now reach your workspace directly when you report a problem.
        * Less back-and-forth to get us into the right place — the next time you open a ticket, expect a faster "I'm in, let me take a look."
      </Accordion>
    </AccordionGroup>

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

    <AccordionGroup>
      <Accordion title="Small polish across connector setup" icon="paintbrush">
        * Cleaner credential error messages in the connector wizard — the form tells you which specific field to fix.
        * Magic-link sign-in: tidier input contrast so the field is easier to spot on busy backgrounds.
      </Accordion>

      <Accordion title="Safer supply chain, quieter deploys" icon="shield-halved">
        * A batch of internal infrastructure improvements makes our build pipeline harder to tamper with and faster to respond when a dependency vulnerability is announced.
        * You won't see anything change in the app — this is the kind of improvement you'll be glad we made the next time the industry has a bad security week.
      </Accordion>
    </AccordionGroup>

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

    <AccordionGroup>
      <Accordion title="A set of connector setup fixes" icon="plug">
        * Salesforce connector: resolved a case where custom domains weren't being picked up correctly during setup.
        * Linear connector: fixed a configuration mismatch that could block the first sync.
        * Connections with custom auth formats: cleaner handling when a token prefix isn't set.
      </Accordion>

      <Accordion title="Admin access works consistently across your domain" icon="unlock">
        * Resolved an edge case where admin-level access on certain URL shapes could fall back to the wrong permission set.
        * Admin users on every path now see the same consistent behaviour.
      </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 net-new Preview features in this short 3-day window. Team Time Spend's permanent home on Parable lands shortly — watch for it in the next release.
    </Card>

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

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      Nothing else 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="Lab views become easier to tailor per team" icon="sliders" defaultOpen>
        * We've reworked how some Labs are assembled so the same underlying view can be shaped for a different team by changing configuration, not code.
        * Your Labs access stays the same — this is groundwork that makes the next capability we bring to your team faster to offer.
      </Accordion>
    </AccordionGroup>

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

    <AccordionGroup>
      <Accordion title="Lab reliability polish" icon="bolt">
        * A handful of behind-the-scenes fixes to make Labs with large datasets load more predictably.
      </Accordion>
    </AccordionGroup>

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

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      All Labs polish this week landed under **Improved**.
    </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>