> For the complete documentation index, see [llms.txt](https://documentation.ardoq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ardoq.com/integrations/out-of-the-box-integrations/ai-visual-importer.md).
# AI Visual Importer
Bring your diagrams into Ardoq as components and references.
{% hint style="info" %}
This feature requires administrator permissions to use.
{% endhint %}
## Overview
This integration is intended as a way to bring diagrams you've created in diagramming tools into Ardoq.
Ardoq supports diagrams in image formats like PNG, JPEG, and SVG, as well as importing diagrams directly from Lucidchart.
Objects in a diagram are intended to be imported as Ardoq components and the connecting lines between objects are intended as references. Users can further refine their import using a custom prompt to suggest additional details to consider.
{% embed url="" %}
### Enabling the AI Visual Importer
As an AI-based feature, you will need to manually enable the feature by clicking your organization name in the top-left corner then going to **Admin** > **Organizational settings** and selecting the **Features** tab, and toggling on the Visual Importer.
Once enabled, the Visual Importer can be found on the Integrations dashboard (main menu > **Imports & Integrations**).
## Importing Diagrams
To start the analysis, you'll need to upload an image or select a Lucidchart diagram with the Upload button.
### Selecting Workspaces
The workspace selector sets the scope for the AI analysis. The component and reference types from the selected workspaces will be used in the diagram processing to automatically determine the types for the references being brought in.
Once the relevant workspaces have been selected, run the analysis with **Analyze data**.
#### Matching Across Workspaces
By default, the Visual Importer requires that you specify all workspaces to be used for the import. This means that components will only be automatically identified from the selected workspaces.
On the other hand, if you enable the **Match across workspaces** option, the visual importer will look across all workspaces in your organization to find matching components and it will automatically add workspaces to the scope of the importer.
### Refining the Analysis
After the analysis has completed, you'll be presented with the discovered components and references. We recommend verifying that the AI interpretation was correct.
The visual importer has options to create any missed components and references, as well as to delete falsely identified ones.
The results are organized as components and their outgoing references. You can expand a component to see its references and add any new ones.
#### Existing Components
Components that were originally exported from Ardoq to Lucidchart contain Ardoq IDs and will be identified as already existing in your workspaces.
As these components already have defined types, the importer will pre-populate them and prevent you from making changes to the component type.
#### Diagram Types and Limitations
The visual importer is designed around importing diagrams that were originally exported from Ardoq into Lucidcharts. However, the flexibility of the solution allows you to ingest a wide variety of non-Ardoq diagrams into Ardoq as components and references. Keep in mind that extremely large diagrams may fail analysis due to limitations in AI models.
### Previewing the Results
You can verify the mapping done in the **Review** step with the preview window. It will display the diagram as it will be imported into Ardoq.
## Importing to Scenarios
{% hint style="info" %}
While Ardoq uses Scenarios as a staging ground for your import, this feature does not require the Scenario add-on.
{% endhint %}
Once you've made adjustments to your import, you can bring in any new and existing components into a scenario by clicking the **Import to Scenario** button.
Scenarios serve as a staging ground before bringing in the data created from the diagram directly into Ardoq.
Once you're confident about the state of the scenario, you can merge it to the mainline data.
## Known Limitations
* You can only import components and references to new scenarios, not existing ones
* Depending on the complexity of your custom prompt, the import may not succeed due to AI limitations
