Very formal answer (not to overwrite code), but....
doing a quick and dirty "hack" takes < 30 seconds, whereas buying a 3rd party module cost $$$. In my own world as a software architect at a large global company, that answer would not have been acceptable for me.
DNN, please make changes to the the user accounts grid so that we can specify a sort order.
Meantime, for the person that asked the original question, you do it in PROCEDURE [dbo].[GetAllUsers]
WITH [tmpUsers] AS (
SELECT U.*, row_number() over (order by U.XXXXXXXXXXXXXXX) AS rowid
FROM dbo.vw_Users u
Why the developers handle paging in the TSQL (this partitioning they do in SQL with the "OVER" clause, when the telerik grid is very capable of handling the paging, is strange to me) (see xxxxxxx above, and change that to your field, I use DisplayName as sort order, and my display name is set to [Lastname], [FirstName] (because in non developers world, one search by a persons surname and name, and not a strange looking username)
Here is another tip for handling YOUR hacks in DNN source code:
I hack a lot of DNN stuff (SQL, cs, css, ascx etc, and the add a comment with my name in -- JOE SOAP or //JOE SOAP + the reason I did it. Then before I apply a DNN patch, I make a copy of the web and the SQL (Copy Database). After an update I use a file compare utility and db compare utility, filter on all that contains my name "JOE SOAP" and re-apply my hacks. (pew, still better than re-writing DNN or buying 3rd partyt modules for almost everything.
With this "compare" after every update, you also force yourself to know exactly what changes was made in DNN.
Good luck!