Django SmartBase Admin
A modern, modular, and developer-friendly admin interface for Django.
Built to speed up development of internal tools and admin panels — beautifully and efficiently.
✨ Features
- Fast integration with any Django project
- Improved performance of Django List Admin using
SBAdminField, databaseannotate()andvalues()to avoid direct object access - Simple configuration of menu structure, dashboard components, and permissions per user role
- Enhanced Django List Admin filters: autocomplete support for related fields and filtering across all model fields
- Ability for users to save and reuse custom filters in Django List Admin
- Improved Django Detail Admin with autocomplete for relational fields
- Support for "FakeInlines" – define inline-like blocks without requiring a direct model relationship
- Easy extension of list and detail views with custom actions and corresponding views
- Beautiful modern UI (Tailwind CSS)
- Responsive & mobile-friendly
- End-user ready for building SaaS or similar projects with global queryset configuration
- Built-in audit logging — automatically tracks all admin create, update, and delete operations with full change history, snapshots, and request grouping
📚 Full Documentation (in progress)
🌐 Live Demo
Want to see it in action?
👉 Check out the live demo
Login credentials:
- Admin role:
admin / admin - Editor role:
editor / editor
⚡ Quick Start
1. Install Smartbase Admin
Begin by installing the Smartbase Admin package using pip:
pip install django-smartbase-admin
Ensure that django-smartbase-admin and its dependencies are included in your Django settings. Open your settings.py file and add the following to INSTALLED_APPS:
INSTALLED_APPS = [
# other apps
"django_smartbase_admin",
"easy_thumbnails",
"widget_tweaks",
"ckeditor",
"ckeditor_uploader",
]
2. Add Admin URL Configuration
In your project’s urls.py, register the Smartbase Admin site by importing sb_admin_site and adding the path:
from django_smartbase_admin.admin.site import sb_admin_site
urlpatterns = [
path("sb-admin/", sb_admin_site.urls),
# other paths
]
This makes the Smartbase Admin interface accessible at /sb-admin/
3. Define the SmartBase Admin Configuration
In your project, for example in config package create a file called sbadmin_config.py with the following content:
from django_smartbase_admin.engine.configuration import SBAdminConfigurationBase, SBAdminRoleConfiguration
from django_smartbase_admin.views.dashboard_view import SBAdminDashboardView
from django_smartbase_admin.engine.menu_item import SBAdminMenuItem
config = SBAdminRoleConfiguration(
default_view=SBAdminMenuItem(view_id="dashboard"),
menu_items=[
SBAdminMenuItem(view_id="dashboard", icon="All-application"),
],
registered_views=[
SBAdminDashboardView(widgets=[], title="Dashboard"),
],
)
class SBAdminConfiguration(SBAdminConfigurationBase):
def get_configuration_for_roles(self, user_roles):
return config
4. Reference the Configuration in settings.py
SB_ADMIN_CONFIGURATION = "config.sbadmin_config.SBAdminConfiguration"
5. Add Locale Middleware
Add the following middleware to support internationalization:
MIDDLEWARE = [
# Other middleware...
'django.middleware.locale.LocaleMiddleware',
]
Enable Django i18n URLs so {% url 'set_language' %} is available for the navigation language picker:
from django.urls import include, path
urlpatterns = [
path("i18n/", include("django.conf.urls.i18n")),
]
🔍 Audit Logging
Built-in optional audit app that automatically tracks all admin create, update, delete, and bulk operations with field-level diffs, snapshots, and request grouping. Just add "django_smartbase_admin.audit" to INSTALLED_APPS and run migrations.
See AGENTS.md — Audit Logging for setup and configuration.
🤖 AI/Developer Reference
See AGENTS.md for development patterns, gotchas, and AI assistant instructions.
🤝 Need Help with Development?
We at SmartBase are experts in Django and custom software.
Whether you're building a new platform or modernizing an internal tool — 💡 We can help you design, build, and scale it.
📬 Let's talk — We'd love to work with you.
1 maintainer
Release files for django-smartbase-admin 2.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_smartbase_admin-2.4.1.tar.gz | 3.9 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_smartbase_admin-2.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.2 MB
Release files / django_smartbase_admin-2.4.1.tar.gz
| Download URL | django_smartbase_admin-2.4.1.tar.gz |
|---|---|
| Size | 3.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0f81825198de2ab18a506be662a94a85b05874d7356a360418e8dc47a616e6b7
|
|
BLAKE2b-256 checksum How to use checksums |
ad8c6afc81242257e5c16ff9d64d14df29edd9e1dc12fde057cbf1f7e73b937e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logRelease files / django_smartbase_admin-2.4.1-py3-none-any.whl
| Download URL | django_smartbase_admin-2.4.1-py3-none-any.whl |
|---|---|
| Size | 4.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eaf26e704bcb6845a4335d76b3b4bf4da0be4316e57872213bf78d0b8a5e19f3
|
|
BLAKE2b-256 checksum How to use checksums |
e7dd6b5418ae45a802e02c7dd9fae336df22b886838e61db562898823223a730
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency log
