This quickstart guide is intended to help you create an Anaconda account, obtain conda software, and configure it to access your instance of Anaconda.

​
Creating an account

Click here to create an Anaconda.com account

From here you have several options for account registration:

  • Sign up manually with an email and password
  • Authenticate with a GitHub, Gmail, or Microsoft account

​
Signing up manually

  1. Click Sign Up with Email.
  2. Enter your name, email address, and password.
  3. Check your email for the verification email.
  4. Click the verification link in your email to complete account verification.

​
Subscribing to Anaconda

For information and help with managing subscriptions, see Subscriptions.

​
Installing Anaconda software

​
Installing conda

You can obtain conda by installing either Anaconda Distribution or Miniconda. If you already have conda installed, skip ahead to Installing Anaconda Navigator.

If you do not have conda installed, download either Anaconda Distribution or Miniconda and install it on your system before proceeding. If you’re unsure which to download, refer to our Getting Started with Anaconda topic for guidance.

​
Installing Anaconda Navigator

Anaconda Navigator is a desktop graphical user interface (GUI) that uses conda to help you manage your environments. If you installed Anaconda Distribution, you already have Anaconda Navigator and can skip ahead to Installing conda-token.

If you installed Miniconda, you can install Anaconda Navigator by opening Anaconda Prompt (Terminal on macOS/Linux) and running the following command:

conda install anaconda-navigator

If you received a “conda: command not found” error, see this troubleshooting topic to resolve the issue.

​
Installing conda-token

The conda-token tool is used to authenticate your Anaconda.com organization access token and configure the default_channels: in your .condarc file to use Anaconda’s private repository channels. For more information, see Channels.

  1. Open Anaconda Prompt (Terminal on macOS/Linux).

  2. Install conda-token by running the following command:

    conda install conda-token --channel https://repo.anaconda.cloud/repo/anaconda-tools --name base

  3. Enter y when prompted to proceed with the installation.

​
Authenticating to Anaconda

Anaconda uses private tokens to authenticate users to their organizations. You must be assigned a seat within an organization to activate a token. Once you’re assigned a seat, you can generate a private token for yourself at any time.

  1. Go to your organization’s page.
  2. Select Token Access from the left-hand navigation.
  3. Select Activate token if it is the first time you are receiving a token, or Reissue token if you are obtaining a new token. An automated email containing a private token will be delivered to the address associated with your Anaconda account.
  4. Copy the private token you received in your email and set it in either Navigator or the CLI:

  1. Launch Anaconda Navigator.

  2. Select Connect, then Sign in to Anaconda Professional.

    Both the Pro (legacy) and Business tiers share a repository of curated packages. Therefore, signing into Anaconda Professional gives you access to the Package Security Manager channels you need, as long as you have the correct access token.

  3. Paste the token, then click Set token.

​
Important information about the .condarc file

The .condarc file is a configuration file that tells conda where to look for packages. Here is an example of what your .condarc file might look like:

channels:
  - https://repo.anaconda.cloud/repo/<ORG_ID>/<CHANNEL_NAME> # Business tier only
  - defaults
add_anaconda_token: true
restore_free_channel: false
default_channels:
  - https://repo.anaconda.cloud/repo/main
  - https://repo.anaconda.cloud/repo/rcart
  - https://repo.anaconda.cloud/repo/msys2

Conda searches for requested packages in the channel listed at the top of the channels: list first. If that channel contains the requested package, it is downloaded from that channel.

If the requested package is not located in that channel, conda will search for the package in the next entry of the channels: list.

When conda reaches the defaults entry of the channels: list, it searches the channels listed under the default_channels: list, in the same descending order.

In this example for Business tier, conda will look for a requested package in your organization’s channel first, then will look in the default channels in listed order, starting with https://repo.anaconda.cloud/repo/main, then https://repo.anaconda.cloud/repo/r, and finally, in https://repo.anaconda.cloud/repo/msys2.

For Pro tier (legacy), conda will look in the default channels in listed order, starting with https://repo.anaconda.cloud/repo/main, then https://repo.anaconda.cloud/repo/r, and finally, in https://repo.anaconda.cloud/repo/msys2.

For more information regarding the .condarc file, see the official conda documentation.

​
Viewing your .condarc file

You can view and edit your .condarc file in either Navigator or the CLI:

In Anaconda Navigator, navigate to Preferences from the menu bar and select Configure Conda.

You can edit the .condarc file directly from this view.

​
Adding an organization channel to your .condarc file

This section applies to Business tier only.

  1. Go to your organization’s page.
  2. Select your organization.
  3. Select Channels from the left-hand navigation.
  4. Select copy channel path.
  1. Open your terminal and run the following command:
