Stateless Tag-Based Authorization Library
Background
Traditional role-based authorization models are not flexible enough to cover all required use cases. On the other side, full-managed ACLs are too complex for account managers to handle. tagth is a simple and flexible authorization model that can be easily implemented and maintained.
Installation
pip install tagth
Tag-Based Authorization
A lightweight model that is based on three concepts:
- a principal and its associated tags,
- a resource and its associated tags,
- an action.
The model adheres to the following principles:
- the model is stateless and purely functional, and it has no internal persistence,
- the model does not interpret the tags or actions, besides the special values,
- the model produces a binary result: either the action is allowed or not.
Principal and Principal Tags
A Principal is an acting entity. A Principal can be a user, a role, a group, or any other entity that can perform actions.
Principal’s auth tag string looks like a comma-separated list of tags: tag_one, tag_two, tag_three. Each tag should be a string that is a valid Python identifier.
A supertag is a tag that is a prefix of another tag. For example, admin is a supertag of admin_user.
Warning: Matching is based on simple string prefix. This means
adminwill matchadmin_user,administrator, andadmin123. Ensure your tag naming scheme accounts for this to avoid unintended access.
A principal is said to possess a tag if the tag or its supertag exists in the principal’s auth tag string.
Special values:
void(can only access resources withanyoneaccess, see below),root(unlimited access).
Resource and Resource Tags
A Resource is an object that can be accessed by a Principal. A Resource can be a user, a channel, a source asset, an extension, a tenant, a campaign, etc.
A resource tag is a string that is a valid Python identifier. NB: there is no such thing as a supertag for a resource tag.
An action is a string that is a valid Python identifier. A superaction is an action that is a prefix of another action. For example, create is a superaction of create_asset.
Warning: Like tags, action matching is based on simple string prefix.
readwill matchreadingandread_all.
Resource auth tag string looks like a comma-separated of colon-separarted pairs of tags and actions: tag_one:read, tag_two:write or multiple actions: tag_one:{read, write}(tags with associated actions).
If the resource auth tag string is empty or contains only whitespace, only the root principal is allowed access.
An action is allowed for a principal if it possesses:
- a tag that is associated with the action
- a tag that is associated with the superaction of the action
- the
roottag
Special values:
anyoneresource tag (any principal is allowed to perform action).allaction (all action are allowed).
Access Resolution
The model makes a decision based on the following three values only:
- the principal’s auth tag string
- the resource’s auth tag string
- the action to be performed
The resolution is binary: either the action is allowed or not.
Examples
Basic Usage
from tagth import allowed
# A regular user with basic permissions
principal_tags = 'user, content'
resource_tags = 'content:read, metadata:write'
# Check if user can read content
allowed(principal_tags, resource_tags, 'read') # Returns True
# Check if user can delete content
allowed(principal_tags, resource_tags, 'delete') # Returns False
# Multiple actions for a resource
principal_tags = 'user, content'
resource_tags = 'content:{read, write}'
# Check if user can read content
allowed(principal_tags, resource_tags, 'read') # Returns True
# Check if user can write content
allowed(principal_tags, resource_tags, 'write') # Returns True
# Check if user can delete content
allowed(principal_tags, resource_tags, 'delete') # Returns False
# Root user has unlimited access
principal_tags = 'root'
allowed(principal_tags, resource_tags, 'anything') # Returns True
# Void user can only access 'anyone' resources
void_tags = 'void'
allowed(void_tags, 'anyone:read', 'read') # Returns True
allowed(void_tags, 'content:read', 'read') # Returns False
Supertags and Superactions
# Principal tags can be supertags
principal_tags = 'admin'
resource_tags = 'admin_user:write, admin_content:delete'
# 'admin' is a supertag of 'admin_user' and 'admin_content'
allowed(principal_tags, resource_tags, 'write') # Returns True
allowed(principal_tags, resource_tags, 'delete') # Returns True
# Actions can have superactions
principal_tags = 'content'
resource_tags = 'content:create'
# 'create' is a superaction of 'create_asset'
allowed(principal_tags, resource_tags, 'create_asset') # Returns True
Special Values
# 'anyone' resource tag allows access to all principals
principal_tags = 'basic_user'
resource_tags = 'anyone:read'
allowed(principal_tags, resource_tags, 'read') # Returns True
# 'all' action allows all actions
principal_tags = 'content'
resource_tags = 'content:all'
allowed(principal_tags, resource_tags, 'read') # Returns True
allowed(principal_tags, resource_tags, 'write') # Returns True
Release files for tagth 1.2.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tagth-1.2.7.tar.gz | 8.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tagth-1.2.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.1 kB
Release files / tagth-1.2.7.tar.gz
| Download URL | tagth-1.2.7.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c6381e8342f7b99bdd4eaba42bed16d540a56cf703b41e0dcf314d8d4976cb65
|
|
BLAKE2b-256 checksum How to use checksums |
5879d93449dbcec1ba7ce11f897dfe32676215a1e2a62436e5292129ad04ff1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 21, 2026.
Transparency logRelease files / tagth-1.2.7-py3-none-any.whl
| Download URL | tagth-1.2.7-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc07ee4214f4eea7994e7bba414584f55b7bedf1cabab1612505ffe81a559919
|
|
BLAKE2b-256 checksum How to use checksums |
c2ab2c968b3ceab635b11aeb4ea878bb3968233fe42d6cb841b43be13c6fc072
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 21, 2026.
Transparency log