Then it is a very limited scope. The first thing I do on a new Django project is to ensure the admin portal is long gone. If you can't understand or work with your models from the Django shell, something is not right.
When you put your application in production and some non-tech want's to create or modify an entity, do you give them access to a production django shell?
This guy. Has it all sorted out. We're just a bunch of headless chicken running around with an admin to manage our business. Meanwhile, he's all bare hands, manipulating the shell, showing the snowflakes how it's done, telling his non-technical co-founders to learn the models, bash, sql and a god-dam shell. Such an inspiration, much envy, so wow!