You create a key for the agent
An owner or admin creates the key in workspace settings and chooses three things: what the agent can read, which actions it can take, and when the key expires — at most one year out.
If you already use an AI agent for email, planning or paperwork, it can work through LeaseLab instead of around it. Your agent does the reasoning. LeaseLab holds the record, checks what the agent is allowed to do, and records what happened.
It works with any agent or script that can call an HTTP API. You don’t need an agent — or AI at all — to use LeaseLab.
An owner or admin creates the key in workspace settings and chooses three things: what the agent can read, which actions it can take, and when the key expires — at most one year out.
Properties, tenancies, rent, work orders, vendors, open decisions, and signals such as overdue rent or a repeating repair — only the areas you granted. Tenant contact details are off unless you explicitly turn them on.
For example: report a maintenance issue, set a work order’s category, record the outcome of a call to a vendor, or complete a work order within your spending limit. The agent names the action; it never supplies its own permissions.
If the action is allowed for that key and within your limits, it happens and is recorded with the key that made it. If it would go past your limits, nothing changes — it becomes an item in Needs your decision for you to decide. If the key isn’t allowed to take that action at all, the request is refused.
When you connect an agent, LeaseLab sends it the data its key can read, whenever it asks. From there, that agent and whoever provides it handle the data under their own terms, not LeaseLab’s. Grant only what the agent needs, and revoke the key when you stop using it.
Your records and your authority stay in LeaseLab. If you switch agents or AI providers, nothing is lost: revoke the old key, create a new one, and the new agent picks up from the same record.
More in your data and the Privacy Policy.
Start for free