If you are doing things manually and looking for an easier way to go about this without needing to remember the exact grant you typically make for a certain class of user, you can look up the statement to regenerate a comparable user's grants, and change it around to create a new user with similar privileges: mysql> SHOW GRANTS FOR Grants for | However, there is no single privilege that grants some subset of other privileges, which is what it sounds like you are asking. GRANT SELECT, SHOW VIEW, PROCESS, REPLICATION CLIENT ON *.* TO. If that's the reading you want to do, you can combine any of those (or any other of the available privileges) in a single GRANT statement. Note that any or all of these might expose more information than you intend to expose, depending on the nature of the user in question. 'Reading' the current replication state is the REPLICATION CLIENT privilege.

'Reading' the list of currently-executing queries by other users is the PROCESS privilege. 'Reading' the definition of views is the SHOW VIEW privilege. However, it sounds like you mean an ability to 'see' everything, to 'look but not touch.' So, here are the other kinds of reading that come to mind: If that's what you mean by 'all read' then yes: GRANT SELECT ON *.* TO IDENTIFIED BY 'password' 'Reading' from tables and views is the SELECT privilege. If you've customized Administrate in a cool way, or have suggestions for a better way to pull off custom sorting (maybe I should have leaned into COLLECTION_FILTERS for this use case.If there is any single privilege that stands for ALL READ operations on database. While solutions like this can feel a little hacky at times (and cause N+1 performance issues), they're generally quick to pull off and result in precise solutions with minimal side effects. I love the flexibility that Administrate provides when your use cases push you outside the standard lanes. Administrate lets you easily override the default functionality with impressive percission, so here's the solution.įirst, we update the generated UsersController to get our own order functionality in where we want it: # in app/controllers/admin/users_controller.rbĬlass UsersController problem solved! Recap / Ode to Administrate I'm sure it's possible to pull this off in SQL land, but I was curious to see what it'd take to run the sorting logic in Ruby. The goal was to sort all User records by this invitation_status. This is a read-only field that we display on the index and show views, and the value is a string derived from the status of related Invitation records (eg: Invitation Sent 10-13-2021, Accepted). In one of our Administrate dashboards, we display a User's invitation_status.

Super health club read only database