In this case you could suggest that we incorporate your changes. It would be easy to add a module setting to the shared files feature to show or hide columns and or add logic to show or hide if the user is admin or is authenticated.
In this case if you had needs that could not be incorporated back into the project one strategy is to clone the feature and fork it. Basically copy it into your own external projects, change the namesspaces, script off the tables and procedures and do a find and replace to change your table prefixes for your clone to something other than mp_, then do the same replacement of mp_ in your cloned data access code. Give your feature a new guid for the feature definition or moduledefinition so its not the same as the cloned one. I would only choose this strategy if you need customizations that couldn't or shouldn't be incorporated back into the project. Once you have forked the clone you won't get new enhancements unless you add them yourself or port them from updates to our version of the feature as we improve it over time, so ideally its better if we can make ours relatively configurable to meet your needs so you don't have to maintain a fork. But better to fork it than to constantly face merge problems.