Vetting
This is a plugin for pretix.
Lets existing attendees vouch for people who want to join an event. Orders for the selected products stay pending approval until enough attendees have vouched for the applicant.
Configure it under Settings → Vetting in your event. The products you select must require approval.
There are two ways to vouch, and you can enable either or both:
References: during checkout, applicants enter the email addresses of people attending who know them. If an address belongs to an attendee who is allowed to vouch, that person gets an email with a link where they answer “I vouch for them”, “I don’t vouch for them” or “I don’t know them”. Addresses that don’t match anyone are accepted without telling the applicant, so the checkout can’t be used to find out who is attending. Organizers see them in the backend.
Invites: once their own vetted order is approved, attendees get invite codes on their order page. Someone who orders with one of these codes counts as vouched for by the attendee who handed it out.
You choose who can vouch (approved attendees of this event, attendees of the organizer’s past events, or both), whether they need to have paid, and optionally which products allow vouching. When enough people vouched, the order is either approved automatically or the application is marked as ready for you. When someone doesn’t vouch, the application is either held for you to review or, after a number of negative answers, denied. You can always approve or deny an order yourself.
To let someone in without vetting, create a voucher and tick Skip vetting (also available when creating vouchers in bulk). Orders that use such a voucher for every product that needs vetting skip the vetting step at checkout and are approved right away, unless something else in the order still needs approval.
Unanswered requests get a reminder and expire after a configurable number of days. Expiry needs pretix’s periodic task (runperiodic) to run.
The backend shows the vouches on each order and lists all open applications under Vetting in the event navigation. Applicants only see how many vouches they have received, never who declined.
Development setup
Make sure that you have a working pretix development setup.
Clone this repository.
Activate the virtual environment you use for pretix development.
Execute python setup.py develop within this directory to register this application with pretix’s plugin registry.
Execute make within this directory to compile translations.
Restart your local pretix server. You can now use the plugin from this repository for your events by enabling it in the ‘plugins’ tab in the settings.
This plugin has CI set up to enforce a few code style rules. To check locally, you need these packages installed:
pip install flake8 isort black docformatter
To check your plugin for rule violations, run:
docformatter --check -r . black --check . isort -c . flake8 .
You can auto-fix some of these issues by running:
docformatter -r . isort . black .
To automatically check for these issues before you commit, you can run .install-hooks.
License
Copyright 2026 Christiaan de Die le Clercq (techwolf12)
Released under the terms of the Apache License 2.0
Metadata
Release files for pretix-vetting 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pretix_vetting-0.1.0.tar.gz | 37.8 kB | With provenance | Details for pretix_vetting-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pretix_vetting-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for pretix_vetting-0.1.0-py3-none-any.whl |
Total release size: 97.7 kB
Release files / pretix_vetting-0.1.0.tar.gz
| Download URL | pretix_vetting-0.1.0.tar.gz |
|---|---|
| Size | 37.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ead63e048045939062cf38a0f0fedf3328d28cfdd6999e5cb5ca2584a603c48
|
|
BLAKE2b-256 checksum How to use checksums |
75ed44dc9858fad6fb0edc04ca9a2eea3d2299e1ce8d2058de08b6b678760132
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 19, 2026.
Transparency logRelease files / pretix_vetting-0.1.0-py3-none-any.whl
| Download URL | pretix_vetting-0.1.0-py3-none-any.whl |
|---|---|
| Size | 59.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d384f3552014c43d6c78ca675869aec0678a96abefa8e91617f1b58fc848be70
|
|
BLAKE2b-256 checksum How to use checksums |
1b44f5ca85a6b8811f66bdecee2b091c59e7899ce1eddbcafe4ea83eb4edcc05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 19, 2026.
Transparency logSecurity for pretix-vetting 0.1.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pretix_vetting-0.1.0.tar.gz
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 Nov 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.