Skip to main content

AA Permission Management

Version License Python Django pre-commit pre-commit.ci status Code Style: black Checks codecov Translation status Contributor Covenant Discord Alliance Auth Compatibility

ko-fi

Django Permission Management in the Alliance Auth Frontend



Overview

This module provides a user interface for managing permissions within the Alliance Auth application. It allows to assign and revoke permissions for groups, and states.

AA Permission Management

For EVE Online alliances, the number of people in a group or state can grow quite large, which can lead to performance issues when trying to manage permissions through the admin backend. This module provides a more efficient way to manage permissions for large groups and states in the Alliance Auth frontend.

Installation

To install the AA Permission Management module, follow these steps:

Bare Metal Installation

Step 1: Install the Module

Make sure you're in the virtual environment (venv) of your Alliance Auth installation Then install the latest release directly from PyPi.

pip install aa-permission-management==1.2.1

Step 2: Configure Alliance Auth

Add aa_permission_management to the INSTALLED_APPS in your local.py file.

INSTALLED_APPS += [
    # ...
    "aa_permission_management",  # https://github.com/ppfeufer/aa-permission-management
    # ...
]

Step 3: Run Static Collection, Migrations, and Restart Alliance Auth

After adding the module to your configuration, run the following commands:

python manage.py collectstatic --noinput
python manage.py migrate aa_permission_management

sudo systemctl restart supervisor

Docker Installation

Step 1: Add the App

Add the app to your conf/requirements.txt:

aa-permission-management==1.2.1

Step 2: Configure Alliance Auth

Add aa_permission_management to the INSTALLED_APPS in your local.py file.

INSTALLED_APPS += [
    # ...
    "aa_permission_management",  # https://github.com/ppfeufer/aa-permission-management
    # ...
]

Step 3: Build Auth and Restart Your Containers

After adding the module to your requirements and updating the configuration, build your Docker images and restart your containers to apply the changes.

docker compose build --no-cache
docker compose --env-file=.env up -d

Step 4: Finalize the Installation

After the containers are up and running, run the migrations for the new module.

docker compose exec allianceauth_gunicorn bash

auth collectstatic
auth migrate

Changelog

See CHANGELOG.md

Translation Status

Translation status

Do you want to help translate this app into your language or improve the existing translation? - Join our team of translators!

Contributing

You want to contribute to this project? That's cool!

Please make sure to read the Contribution Guidelines.
(I promise, it's not much, just some basics)

Metadata

Release files for aa-permission-management 1.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aa-permission-management 1.2.1
File Size Uploaded
aa_permission_management-1.2.1.tar.gz 81.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for aa-permission-management 1.2.1
File Interpreter ABI Platform
aa_permission_management-1.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 204.6 kB

Release files / aa_permission_management-1.2.1.tar.gz

Download URL aa_permission_management-1.2.1.tar.gz
Size 81.3 kB
Tags Source
SHA-256 checksum
How to use checksums
2bbc735f848f162f187209cee04a8eb37e520af151fad5205d7097f9157b13f7
BLAKE2b-256 checksum
How to use checksums
d1f245b9e52f9e28013eed43a80e95307586f2b742746b672a4b0779d8372c66
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 Oct 6, 2026.

Transparency log

Release files / aa_permission_management-1.2.1-py3-none-any.whl

Download URL aa_permission_management-1.2.1-py3-none-any.whl
Size 123.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1a0fd23753a1fae5b569ae0002a20ef4aa98cb1346fa8793b26a1849cbc09871
BLAKE2b-256 checksum
How to use checksums
8c40057a897a329e157237b626a6e1a468cfdcc08efc520f226e6882ca24852d
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 Oct 6, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.2.1 This release

2 release files

1.2.0

2 release files

1.1.0

2 release files

1.0.0

2 release files

0.0.5

2 release files

0.0.4

2 release files

0.0.3

2 release files

0.0.2

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page