A tuple is a structured permission fact used in relationship-based authorization. It usually records a subject, a relation, and a resource, such as user X can view document Y. In these systems, tuples are stored as data and combined to answer access questions.
Tuples matter because they make authorization explicit and auditable. Security teams can review who should have access, trace why a decision was made, and revoke a single fact instead of editing scattered application logic. In attacks, a bad or stale tuple can overgrant access, especially in multi-tenant apps where one customer must never see another customer’s data. Defenders use tuple stores to centralize permissions, support least privilege, and reduce hidden authorization bugs.