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

# Portal Mode Walkthrough

> Step-by-step guide to ingesting repositories using Portal-managed mode — select repos, fill metadata, review, and submit.

You've selected **Managed by Portal** mode. Here's what happens next as you complete the remaining steps.

## Step 4: Select Repositories

Choose the repositories you want to turn into components. In Portal mode:

* Each repository becomes exactly one component (1:1 mapping)
* Any existing `catalog-info.yaml` files are **ignored**
* Portal will attempt to detect metadata from the repository

> Portal shows all repositories from the organizations you selected in Step 3, regardless of whether they have a `catalog-info.yaml` file.

## Step 5: Fill Missing Details (Optional)

Portal auto-detects what it can from your repositories, but some information may be missing.

**This step is optional.** You can:

* Fill in details now for complete metadata
* Skip and update later through the Portal UI

<Frame>
  <img
    src="https://mintcdn.com/spotify-89f50c35/30KNAI5WzZFwyWnx/portal/core-features-and-plugins/catalog-builder/assets/catalog-builder-azure-metadata-missing.png?fit=max&auto=format&n=30KNAI5WzZFwyWnx&q=85&s=3d0f7441e358144cf544ac3aa99ffdfc"
    alt="Catalog Builder Missing
Steps"
    width="3824"
    height="1846"
    data-path="portal/core-features-and-plugins/catalog-builder/assets/catalog-builder-azure-metadata-missing.png"
  />
</Frame>

## Step 6: Review and Complete

Review your selected components before finalizing. This screen shows:

* All components that will be created
* Their metadata (name, owner, lifecycle, type)
* Any warnings or missing information

Click **Complete** to finish the ingestion.

## What Happens Next

When you complete the workflow:

1. **Components are immediately registered** in the catalog
2. **They appear in Portal** within 1-2 minutes
3. **All metadata is stored in Portal's database**

You can now:

* Find your components in the catalog
* Update metadata using the [edit and bulk edit dialogs](../catalog/bulk-editing)

## Managing Your Components

Since these components are managed by Portal:

* **Updates** are made using the [edit and bulk edit dialogs](../catalog/bulk-editing), not by editing files
* **Metadata lives in Portal's database**, not in your repositories
* **No `catalog-info.yaml` files** will be created or used

Need to switch to YAML management later? See the [FAQ](./faq).

## Troubleshooting

Having issues? Check the [Troubleshooting guide](./troubleshooting) for common problems and solutions.