# Artifact settings

The **Libraries** tab contains a list of repositories that can be referenced in your code repository, which we refer to as backing repositories. This is a list of all shared code repositories in your Foundry environment, as well as external or public libraries. You can use the Libraries tab to discover and add backing repositories.

If you are looking to import and use Python libraries, see the section on [sharing Python libraries](../../transforms-python/share-python-libraries/index.md).

:::callout{theme="neutral"}
Viewing artifact settings requires the `artifacts:view-repository` permission, and managing artifact settings requires the `artifacts:manage-repository` permission.
:::

![artifact-settings-tab](../../../assets/45327a80fdab47422ca5571804ff447afe5db5438fdd8e54ad9e2da9716a238c.webp)

### Add a new artifact to your Code Repository

To add a new artifact, select **Add** and choose one of two types of repositories:

1. **Local repositories:** These are other code repositories in your Foundry environment that were configured as a [shared library](../libraries/index.md).
2. **External repositories:** Artifact repositories stored out of your Foundry environment. These could be external Foundry repositories or public artifact repositories that are available in your environment.

![artifact-settings-add-repository](../../../assets/fede863f3aa1547f15d88367d99c2e4b1073a0df4963385d61c16c21a9c576fc.webp)

If the added artifact repository contains references to additional repositories, they will be added as well. The same access permissions are required for all the dependencies of the added repository.

When you add a local repository from a different project, a [project reference](../use-project-references/index.md) to that repository is also added. This requires the `compass:view-project-imports` and `compass:import-resource-to` permissions on your own code repository, and the `compass:import-resource-from` permission on the referenced shared repository.

:::callout{theme="warning"}
While it is possible to reorder and delete backing repositories, this might break builds of transforms that use packages from those repositories. Only take this action after considering the possible implications.
:::

## Beta OSDK generator versions toggle

When the **Enable beta OSDK versions** option is enabled, users can generate beta (release candidate) ontology generator versions. The toggle is off by default.

![beta-toggle](../../../assets/1cc763349934d033912fcf32ee998b7e162fa1514a59fc83372c3bf43eef4259.webp)

To enable beta OSDK versions:

1. Navigate to the **Branches** tab and ensure you are on the default branch.
2. Inside the repository's functions.json file, add `"allowBetaGeneratorVersions": true` to the file. To discover this file, the **Show hidden files** toggle may have to be enabled by selecting the cogwheel at the top near the Files header.

![beta-field-functions-json](../../../assets/6a8f2659449bfdff495c1ee58ce148f1d3794f691485c8675e01126120ee8a88.webp)

3. Make sure to commit this change in the **Source Control** tab; otherwise, it will not be reflected in the settings.
4. Navigate to the **Libraries Settings** and enable the **Beta OSDK Versions** toggle.
5. You can now discover beta generator versions in the **Generator** dropdown when creating a new version in the **Functions Imports** tab.

![beta-versions](../../../assets/68a0a1b0bd650bb072b530e0eaf4ba7652ee8dab5ac6eed5ec26019612e36128.webp)