> For the complete documentation index, see [llms.txt](https://corpus-core.gitbook.io/iot-colibri-stateless/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://corpus-core.gitbook.io/iot-colibri-stateless/applications-and-colibri-products/use-cases/access-rights-and-authorization.md).

# Access, Rights, and Authorization

* **Access Control for Physical Infrastructure**\
  Devices verify access rights for doors, machines, vehicles, or restricted areas based on verifiable permissions instead of centralized access control systems. Authorization decisions are made locally by validating cryptographic proofs of access rights, enabling operation even during network outages or backend failures. This model reduces reliance on always-online access management services and allows access policies to be enforced consistently across organizational boundaries.
* **Delegated and Time-Bound Permissions**\
  Temporary, conditional, or revocable access rights are enforced locally by devices without continuous connectivity to a central authority. Devices verify whether permissions are valid with respect to time, scope, or contextual conditions encoded in verifiable state. This enables flexible delegation models such as temporary access for maintenance, leasing scenarios, or shared infrastructure usage without introducing centralized control points.
* **Ownership and Custody Management**\
  Devices verify ownership, leasing, or custodial relationships directly using verifiable state. This enables secure handover, resale, or shared usage models without relying on manufacturer-operated services. Ownership changes can be enforced and audited over long device lifetimes, reducing dependency on proprietary backend systems and mitigating risks associated with vendor discontinuation.
* **Verifiable License Management**\
  Devices enforce usage rights for software, data, or physical capabilities based on verifiable license state rather than centralized licensing servers. License conditions such as validity period, usage limits, feature activation, or transferability are evaluated locally using cryptographic proofs.\
  This enables licensing models that remain enforceable under intermittent connectivity and across organizational boundaries. Devices verify license status without contacting vendor-operated services, reducing dependency on proprietary licensing infrastructure and enabling long-lived deployments, secondary markets, and decentralized distribution models.