Actions as Buttons vs. Table Headers/Footers

I'm reporting this as a bug because it has caused some confusion for our new users.

There appears to be some inconsistencies between having actions as buttons or having them listed as text links above and below the table. It seems that the intention was to have buttons operate on multiple selected items, while single (e.g. new) item actions appear as the text links.

Case in point: The Mail and FTP Users page (list_users.cgi). Adding a new user or a website FTP access user both appear as text links above and below the table. Deleting and modifying users appear as buttons. However, the Batch Create Users button does not fit this mold. It doesn't use any selections in the table above, so it doesn't fit with the other buttons.

Aside from the inconsistencies, the current model is not intuitive. New users don't easily see the options above/below the tables and therefore don't realize how to perform these actions. In my opinion, the lines above/below the tables should be reserved strictly for table navigation and selection options (i.e. select all, invert selection, etc.). All other actions, whether making use of selections or not, should appear as buttons below the table, or some other consistent method.