AllianceAuth Contacts
This is a plugin for AllianceAuth that lets alliances and corporations track and manage their contacts (i.e. standings).
Overview
Tracking an Alliance or Corporation
Users with the right permission can add an alliance or corporation just by clicking on the + button in the index page.
Viewing Contacts
The index page shows all the alliances and corporations that have been added and are available for that user, that means every alliance or corporation in which the user has a character. Superusers can see all the alliances and corporations.
In every alliance or corporation view, the user can see the contacts and their standings. If it has the right permissions, the user can see and edit notes or trigger a manual update of the contacts.
Server Links
From version 1.0.0 users with the right permissions can see or edit server links. These consist of a URL and an optional password and can be used to save discord invites, TS3 server details and such.
Secure Groups integration
If the Secure Groups plugin is installed, a new smart filter will appear in the admin panel of AA Contacts. It allows to filter users by the standings a corporation or alliance has set for them or their alliance/corporation.
Note: when multiple corporations/alliances are set, the logic applies an OR condition, i.e. it is sufficient that at least 1 corp/alliance meets the requirement for the filter to pass. If you want to apply an AND condition, you need to create one filter per condition and put them together in the smart group.
Fields
- comparison: comparison operator to use
- standings: the standing to compare against
- check type:
- at least one character: if at least one character passes the filter, the user passes the filter
- all characters: all characters have to pass the filter for the user to pass the filter
- no character: opposite of all characters
- only main: consider only the main character
- corporations and alliances: groups that have set the standings
Installation
-
Install the package. If you have a traditional installation, run the following command in your terminal:
pip install aa-contacts
If you have a Docker installation instead, add to your
requirements.txtfile:aa-contacts==x.y.z
with the desired version and rebuild the Docker stack.
-
Add
'aa_contacts',to yourINSTALLED_APPSinlocal.py. -
Run migrations and collectstatic:
python manage.py migrate python manage.py collectstatic
or, if you are on docker:
auth migrate auth collectstatic
-
Add the update task at the end of the
local.py:# AA Contacts CELERYBEAT_SCHEDULE['aa_contacts_update_all_contacts'] = { 'task': 'aa_contacts.tasks.update_all_contacts', 'schedule': crontab(minute='0'), 'apply_offset': True, }
-
Restart Supervisor if you are on a traditional install or the docker stack if you are on docker.
Settings
| Setting | Description | Default |
|---|---|---|
AA_CONTACTS_TASK_JITTER |
Maximum number of seconds for a task to be delayed. This helps to prevent tasks from running at the same time and spreads the load both on workers and on ESI. | 300 |
Permissions
| Permission | Description |
|---|---|
manage_alliance_contacts |
Can add tokens for the alliance and trigger manual updates |
manage_corporation_contacts |
Can add tokens for the corporation and trigger manual updates |
view_alliance_notes |
Can view contact notes for alliance contacts. If combined with manage_alliance_contacts, can also edit notes. |
view_corporation_notes |
Can view contact notes for corporation contacts. If combined with manage_corporation_contacts, can also edit notes. |
view_alliance_server_links |
Can view server links for alliance contacts. if combined with manage_alliance_contacts, can also edit server links. |
view_corporation_server_links |
Can view server links for corporation contacts. if combined with manage_corporation_contacts, can also edit server links. |
Metadata
Release files for aa-contacts 1.0.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 | |
|---|---|---|---|
| aa_contacts-1.0.1.tar.gz | 968.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aa_contacts-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 MB
Release files / aa_contacts-1.0.1.tar.gz
| Download URL | aa_contacts-1.0.1.tar.gz |
|---|---|
| Size | 968.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
acf66385999132738494f272f99e10dfa0ed6d68f39c8756ba6d527a165fb304
|
|
BLAKE2b-256 checksum How to use checksums |
3dbaddff2e1f44fb28b57cb35daa50c5246f6b492e15ec815849b84d0de29d4b
|
| 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 16, 2026.
Transparency logRelease files / aa_contacts-1.0.1-py3-none-any.whl
| Download URL | aa_contacts-1.0.1-py3-none-any.whl |
|---|---|
| Size | 995.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b99afa784f3f881168dc1835a30a5dcbf9158fa781a72f7cb97858feea62cc8e
|
|
BLAKE2b-256 checksum How to use checksums |
8a6b711863ed96eeb725bc42faac7806c0b13b7411072435771a8d916ebe9bfb
|
| 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 16, 2026.
Transparency log