There are 2 questions in it: 1) assign alias to use by user locally; 2) declare global linux alias for system-wide usage by any user. Earlier i mentioned, that could be good to simplify an alias for composer... Reason: During my normal activity with drupal modules, their paths of installation are always copied seamlessly as: composer require 'drupal/video:^3.0'. When we use different versions of the Composer, it comes an inconvenient way to prepend: Code: php82 /usr/local/bin/composer82 require 'drupal/video:^3.0' Necessarily and would be useful to use a such alias: PHP: alias composer82='/opt/remi/php82/root/usr/bin/php /usr/local/bin/composer82' or Steps, that were reproduced: 1) adding to local /home/drupal/.bashrc file of a user required fragment of the alias: Problem to activate this script we need to run Code: source /home/drupal/.bashrc response: bash: /home/drupal/.bashrc: Permission denied Not placing the user to the wheel-group, we can't also execute: sudo source /home/drupal/.bashrc We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility. [sudo] password for web1: Neither the root, nor the user password grants access. 2) Declare global alias Creation of a script at /etc/profile.d/ This method is also unsuccessful to achieve our aim.