Skip to main content

Group accounts for Django

Project description

Summary Groups and multi-user account management
Author Ben Lopatin (
Status Documentation Status Travis-CI Build Status PyPI Package latest release PyPI Wheel Supported versions Supported implementations

Separate individual user identity from accounts and subscriptions. Django Organizations adds user-managed, multi-user groups to your Django project. Use Django Organizations whether your site needs organizations that function like social groups or multi-user account objects to provide account and subscription functionality beyond the individual user.

  • Works with your existing user model, whether django.contrib.auth or a custom model. No additional user or authentication functionality required.
  • Users can be belong to and own more than one organization (account, group)
  • Invitation and registration functionality works out of the box for many situations and can be extended as need to fit specific requirements.
  • Start with the base models or use your own for greater customization.

Documentation is on Read the Docs

Development & Contributing

The master branch represents version 2 development. For updates related to 1.x versions of django-organizations pull requests should be made against the [`version-1.x` branch](tree/version-1.x).

Development is on-going. To-do items have been moved to the wiki for the time being.

The basic functionality should not need much extending. Current dev priorities for me and contributors should include:

  • Improving the tests and test coverage (ideally moving them back out of the main module and executable using the file)
  • Improving the backends and backends concept so that additional invitation and registration backends can be used
  • Documentation
  • Ensuring all application text is translatable

Please use the project’s issues tracker to report bugs, doc updates, or other requests/suggestions.

Targets & testing

The codebase is targeted and tested against:

  • Django 2.2.x against Python 3.5, 3.6, 3.7, 3.8
  • Django 3.0.x against Python 3.6, 3.7, 3.8
  • Django 3.1.x against Python 3.6, 3.7, 3.8

To run the tests against all target environments, install tox and then execute the command:


Fast testing

Testing each change on all the environments takes some time, you may want to test faster and avoid slowing down development by using pytest against your current environment:

pip install -r requirements-test.txt

Supply the -x option for failfast mode:

py.test -x


These submission guidelines will make it more likely your submissions will be reviewed and make it into the project:

  • Ensure they match the project goals and are sufficiently generalized
  • Please try to follow Django coding style. The code base style isn’t all up to par, but I’d like it to move in that direction
  • Also please try to include good commit log messages.
  • Pull requests should include an amount of code and commits that are reasonable to review, are logically grouped, and based off clean feature branches.

Code contributions are expected to pass in all target environments, and pull requests should be made from branches with passing builds on Travis CI.

Project goals

django-organizations should be backend agnostic:

  1. Authentication agnostic
  2. Registration agnostic
  3. Invitation agnostic
  4. User messaging agnostic



First add the application to your Python path. The easiest way is to use pip:

pip install django-organizations

Check the Release History tab on the PyPI package page for pre-release versions. These can be downloaded by specifying the version.

You can also install by downloading the source and running:

$ python install

By default you will need to install django-extensions or comparable libraries if you plan on adding Django Organizations as an installed app to your Django project. See below on configuring.


Make sure you have django.contrib.auth installed, and add the organizations application to your INSTALLED_APPS list:


Then ensure that your project URL conf is updated. You should hook in the main application URL conf as well as your chosen invitation backend URLs:

from organizations.backends import invitation_backend

urlpatterns = [
    url(r'^accounts/', include('organizations.urls')),
    url(r'^invitations/', include(invitation_backend().get_urls())),

Auto slug field

The standard way of using Django Organizations is to use it as an installed app in your Django project. Django Organizations will need to use an auto slug field which are not included. By default it will try to import these from django-extensions, but you can configure your own in settings. The default:

ORGS_SLUGFIELD = 'django_extensions.db.fields.AutoSlugField'


ORGS_SLUGFIELD = 'autoslug.fields.AutoSlugField'

Previous versions allowed you to specify an ORGS_TIMESTAMPED_MODEL path. This is now ignored and the functionality satisifed by a vendored solution. A warning will be given but this should not have any effect on your code.

Registration & invitation backends

You can specify a different invitation backend in your project settings, and the invitation_backend function will provide the URLs defined by that backend:

INVITATION_BACKEND = 'myapp.backends.MyInvitationBackend'

Usage Overview

For most use cases it should be sufficient to include the app views directly using the default URL conf file. You can customize their functionality or access controls by extending the base views.

There are three models:

  • Organization The group object. This is what you would associate your own app’s functionality with, e.g. subscriptions, repositories, projects, etc.
  • OrganizationUser A custom through model for the ManyToMany relationship between the Organization model and the User model. It stores additional information about the user specific to the organization and provides a convenient link for organization ownership.
  • OrganizationOwner The user with rights over the life and death of the organization. This is a one to one relationship with the OrganizationUser model. This allows User objects to own multiple organizations and makes it easy to enforce ownership from within the organization’s membership.

The underlying organizations API is simple:

>>> from organizations.utils import create_organization
>>> chris = User.objects.get(username="chris")
>>> soundgarden = create_organization(chris, "Soundgarden", org_user_defaults={'is_admin': True})
>>> soundgarden.is_member(chris)
>>> soundgarden.is_admin(chris)
>>> soundgarden.owner.organization_user
<OrganizationUser: Chris Cornell>
>>> soundgarden.owner.organization_user.user
>>> <User: chris>
>>> audioslave = create_organization(chris, "Audioslave")
>>> tom = User.objects.get(username="tom")
>>> audioslave.add_user(tom, is_admin=True)
<OrganizationUser: Tom Morello>

Custom models

Django-organizations can act as a base library (not installed in your project) and used to create unique organization model sets using custom tables. See the Cooking with Django Organizations section in the documentation for advice on proceeding.


Anyone is free to use or modify this software under the terms of the BSD license.


Muster is building precision advocacy software to impact policy through grassroots action.

Alternative text



  • Remove default_app_config for forward compatiblity with Django 4.1


  • Better compatibility with Django 3.2


  • Invitation model backend uses models to track invitations
  • Registration/inviation backends take an optional namespace argument on initialization. The use case is if you want to namespace the URLs
  • Can provide a dotted path to invitation_backend and registration_backend functions
  • Drops support for Python 2 and Django versions < 2.2 LTS
  • Migrate the codebase to an src/ layout
  • Now with more test coverage!


  • Fixes issue with default backend where users defined without first/last names might not be represented


  • Migrations and slug related fixup

This is a small but significant change. A change introduced in version 1.0.0 due to incompatability with an unmaintained default dependency yielded migration issues for many users. This release switches back to a fork of the original dependency to revert the default changes.


  • Django 2 compatibility.

At this point it seems reasonable to bump to version 1.


  • Create username value for user if username field exists (custom user models)
  • Replaced BaseBackend._send_email with BaseBackend.email_message. email_message() should return the message without actually doing the send.


  • Decouple concrete organizations.Organization model from the invitation/registration backends


  • Fixes missing migration. Migration was created due to non-schema changes in models


  • Add notification to users when added to an organization
  • New abstract models create separation between ‘plain’ base models and abstract models that include abstracted functionality previously included only in concrete models
  • Python 3.6 and Django 1.11 test support


  • Updates setup classifiers information


  • Fixes [lack of] validation bug in backend registration form


  • Adds Django 1.10 support


Fixes some issues which may require some users to clear out extraneous migrations produced by using configurable base classes.

  • Fixes condition where create_organization produces an owner who is not an admin user.
  • Fixes issue in slug field import resulting in spurious migrations.
  • Immediately deprecates configurable TimeStampedModel import. This caused serious problems with Django’s migration library which were not easily resolved for a feature that added little value.


  • Fixes email parsing from settings


  • Adds Django 1.9 support
  • Drops support for Django 1.7
  • Fixes migration issue related to incomplete support for configurable model fields and base model. If you are upgrading (especially from a fork of the development version of django-organization) you may have an extra migration, 0002_auto_20151005_1823, which has been removed.


  • Fixes migrations problem in build


  • Fixes packaging bug


  • Cleaned up installation instructions


  • Drops testing support for Django 1.5 and Django 1.6
  • Adds native Django database migrations
  • Adds tested support for Django 1.7 and Django 1.8


  • Adds app specific signals


  • Various related name fixes in models, registration backends


  • Support for older Django versions with outdated versions of six


  • Allows for configurable TimeStampModel (base mixin for default Organization model) and AutoSlugField (field on default Organization model).


  • Initial Django 1.7 compatability release


  • Fix issue validating organziation ownership for custom organization models inheriting directly from the Organization class.


  • Packaging fix


  • Packaging fix


  • Abstract base models. These allow for custom organization models without relying on mulit-table inheritence, as well as custom organization user models, all on an app-by-app basis.


  • Packaging fix


  • Restructures tests to remove from installed module, should reduce installed package size


  • Fixes another bug in email invitations


  • Fixes bug in email invitation


  • Extends organizaton name length
  • Increase email field max length
  • Adds get_or_add_user method to Organization
  • Email character escaping


  • Use raw ID fields in admin
  • Fixes template variable names
  • Allow superusers access to all organization views
  • Activate related organizations when activating an owner user


  • Bug fix for user model import


  • Bugfixes for deleting organization users
  • Removes additional auth.User references in app code


  • Changes SlugField to an AutoSlugField from django-extensions
  • Base models on TimeStampedModel from django-extensions
  • ForeignKey to user model based on configurable user selection


  • Manage organization models with South
  • Added configurable context variable names to view mixins
  • Added a base backend class which the Invitation and Registration backends extend
  • Lengthed Organization name and slug fields
  • Makes mixin model classes configurable
  • Improved admin display
  • Removes initial passwords


  • Added registration backend
  • Various bug fixes


  • Add RequestContext to default invitation registration view
  • Fix invitations


  • Initial alpha application

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-organizations-2.0.2.tar.gz (34.6 kB view hashes)

Uploaded source

Built Distribution

django_organizations-2.0.2-py2.py3-none-any.whl (51.8 kB view hashes)

Uploaded py2 py3

Supported by

AWS AWS Cloud computing Datadog Datadog Monitoring Facebook / Instagram Facebook / Instagram PSF Sponsor Fastly Fastly CDN Google Google Object Storage and Download Analytics Huawei Huawei PSF Sponsor Microsoft Microsoft PSF Sponsor NVIDIA NVIDIA PSF Sponsor Pingdom Pingdom Monitoring Salesforce Salesforce PSF Sponsor Sentry Sentry Error logging StatusPage StatusPage Status page