Read door locks and access grants, then change access as an approved step
Connect the Seam workspace Luumen uses an API key to reach, and you can ask who holds access to which door, which devices a provider account brought in, and whether a lock command actually landed. When something needs to change, Luumen shows the grant, the spaces, and the validity window first, then waits for your approval.
10 tools: 6 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Seam run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add access methods to grant, create access grant, delete access grant, update access grant — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Seam — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.