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'

There is also a lightly tested way to use your own user model, rather than the
default auth.User model. Set the AUTH_USER_MODEL setting to the dotted
model name of your custom user model, following the procedure in Django 1.5:

AUTH_USER_MODEL = 'myuserapp.MyUser'

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.

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 setup.py 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.4.x against Python 2.6 and Python 2.7

Django 1.5.x against Python 2.6, Python 2.7, and Python 3.3

Django 1.6.x against Python 2.7 and Python 3.3

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

tox

Submitting

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