> ## 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 February 1 – 7, 2026

> What's new this week: stronger sync safety guarantees, honest credential status, and new admin controls for managing who has access.

<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="The same connector can never sync twice at once" icon="lock" defaultOpen>
        <Badge>Reliability</Badge>

        * Parable now takes a platform-level lock on each connector while it's syncing, so a manual trigger and a scheduled run can't accidentally both fire at the same time.
        * You'll see cleaner history in the connector activity view — one run per sync, no duplicates.
      </Accordion>

      <Accordion title="Credentials have a new, honest status: Unvalidated" icon="circle-check">
        * Some connectors don't yet have a built-in credential validator. Previously those credentials showed as "Valid" as soon as they were stored — which wasn't quite true.
        * You'll now see **Unvalidated** in that case, so you know the credentials are stored but haven't been verified end-to-end. When validation becomes available for a connector, the status updates automatically.
      </Accordion>

      <Accordion title="Suspend, reactivate, or revoke users from the admin UI" icon="user-gear">
        * Admins can now manage user access directly from the tenant settings — with clear status badges and confirmation dialogs.
        * Previously this was a request to the Parable team; now it's self-serve.
      </Accordion>

      <Accordion title="Credentials are encrypted with per-workspace keys in Google Cloud KMS" icon="key">
        * Each Parable workspace now has its own asymmetric encryption key managed by Google Cloud's Key Management Service.
        * The private half of that key never leaves KMS — every decryption is hardware-backed and audit-logged. Another layer of separation between workspaces, and a cleaner answer to "where does this credential live?".
      </Accordion>

      <Accordion title="Tenant setup now captures a domain and a stable slug up front" icon="id-card">
        * New workspaces ask for an explicit URL slug and a company domain at creation time.
        * The slug is used everywhere your team will see a Parable link; the domain lays the groundwork for upcoming single-sign-on and email-based invitations.
      </Accordion>
    </AccordionGroup>

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

    <AccordionGroup>
      <Accordion title="Sync status is now reported end-to-end" icon="arrows-rotate">
        * The ingestion service now reports every sync's start, success, and failure back to Parable's control plane automatically.
        * When you look at a connector's status, you're seeing the live state of the actual run — not a best-effort guess.
      </Accordion>

      <Accordion title="Small web-app performance improvements" icon="gauge-high">
        * Tightened imports in the web application so your browser downloads slightly less JavaScript on each page load.
        * Minor on its own; compounds across every navigation.
      </Accordion>
    </AccordionGroup>

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

    <AccordionGroup>
      <Accordion title="Foreign-key integrity preserved when a related record is archived" icon="database">
        * Fixed an edge case where archiving a related record could detach its reference from another record, making audit trails harder to follow.
        * No customer action needed — the fix applies automatically.
      </Accordion>

      <Accordion title="Reliability fixes in the connector startup flow" icon="shield-check">
        * Resolved a startup race that could briefly delay a connector's first connection.
        * Tightened a handful of internal build and test paths so releases behave predictably.
      </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>

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      No Preview-tier updates this week — everything customer-facing landed at the Platform tier. More coming soon.
    </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="Foundations for a new Labs deployment pattern" icon="rocket" defaultOpen>
        * We extended the Labs deployment pattern to cover workspaces whose data lives in a cloud data lake rather than a database.
        * Nothing visible yet on your side — this is groundwork for upcoming Labs capabilities.
      </Accordion>
    </AccordionGroup>

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

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

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

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      Nothing to fix in Labs 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>