Installing for multiple users

If you have administrator access and want to install Anaconda Distribution or Miniconda for all users on a shared system, follow these steps:

Windows
Linux

Administrator privileges are required.

Install Anaconda Distribution or Miniconda for all users. When prompted, select All Users and use a location users have read access to (such as C:\ProgramData\miniconda3). All users on the machine can now access conda through the Anaconda Prompt (or Anaconda PowerShell Prompt) application in the Start Menu. These applications activate the base environment automatically.
Accept the Terms of Service.
If you are setting up Anaconda Distribution or Miniconda on behalf of members of your company, you can globally accept the Terms of Service for all users. If unrelated individual users are accessing Anaconda Distribution or Miniconda on the system, instead instruct users to accept the Terms of Service on an individual basis.
- System-wide TOS acceptance
- Individual TOS acceptance
Open Anaconda Prompt (or Anaconda PowerShell Prompt) from the Start Menu and run the following command:
conda tos accept --system
Open Anaconda Prompt (or Anaconda PowerShell Prompt) from the Start Menu and run the following command:
conda tos accept
For more information on conda tos, see Managing Terms of Service on the command line.
Optionally, create additional shared environments that all users can access. To create a shared environment, run the following command in Anaconda Prompt (or Anaconda PowerShell Prompt) with administrator privileges:
You can open Anaconda Prompt (or Anaconda PowerShell Prompt) with administrator privileges by right-clicking the application from the Start Menu and selecting Run as administrator.
```
conda create --name <ENV-NAME>
```
When created with administrator privileges, shared environments are saved to C:\ProgramData\anaconda3\envs or C:\ProgramData\miniconda3\envs and are accessible to all users.
Users cannot modify shared system environments, but they can create their own private environments using the same command.User-created environments are saved to %USERPROFILE%\.conda\envs in the user’s home directory and are only accessible to that user.
Optionally, monitor disk usage of the shared package cache at C:\ProgramData\anaconda3\pkgs or C:\ProgramData\miniconda3\pkgs. Users share the system-wide package cache, which conda reads from first before falling back to each user’s own cache at %USERPROFILE%\.conda\pkgs. Run conda clean periodically to remove unused packages and free up disk space.
Optionally, configure a global .condarc file at C:\ProgramData\anaconda3\.condarc or C:\ProgramData\miniconda3\.condarc to set system-wide defaults such as default channels. For example:
```
channels:  #!final
  - defaults

channel_alias: https://repo.anaconda.com/pkgs/  #!final
```
The #!final keyword prevents users from overriding specific settings with their own .condarc file. For a full list of configurable options, see Using the .condarc conda configuration file in the official conda documentation.
Users may still be able to override #!final settings in some circumstances. System-wide configuration cannot fully enforce policy.

root access is required.

Install Anaconda Distribution or Miniconda into a location accessible to all users, such as /opt/anaconda3 or /opt/miniconda3.
Initialize conda for all users so it is available in their terminals. Open a terminal and run the following command:
. <PATH-TO-INSTALL>/etc/profile.d/conda.sh conda init --all --system
Users might not see the active environment name in their shell prompt on first login due to their shell profile overwriting the prompt. This only affects the prompt display; conda will still work correctly. Users can run conda activate to fix the prompt for the current session, or conda init to fix it permanently for each new shell.
Accept the Terms of Service.
If you are setting up Anaconda Distribution or Miniconda on behalf of members of your company, you can globally accept the Terms of Service for all users. If unrelated individual users are accessing Anaconda Distribution or Miniconda on the system, instead instruct users to accept the Terms of Service on an individual basis.
- System-wide TOS acceptance
- Individual TOS acceptance
Open a terminal and run the following command:
conda tos accept --system
Open a terminal and run the following command:
conda tos accept
For more information on conda tos, see Managing Terms of Service on the command line.
Optionally, create additional shared environments that all users can access. To create a shared environment, run the following command as root:
You can open a root shell by running sudo -i or su - in your terminal.
```
conda create --name <ENV-NAME>
```
Users cannot modify shared system environments, but they can create their own private environments using the same command without root access.User-created environments are saved to ~/.conda/envs in the user’s home directory and are only accessible to that user.
Optionally, monitor disk usage of the shared package cache at <PATH-TO-INSTALL>/pkgs. Users share the system-wide package cache, which conda reads from first before falling back to each user’s own cache at ~/.conda/pkgs. Run conda clean periodically to remove unused packages and free up disk space.
Optionally, configure a global .condarc file at <PATH-TO-INSTALL>/.condarc to set system-wide defaults such as default channels. For example:
```
channels:  #!final
  - defaults

channel_alias: https://repo.anaconda.com/pkgs/  #!final
```
The #!final keyword prevents users from overriding specific settings with their own .condarc file. For a full list of configurable options, see Using the .condarc conda configuration file in the official conda documentation.
Users may still be able to override #!final settings in some circumstances. System-wide configuration cannot fully enforce policy.

Documentation Index