> ## Documentation Index
> Fetch the complete documentation index at: https://anaconda.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# General artifacts
export const Danger = ({children}) => {
return ;
};
Channels support the upload of a wide range of generic file types, allowing you to store and share resources. This flexibility makes channels versatile for various use cases, ensuring that different types of files can be managed and accessed as needed. For example, a Miniconda installer can be packaged in different formats depending on the platform, such as `.exe` or `.dmg`. By supporting multiple file types, channels enable seamless sharing of these platform-specific resources, making them easily accessible to others.
There is no built-in security check on uploaded artifacts. *Performing manual security checks is strongly recommended*. Administrators and users with upload permissions should verify file integrity before uploading to ensure they are safe and that no malicious files are present.
* `.bz2`
* `.conda`
* `.deb`
* `.egg`
* `.exe`
* `.gz`
* `.ipynb`
* `.json`
* `.lz`
* `.lzma`
* `.msi`
* `.rpm`
* `.tar`
* `.tbz`
* `.tgz`
* `.tlz`
* `.txz`
* `.whl`
* `.xz`
* `.yaml`
* `.yml`
* `.zip`
## Uploading general artifacts
When uploading a general artifact file, you must assign it to an artifact group. In Package Security Manager, the group is considered to be the artifact itself, with the intent that each group contains variations of the same file for different platforms. Using our earlier example, if you want to upload Miniconda installers for distribution, you might create an artifact group called `Miniconda Installers`. If the group already exists, the uploaded file is included with the existing group’s files.
1. Select a channel that you want to upload a general resource artifact to.
2. Open the **Manage** dropdown menu and select **Upload File**.
3. Open the **Type** dropdown menu and select **General Artifact**.
4. Establish a descriptive group name for your artifacts, or use an existing group to include your file in.
5. Click **Select files…**, then locate and upload your general resource artifact. Alternatively, you can drag and drop your general resource artifact into the field.
6. Click **Upload**.
It is a known issue that uploading a file with an identical name as an existing one removes the original file from its artifact group and assigns it to a new group.
## Managing general artifacts
You can **Copy**, **Move**, or **Delete** entire groups of general artifacts, or the individual artifact files they contain.
To manage entire groups:
1. Select a channel you need to manage general artifacts for.
2. Select the **General Artifacts** tab.
3. Select the checkboxes beside group names. Management options appear at the top of the table.
4. Choose the action you want to take for the selected groups.
To manage files within a general artifact group:
1. Select a channel you need to manage general artifacts for.
2. Select the **General Artifacts** tab.
3. Click on a group name to view its files.
4. Select the checkboxes beside artifact names. Management options appear at the top of the table.
5. Choose the action you want to take for the selected files.
You might need to refresh the page to see your changes.
## Managing general artifacts via the CLI
If you want to manage your channel uploads using the CLI, see [Package Security Manager CLI](./cli#uploading-to-a-channel).