You don't need anything else since the way catkin_make install works is to simply copy the files from your source location to the location where you want to install your ROS packages. This will make catkin_make visible to the superuser.
Now that you have superuser privileges all you have to do is source the setup.bash located in your non-super user's catkin workspace or the one located in /opt/ros//setup.bash: All you have to do is change the current user (marked as indicating a user with not superuser privileges and the one you normally use for developing ROS software): That is why option two seems the most straight forward way to go. The third option might pose some issues for new ROS users who are not used to handling multiple workspaces, which require combining several setup.bash files. So under normal circumstances we have only the second and third option from the list above. Also working as a superuser is often something that people generally avoid to do (security reasons). The first option is not recommended since ROS doesn't usually require superuser privileges when you do development.
CMAKE INSTALL PERMISSION WINDOWS PLUS
The build folder is where cmake and make are invoked, and the devel folder contains any generated files and targets, plus setup.*sh files so that you can use it like it is installed.
CMAKE INSTALL PERMISSION WINDOWS CODE
Catkin_make is a convenience tool for building code in a catkin workspace.