Access License or Permit¶
Grant instrument — instantiates Property Rights Bundle Governance
Grants a scoped, conditional, revocable permission to use a resource — without handing over any ownership of it.
An Access License or Permit hands out one slice of the bundle — a defined measure of the use stick — while every other stick stays with the owner. Its defining move is that it is a permission, not an interest: the holder may do a specified thing with the resource but acquires nothing they can keep, mortgage, or assert against the grantor. That is exactly what separates it from an easement (which runs with the land and survives a sale) and from a transfer (which moves ownership itself). A license is scoped (what, where, how much, how long), conditional (comply or forfeit), and revocable — the owner keeps the resource and merely lends out a bounded window of access.
Example¶
A city owns its sidewalks; a restaurant wants four tables out front. Rather than sell or lease the pavement, the city issues a sidewalk-café permit. It scopes the grant: which three metres of frontage, which hours, a maximum table count, a clear-path width for pedestrians. It attaches conditions: proof of liability insurance, no amplified music, tables stored overnight. It sets a term: one season, renewable on good behaviour, revocable on complaint. The restaurant never owns an inch of sidewalk — the public still does — it holds a bounded, revocable permission to use it. When the café quietly adds two more tables and blocks the walkway, the city does not sue for trespass or renegotiate a lease; it simply pulls the permit. That revocability is the whole point: the city lends the use-stick without ever loosening its grip on the pavement.
How it works¶
Issuance does three things and stops there: it draws the scope of permitted use (the metes and bounds of what the holder may do), attaches conditions the holder must keep, and fixes an expiry or revocation trigger that returns the access to the owner. It deliberately does not police outsiders or litigate breaches — detecting a violation and enforcing consequences is a separate mechanism that the permit merely authorises. The license is the grant and its leash, not the patrol.
Tuning parameters¶
- Exclusivity — exclusive vs. non-exclusive; whether one holder or many share the same permitted use. Exclusive grants command a premium but foreclose everyone else.
- Scope breadth — a narrow single-purpose permission vs. a broad one. Narrow protects the owner but multiplies the paperwork; broad is convenient but leaks control.
- Term and renewability — fixed short term vs. evergreen. Short terms preserve the owner's leverage; long or auto-renewing ones invite the holder to rely and invest.
- Revocability — at-will vs. for-cause-only. At-will keeps maximum leverage but chills any holder investment; for-cause is more bankable but harder to exit.
- Transferability — whether the holder may assign or sublicense. Usually no — non-transferability is precisely what keeps this a license and not a disguised sale.
When it helps, and when it misleads¶
Its strength is letting an owner allow use without giving anything away: reversible, low-commitment, and fully retaining the resource. It is the right tool when access should be permission-like and provisional rather than owned.
Its central failure mode is reliance drift — a holder invests season after season as though they owned the spot, until a revocation that is contractually clean lands as de facto expropriation. Sloppy scope compounds this: ambiguity behaves like a broader grant than anyone intended. The classic misuse is drafting a "license" that is really perpetual, irrevocable, and transferable — an easement or a sale wearing a license's label to dodge the formalities and price of one.[1] The discipline that guards against it is to keep scope, term, and revocation explicit, and to match the holder's permitted reliance to the grant's real durability.
How it implements the components¶
exclusivity_and_access_scope— the permit is a scoped grant of access: it fixes who may use the resource, for what, in what quantity, and whether exclusively.revocation_reversion_or_sunset_trigger— every license carries its own expiry and revocation-on-breach; by its own terms the access lapses back to the owner.
It does not police non-holders or enforce a breach — that active exclusion is Exclusion Enforcement Protocol; nor does it move ownership, which is Transfer Assignment or Sale Contract's job.
Related¶
- Instantiates: Property Rights Bundle Governance — a license supplies the scoped, revocable use grant the bundle relies on when access should be lent, not sold.
- Sibling mechanisms: Easement Covenant or Use Restriction · Exclusion Enforcement Protocol · Commons Access Rule · Transfer Assignment or Sale Contract · Title or Entitlement Registry · Rights Bundle Matrix
Notes¶
The practical tell that separates a license from an easement is revocability plus running-with-the-land: a license is personal and can be pulled; an easement is an interest that transfers with the property and cannot simply be withdrawn. Because reliance accretes silently, the boundary is where disputes concentrate — a long-tolerated permit can be argued to have hardened into something more, which is why explicit term and revocation language earns its keep.
References¶
[1] In common-law property a bare license is revocable and personal to the holder, whereas an easement is a durable interest that runs with the land and survives its sale. Mislabelling one as the other — using "license" for what functions as a permanent, transferable interest — is a recurring source of dispute, which is why the revocability and scope terms are load-bearing. ↩