Read your org map, then change roles and groups as approved steps
Connect Peerdom and Luumen can read your organization map the way your team sees it: peers, roles, groups, and the custom fields you actually use. Ask who holds a role, or which group a team sits under, and get an answer from live data. Changes — creating a role, moving a group, marking a peer as former — are previewed and approved before they land. Authentication is by API key.
19 tools: 5 read, 14 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Peerdom 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.
This connection exposes write actions such as create custom field definition, create group, create peer, create role, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Peerdom — 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.