Peerdom
for LuumenAI
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.
The Peerdom toolbox
19 tools: 5 read, 14 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Custom Field DefinitionsList custom-field definitions or return one definition by ID so agents can use the organization's real field names and value types.
- ReadGet GroupsList organization groups or return one group by ID, with optional map and peer filters and optional custom-field-value expansion.
- ReadGet Organization ContextReturn the connected Peerdom organization and its maps, including the live map ID and tenant palette needed to create groups and roles.
- ReadGet PeersList peers with optional former-peer and custom-field inclusion, or return one peer by ID with optional roles and custom fields.
- ReadGet RolesList roles or return one role by ID, with optional peer, group, and map filters plus holder, group, representing-node, and custom-field expansions.
- WriteCreate Custom Field DefinitionCreate one custom-field definition that controls a named field's owner, type, multiplicity, order, and visibility. Approval by default
- WriteCreate GroupCreate a group from an existing parent-group anchor on a map. Approval by default
- WriteCreate PeerCreate an email-free person record in the organization; this tool deliberately cannot provision a Peerdom login account. Approval by default
- WriteCreate RoleCreate a role under a parent group on a map using core role fields that do not require Peerdom's Contribution or Goals apps. Approval by default
- WriteDeactivate PeerMark a peer as former. Approval by default
- WriteDelete Custom Field DefinitionPermanently delete a custom-field definition. Approval by default
- WriteDelete GroupPermanently delete one group after reading it to block accidental root-group deletion. Approval by default
- WriteDelete RoleDelete one role by ID and return the deleted role for confirmation. Approval by default
- WriteUnassign Role HolderRemove one peer's assignment from one role without deleting either the peer or the role. Approval by default
- WriteUpdate Custom Field DefinitionRename a custom-field definition and its custom-field API key, or update its labels, display order, or public visibility without changing its value type or owner. Approval by default
- WriteUpdate GroupUpdate selected group properties such as name, parent, external state, color, shape, or custom fields. Approval by default
- WriteUpdate PeerUpdate selected profile fields on an existing peer; omitted fields remain unchanged despite the provider using PUT. Approval by default
- WriteUpdate RoleUpdate selected core role properties without changing Contribution- or Goals-specific settings. Approval by default
- WriteAssign Or Update Role HolderEnsure a peer holds a role, creating the assignment when absent or updating its percentage, focus, and elected-until date when present. Approval by default
One prompt, start to finish
What a governed Peerdom run looks like inside Luumen.
Questions
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 — create custom field definition, create group, create peer, create role, and more — is shown as a plan and requires approval by default, including the 5 actions 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 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.
Put Peerdom to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.