---
title: "Peerdom integration for LuumenAI"
url: "https://www.luumen.ai/integrations/peerdom/"
entity: SoftwareIntegration
category: "Project management"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Peerdom integration for LuumenAI

Read your org map, then change roles and groups as approved steps

## What LuumenAI can do with Peerdom

LuumenAI connects to Peerdom with an API token and exposes 19 tools (5 read-only · 9 write · 5 destructive). For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

## Key facts

- Authentication: API token
- Tools available: 19 tools (5 read-only · 9 write · 5 destructive)
- Deployment: scoped as part of your Pilot, Platform, or Managed rollout
- Category: Project management

## About Peerdom with LuumenAI

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.

## Example tools

Read-only (5 in total):

- `PEERDOM_GET_CUSTOM_FIELD_DEFINITIONS` — List custom-field definitions or return one definition by ID so agents can use the organization's real field names and value types.
- `PEERDOM_GET_GROUPS` — List organization groups or return one group by ID, with optional map and peer filters and optional custom-field-value expansion.
- `PEERDOM_GET_ORGANIZATION_CONTEXT` — Return the connected Peerdom organization and its maps, including the live map ID and tenant palette needed to create groups and roles.
- `PEERDOM_GET_PEERS` — List peers with optional former-peer and custom-field inclusion, or return one peer by ID with optional roles and custom fields.
- `PEERDOM_GET_ROLES` — List roles or return one role by ID, with optional peer, group, and map filters plus holder, group, representing-node, and custom-field expansions.

Write and destructive (14 in total, subject to configured approval policy):

- `PEERDOM_CREATE_CUSTOM_FIELD_DEFINITION` — Create one custom-field definition that controls a named field's owner, type, multiplicity, order, and visibility.
- `PEERDOM_CREATE_GROUP` — Create a group from an existing parent-group anchor on a map.
- `PEERDOM_CREATE_PEER` — Create an email-free person record in the organization; this tool deliberately cannot provision a Peerdom login account.
- `PEERDOM_CREATE_ROLE` — Create a role under a parent group on a map using core role fields that do not require Peerdom's Contribution or Goals apps.
- `PEERDOM_DEACTIVATE_PEER` — Mark a peer as former.
- `PEERDOM_DELETE_CUSTOM_FIELD_DEFINITION` — Permanently delete a custom-field definition.
- `PEERDOM_DELETE_GROUP` — Permanently delete one group after reading it to block accidental root-group deletion.
- `PEERDOM_DELETE_ROLE` — Delete one role by ID and return the deleted role for confirmation.

## Frequently asked questions

### How does LuumenAI connect to Peerdom?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Peerdom on its own?

For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

### Is there an audit trail?

Every call to Peerdom — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/peerdom/