# Replace <CHANNEL_PATH> with the copied channel path
conda config --prepend channels <CHANNEL_PATH>

​
Adding conda-forge as a channel

If you need to install packages from the conda-forge repository, you can do so in either Navigator or the CLI:

  1. Select Channels, then click Add….
  2. Enter conda-forge as your channel.
  3. Press Enter (Windows)/Return (Mac) to add the channel.
  4. Click Update channels to instruct navigator to update the channels: list in your .condarc file.

​
Using Anaconda behind a firewall or proxy (Optional)

Some companies have security policies that prevent communications on their network with external servers like Anaconda. Under these circumstances, you’ll need to connect to your company’s firewall/proxy server in order to download packages successfully.

To connect to a firewall/proxy server, you’ll need to include a proxy_servers: section in the .condarc file that contains the URL to the proxy server. This entry must also contain a username and password for logging in to the proxy server. Speak with your IT Administrator if you do not have this information.

There are no commands to include this portion of the .condarc file, so you need to manually include the following lines:

If your password contains special characters, you’ll need to escape them using percent encoding as described here.

# Replace <USERNAME> with the username for your proxy server
# Replace <PASSWORD> with the password for your proxy server
# Replace <URL> with the URL to your proxy server
proxy_servers:
 http: http://<USERNAME>:<PASSWORD>@<URL>:8080
 https: https://<USERNAME>:<PASSWORD>@<URL>:8443

You’ll also need to work with your IT team to allowlist connections to the main package repositories once you’ve configured your connection to the firewall/proxy server. The main package repositories are:

https://anaconda.org
https://repo.anaconda.com
https://repo.anaconda.cloud

In some situations, it is necessary to export the HTTP_PROXY and HTTPS_PROXY environment variables to utilize the proxy server. To export your environment variables, open a terminal and run the following commands:

# Replace <USERNAME> with the username for your proxy server
# Replace <PASSWORD> with the password for your proxy server
# Replace <URL> with the URL to your proxy server
export HTTP_PROXY=http://<USERNAME>:<PASSWORD>@<URL>:8080
export HTTPS_PROXY=https://<USERNAME>:<PASSWORD>@<URL>:8443

For more information about using conda behind a proxy server, see Configure conda for use behind a proxy server.

​
Enabling environment management

Administrators can enhance organizational security by requiring members to log their local conda environments with the organization. Environments that are logged with an organization can be monitored, scanned, and blocked from use if a vulnerability is discovered. For more information about logging, scanning, and managing environments, see Environments.

Implementing environment logging requires coordination at the organizational level.

​
Prerequisites

Environment logging and scanning requires the following:

  • An Anaconda.com account

  • Python 3.10 or later in your (base) environment

​
Installing required plugins

Environment logging and scanning requires the installation of a few plugins in your (base) environment that expand the functionality of conda.

Obtain the necessary plugins by installing the anaconda-env-manager “metapackage” (which contains all of the plugins listed below). To install anaconda-env-manager, run the following command:

conda install --name base anaconda-cloud::anaconda-env-manager

​
Registering your organization

To ensure your environments are properly logged to your organization on Anaconda.com, you must log in via the CLI and register your organization with conda. To register your organization:

  1. Open Anaconda Prompt (Terminal on macOS/Linux).

  2. Authenticate to Anaconda by running the following command:

    anaconda login --at cloud

You will be prompted for your username and password. Enter your Anaconda.com credentials and complete the login process in the browser window that opens.

  1. After successfully logging in, return to the command line and register your organization by running the following command:

    # Replace <ORG_ID> with your ORG_ID — found in your organization's URL —
# https://anaconda.com/app/organizations/<ORG_ID>
conda env-log register --organization-name <ORG_ID>

With the organization registered (and anaconda-env-log installed in the (base) environment), newly created environments are logged to the registered organization.

​
Verifying your configurations

Test your configurations and verify that conda downloads packages from the desired channel in either Navigator or the CLI:

  1. Go to Environments in the left-hand navigation, then select Create at the bottom of the window.
  1. Enter a name for your environment and select a version of Python (3.11 is preferred) from the dropdown menu, then click Create.
  2. Change the package selector to Not installed. This will show you packages that are available from your channel but are not installed on your machine.
  1. If you know the name of the package you need, you can enter it in the search bar to locate the package. Select a package to download and click Apply.
  1. Click Apply to install the selected packages (and their dependencies).

The Channel column will display your organization’s channel path, if correctly configured.

Was this page helpful?