Custom Document Type Library

Manage reusable document templates for AI agent configurations, operational runbooks, guardrails, and any structured .md document your team needs.

Who Is This For?

• Company Admins — define company-wide document types and control who can create new types
• Project Managers — create project-specific types when permitted by the admin
• Developers — create and manage documents within available types

Quick Start

1. Navigate to Documents

Open the sidebar and click Documents > Document Types to see the type library.

2. Create a Document Type

1. Click New Type
2. Browse existing company-wide types first — if one fits, use it
3. Click "None of these fit? Create a new type"
4. Fill in the form:
   • Name: Uppercase identifier (e.g., AGENTS, RUNBOOKS)
   • Display Name: Human-readable label
   • Icon & Color: Visual identification
   • Metadata Fields: Custom fields each document must fill in
   • Conventions: Guidelines shown to users creating documents of this type

3. Create a Document

1. Go to Documents > Document Library > New Document
2. Select the document type
3. Fill in name, metadata fields (auto-generated from type), and markdown content
4. Optionally assign to a project and add tags

4. Bind to a Prompt

On the document detail page, use the Prompt Bindings section to attach the document to stored prompts. The document content will be injected as context during prompt execution.

Document Type Scoping

Scope	Visibility	Who Can Create
Company-wide	All projects in the company	Admins only
Project-specific	Only within that project	Managers (when admin enables it)

Enabling Project-Level Types

Admins can toggle this in Settings:

Allow project owners to create custom document types

When enabled, project managers can create types scoped to their projects.

Promoting a Project Type

If a project-level type proves useful across the company, an admin can promote it to company-wide from the type detail page. This doesn't affect existing documents — they keep working.

Metadata Fields

Each document type can define custom metadata fields that authors must fill in:

Field Type	Input	Example
Text	Free text	Agent runtime, author name
Number	Numeric	Max tokens, timeout seconds
Boolean	Checkbox	Requires approval
Select	Dropdown	Status: draft / review / published
Array	Comma-separated	Required tools, allowed models

Required fields are enforced — a document cannot be saved without them.

Prompt Bindings

Documents can be bound to stored prompts with three injection modes:

Mode	Behavior
Prepend	Document content added before the prompt
Append	Document content added after the prompt
Reference	Document available as a reference (not auto-injected)

Use bindings to attach agent configurations, style guides, or compliance rules to prompts without editing the prompt itself.

API Access

Full CRUD is available via the REST API:

• Custom Document Types API
• Custom Documents API

Example: Agent Configuration Workflow

1. Admin creates type AGENTS with fields: agentRuntime (required), maxTokens, requiredTools (array)
2. Developer creates document "Claude Code Config" with:
   • agentRuntime: "claude-code"
   • requiredTools: ["Read", "Write", "Edit", "Bash"]
   • Content: Full markdown with behavior guidelines
3. Developer binds the document to their "Code Review" prompt (prepend mode)
4. When the prompt executes, the agent configuration is automatically injected as context

Troubleshooting

Issue	Solution
"You do not have permission to create document types"	Ask your admin to grant you a Manager role, or ask them to enable project-level type creation
"Cannot delete type with active documents"	Delete or deactivate all documents of this type first
Metadata validation error	Check that all required fields are filled in and match the expected type
Can't find document types in sidebar	Documents section is available to Developer role and above