Dosu's configuration is organized into four levels: organization, space, deployment, and data source. Each level controls different aspects of how Dosu works with your team and codebase.

Organization Settings#

Organization settings apply to your entire Dosu account.

Settings > Organization: Organization name and avatar (owners and admins only)

Settings > Members: Invite and manage team members, assign roles (owner, admin, member). See Member Invitation for details.

Settings > Billing: Subscription plan, seat count, payment methods

Space Settings#

Spaces are projects within your organization. Each space has its own knowledge base and can be configured independently.

Settings > Project > Space Name

• Space name
• Visibility (public or private)
• Auto-Accept Review

Public spaces allow unauthenticated users to view documentation and ask questions. See Public Spaces for details.

Auto-Accept Review: Controls whether Dosu's proposed documentation changes are applied automatically or require manual review. When enabled, documentation updates are accepted automatically. When disabled, you must manually review and accept proposed changes. Find this setting at app.dosu.dev/settings/spaces.

Deployment Configuration#

Deployments connect Dosu to platforms like GitHub, GitLab, and Slack. Each deployment type has its own configuration options controlling how Dosu responds, labels issues, and maintains documentation. Only owners and admins can create or modify deployments.

• GitHub Configuration
• GitLab Configuration
• Slack Configuration

For setup instructions, see Setting Up a GitHub Deployment or Setting Up a Slack Deployment.

Data Source Configuration#

Data sources determine what content Dosu indexes and searches. See Data Source for an overview of how data sources work.

Available integrations:

• GitHub: Repositories, issues, PRs, discussions, wikis. Configure include and ignored file patterns to control which files are indexed.
• GitLab: Projects, issues, merge requests. Configure include and ignored file patterns to control which files are indexed.
• Slack: Channel messages and threads
• Web: Public websites and documentation. Note: Web data sources serve as placeholder configurations only. When you configure a web data source, no website content is crawled, indexed, or stored. The data source is immediately marked as "synced" for UI consistency with other data source types, but no actual data syncing occurs. Web information is accessed only at query time through real-time search tools (Tavily), not through any pre-indexed content.
• Coda: Docs and pages (Beta)
• Confluence: Spaces and pages (Beta)

File pattern filtering (GitHub and GitLab):

Control which files are indexed from your repositories using include and ignored file patterns. Both use Unix wildcard (glob) pattern syntax (e.g., src/**, *.md, docs/**/*.rst). Configure these patterns in the data source configuration UI for GitHub and GitLab data sources.

• Include file patterns: Only files matching these patterns will be indexed. Leave empty to index all files (subject to ignored patterns). This feature is available in the configuration UI for both GitHub and GitLab data sources.
• Ignored file patterns: Blacklist files from indexing. Files matching these patterns are always excluded, regardless of include patterns.

Filtering logic: Files are evaluated in two steps. First, files matching any ignored pattern are excluded. Second, if include patterns are specified, only files matching at least one include pattern are indexed. If no include patterns are specified, all remaining files (after applying ignored patterns) are indexed.

Example use cases for include patterns:

• *.md — Index only Markdown files
• docs/** — Index only files in the docs directory and its subdirectories
• backend/** — Index only files within the backend directory
• src/**/*.py — Index only Python files within the src directory
• README.md — Index only the README file

Documentation Settings#

Documentation settings control how Dosu generates and maintains your docs. Find these under your knowledge store deployment settings.

Auto Publish: When enabled (default), generated documentation publishes automatically. When disabled, new documents require manual review.

Suggest New Topics: When enabled, Dosu analyzes merged PRs and suggests documentation topics.

Custom Instructions: Provide custom instructions to shape how the documentation agent writes content.

Style Guidelines: Configure style guidelines to ensure consistent documentation style across your space. Dosu uses two complementary mechanisms to maintain consistency:

1. Style Guidelines (configured here): Explicit rules for voice, tone, and formatting that you define for your documentation.

2. Automatic Pattern Matching: When creating documentation through the UI, Dosu automatically appends an instruction to your request: "Always search for existing similar documentation. If similar documentation exists, model the new document's structure and style on it (unless my request above or style guidelines say otherwise)". This happens automatically for UI-triggered documentation generation—you don't need to configure anything.

These mechanisms work together to maintain consistency. Style guidelines provide your explicit preferences, while automatic pattern matching ensures new documents follow the structural patterns of your existing documentation. The precedence order is: your specific request takes priority, followed by style guidelines, followed by learned patterns from existing documentation.

Documentation Updater Instructions: Provide custom instructions to control how the Documentation Updater updates existing documentation. Use this to enforce specific update behaviors, such as preserving certain sections or following particular formatting rules when modifying documents.

Stale Doc Check: Configure when Dosu checks for outdated documentation on pull requests. When enabled, Dosu identifies documents that may need updates based on code changes.

Monitored Paths: Control which directories trigger documentation updates. This setting is available in your deployment configuration settings and offers two modes:

• All paths (default): Monitors all repository changes
• Specific paths: Select directories using an interactive directory tree picker

When "Specific paths" is selected, an interactive directory tree view displays your repository's structure, allowing you to select which directories should trigger documentation updates. The directory tree is loaded from your indexed codebase. This setting is disabled when Stale Doc Check is turned off.

Technically, monitored paths are stored as an array of glob pattern strings (e.g., ["src/**", "docs/**/*.md"]). When the array is empty, all paths are monitored by default.

Dosu automatically skips updating synced pages (from GitHub, GitLab, Notion, or Confluence data sources) when their source files are modified in the same pull request. The sync mechanism handles these updates directly.

Response Guidelines#

Each deployment can have custom response guidelines that shape how Dosu writes responses. Use this to enforce tone, formatting, or content requirements specific to your project.

Find this under Settings > Deployments > Deployment > Response Guidelines.

Response Drafts#

When reply mode is set to Auto Draft, Dosu generates responses for review before posting. See Response Drafts for details on reviewing and approving drafts.