Check your Docupilot folder layout, then add new ones as approved steps.
Docupilot generates PDFs, contracts, and invoices from templates. Connect it with an API key and Luumen can read your folder structure and confirm which account it is acting as. When a new folder is needed for a team or document type, Luumen shows the plan first and creates it after you approve.
4 tools: 2 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Docupilot 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 docupilot folder, create docupilot folder. 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 Docupilot — 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.