Migrations-disable the console on the server

[joshua-gould]

"To use migrations effectively, the console on the server (which is served at /console) should be disabled and all changes must go through the console served by the CLI. Otherwise, changes could be made through the server console and they will not be tracked by migrations." from https://hasura.io/docs/latest/graphql/core/migrations/migrations-setup.html#step-0-disable-the-console-on-the-server

Can you please clarify why I need to start the console using the CLI instead of using the console on the server? I don't understand this explanation. Thanks.