Skip to content
👫 Multi-user accounts for Django projects
Python HTML Makefile
Failed to load latest commit information.
docs Update docs and history for release 0.7.0 Apr 3, 2016
example Removes South and south_migrations Sep 28, 2015
organizations Cleanup imports Apr 3, 2016
test_accounts Removes South and south_migrations Sep 29, 2015
test_custom Adds native Django migrations Apr 11, 2015
test_vendors Removes South and south_migrations Sep 29, 2015
tests Make organization owner admin user by default Apr 3, 2016
.coveragerc Adds test coverage reporting Jul 6, 2014
.gitignore Add pycharms .idea folder to .gitignore Feb 29, 2016
.travis.yml Disable travis pypy3 testing Sep 29, 2015
AUTHORS.rst Update authors Jan 30, 2016
CONTRIBUTING.rst Updates contribution guidelines [ci skip] Jul 27, 2014
HISTORY.rst Update docs and history for release 0.7.0 Apr 4, 2016
LICENSE Update copyright year Jan 6, 2016 Move test fixtures to test module Jan 25, 2014
Makefile Add a Makefile Sep 29, 2015
README.rst Update docs and history for release 0.7.0 Apr 4, 2016 Remove swappable base model for TimeStampedModel and fix slug field Apr 3, 2016 Remove swappable base model for TimeStampedModel and fix slug field Apr 4, 2016
requirements-dev.txt Break out requirement files May 31, 2014
requirements-test.txt Remove swappable base model for TimeStampedModel and fix slug field Apr 4, 2016
setup.cfg Add support for Wheel packaging May 18, 2014 Removes South and south_migrations Sep 29, 2015
tox.ini Use full Django 1.9 version Jan 6, 2016



Info:Groups and multi-user account management
Version: 0.7.0
Author: Ben Lopatin (
Build Status PyPI relesae PyPI downloads:

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


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

pip install django-organizations

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 = patterns('',
    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:

ORGS_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.

Development & Contributing

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
  • Python 3 readiness

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

Targets & testing

The codebase is targeted at tested against:

  • Django 1.8.x against Python 2.7, 3.4, 3.5
  • Django 1.9.x against Python 2.7, 3.4, 3.5

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



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



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

Something went wrong with that request. Please try again.