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

# Integrations & imports

> Questions about getting model data into Real-Time LCA — Revit, Archicad, Rhino, Grasshopper, IFC, and Excel.

<AccordionGroup>
  <Accordion title="My Revit file has linked models (e.g. a steel supplier's model) — why isn't their data imported?">
    Linked models are excluded by default. In the Speckle Connector's publish dialog, scroll to the **Publish settings** panel and switch **Include Linked Models** on, then publish again.

    If the linked IFC is heavy, it can be easier to add it as a *separate* model on the Real-Time LCA project rather than bundling it through the host file.

    Walkthrough: [Speckle for Revit → Confirm publish settings](/user-guide/integrations/speckle/revit#step-4-confirm-publish-settings).
  </Accordion>

  <Accordion title="Why can't I sign in to Speckle from the Connector?">
    The Speckle Connector ships pointing at the public Speckle server, **app.speckle.systems**, by default. Real-Time LCA runs its own Speckle server, so you need to point the Connector at **api.realtimelca.com** instead.

    Sign in with the username and password from the *Connect Real-Time LCA with Speckle* email we sent you.

    Step-by-step: [Get set up with Speckle](/user-guide/integrations/speckle#get-set-up-with-speckle), or the host-specific walkthrough for [Revit](/user-guide/integrations/speckle/revit#sign-in-to-the-real-time-lca-speckle-server), [Archicad](/user-guide/integrations/speckle/archicad), [Rhino](/user-guide/integrations/speckle/rhino), or [Grasshopper](/user-guide/integrations/speckle/grasshopper).
  </Accordion>

  <Accordion title="If a material name changes in Revit, do I lose the EPD mapping when I re-push via Speckle?">
    Yes. EPD mappings are keyed on the combination of **type** and **material name**, so if either one changes — even by a single character — the link is broken.

    Once the identifier changes, we have no way of knowing what actually changed. A typo correction and a genuine change — say an inner wall becoming an outer wall — look identical to us: both just show up as a new identifier. Because we can't tell a harmless edit from a real change, we can't safely carry the mapping over in either case.
  </Accordion>
</AccordionGroup>