← Back to Solution Library
Company-Wide Collaboration

IT Team Knowledge Base

Key Takeaways

IT Team Knowledge Base helps technical teams find system configs fast without complex wikis. Instead of hunting through tickets and Slack, you get one workspace. Teams document servers, track network changes, and preserve infrastructure expertise. MatrixFlows includes unlimited team collaboration. No per-user fees that force companies to limit who contributes.

  • Example Outcome: Technical teams find configs faster - some report 85% search time reduction within weeks
  • Deploy in 3 Days: Pre-built infrastructure templates - not months building custom wiki structures
  • No User Limits: Include entire IT organization with unlimited users - traditional tools charge $50-150 monthly per person
  • AI That Understands Tech: Search works with system names and error codes - not just keyword matching
  • Getting Started: Get started with infrastructure docs, team collaboration, and AI search

💡 Quick Answer: IT Team Knowledge Base helps technical teams document server configs, network architecture, and troubleshooting procedures in one searchable workspace. Most teams deploy within 3 days.

⚡ Bottom Line: Instead of recreating solutions from memory, get centralized workspace that preserves infrastructure knowledge and onboards new engineers faster.

IT Team Knowledge Base (Live, Deployable)

This is an interactive system you can deploy today — not a static template.

The IT Team Knowledge Base application is built on the MatrixFlows platform and runs inside your MatrixFlows workspace alongside other apps and workflows. This is a live, browser-based system where technical teams document infrastructure while new engineers find solutions instantly. Teams access it through docs.yourcompany.com or integrate with existing IT tools.

Deployment:

  • Launch quickly using pre-built technical documentation templates
  • Customize taxonomy, security controls, and workflows without coding
  • Every plan includes unlimited IT team access and structured documentation

What's included:

  • Team-facing workspace with AI-powered technical search
  • Structured templates for servers, networks, security protocols, deployment procedures
  • Real-time collaboration through Matrix with version control
  • Knowledge gap tracking and documentation requests in Inbox

The application runs in your MatrixFlows workspace. Integrates with existing IT systems if needed.

Why technical teams need IT Team Knowledge Base

IT Team Knowledge Base helps technical teams preserve expertise without losing knowledge. Here's what changes:

Find System Configurations Instantly

IT staff search server specs and network diagrams in one place. No more hunting through Confluence, Jira tickets, and Slack threads. Your workspace shows infrastructure docs organized by system type and data center.

Search time drops from hours weekly to under 30 minutes. Configs live in one searchable location instead of scattered across systems. Technical teams focus on infrastructure improvements instead of asking "where did we document that?"

Teams with distributed engineers see big productivity gains. Everyone accesses complete documentation from one platform instead of fragmenting knowledge.

Preserve Knowledge When People Leave

Senior engineers document system architecture before they leave. Their expertise stays in searchable formats instead of walking out the door. New hires access proven configurations from day one.

Teams that centralize technical knowledge report faster onboarding. Comprehensive documentation available immediately instead of requiring extensive mentorship. Onboarding time drops from months to weeks.

Organizations see fewer repeated mistakes when documented solutions are accessible. Everyone uses same guidance instead of expertise trapped in individual experience.

Collaborate on Complex Systems

Multiple engineers work on same infrastructure docs simultaneously. Network team documents switches and routers. Security team adds firewall rules. DevOps team maintains deployment procedures. Everyone sees current state.

Real-time collaboration eliminates duplicate wikis and conflicting versions. Engineers work together on living documentation. No more multiple outdated copies across different systems.

Stop Recreating Solutions

Your team solved database performance issue last year. Solution exists somewhere in old Jira ticket. Engineer spends hours re-diagnosing before realizing someone fixed this already.

With centralized knowledge, search finds previous solution in seconds. Team builds on existing expertise instead of starting over. Organizations report big reduction in duplicate troubleshooting work.

Why scattered IT documentation doesn't work for technical teams

IT teams struggle with lost knowledge because infrastructure expertise stays trapped. Information fragments across Confluence pages, old tickets, and Slack threads. Each system has different conventions. Nobody knows current state.

Organizations lose big productivity hunting for information. Documentation scattered across disconnected systems without unified search.

The three biggest problems with fragmented IT knowledge:

1. Critical Knowledge Lives in Tickets

Engineer solved production outage last month. Root cause analysis exists only in closed Jira ticket. Six months later, similar issue happens. New engineer can't find original ticket. Spends hours re-diagnosing what someone already solved.

Business Impact: Example outcome: Technical teams waste 10-15 hours monthly re-solving problems. Organizations lose $40-80K annually in duplicate work per team.

2. Knowledge Walks Out Door With People

Senior DevOps engineer leaves. Takes years of deployment expertise. Knows which systems break under load. Understands why certain configs exist. None of this documented.

Business Impact: Losing senior technical staff costs months of reduced productivity. For specialized roles, knowledge loss impacts $50-100K through delayed work.

3. Documentation Spreads Across Too Many Tools

Network docs live in Confluence. Server configs in wiki pages. Security protocols in SharePoint. Runbooks in PagerDuty. During outage, engineer checks multiple different systems.

Business Impact: Fragmented docs increase mean time to resolution 2-3x during outages. Multi-tool search adds hours to every troubleshooting effort.

How IT Team Knowledge Base solves technical documentation challenges

Here's how the application behaves once deployed:

IT Team Knowledge Base gives technical teams one workspace. Teams document infrastructure, share solutions, and preserve expertise. Engineers search system configs, review network architecture, and collaborate on procedures from one platform.

Technical Search That Understands Systems

Engineers search using system names and error codes. AI understands "prod database replication lag" and shows relevant runbooks. Most searches find needed information in under 30 seconds.

AI recognizes infrastructure concepts and system dependencies automatically. Your team stops asking Slack "where did we document the backup procedure?" Search effectiveness improves when AI understands technical relationships.

Real-Time Collaboration on Infrastructure Docs

Multiple engineers edit same network diagram simultaneously. Security team adds firewall rules while network team updates switch configs. See who's working on what right now. Comments appear instantly.

Collaboration happens without merge conflicts like wiki systems create. Engineers work together on living documentation with immediate visibility.

Version History for Critical Changes

Track every change to infrastructure documentation. See who modified deployment procedure and when. Compare server config from last month versus today. Roll back if needed.

Full audit trail for compliance prevents "who changed the production runbook?" mysteries. Organizations report improved change control when complete history is accessible.

Structured Technical Content

Create custom templates for different documentation types. Server specs have different fields than network diagrams. Security protocols need different structure than deployment procedures.

Your documentation matches how technical work actually happens. Documentation quality improves when structure matches infrastructure reality.

What you can do with IT Team Knowledge Base

  • AI-Powered Technical Search: Find infrastructure docs using natural language - search "database backup procedure" and get relevant runbooks instantly
  • Structured Documentation Templates: Create consistent technical docs - server, network, security, deployment templates match actual infrastructure work
  • Real-Time Collaboration: Multiple engineers edit simultaneously - network team and security team work together without conflicts
  • Version Control: Track every infrastructure change - see who modified what and when for compliance
  • Custom Taxonomy: Organize by data center, system type, environment - structure matches your infrastructure
  • Gap Identification: System tracks what engineers search for - identify missing documentation based on team patterns
  • Mobile Access: Engineers find configs from anywhere - works on desktop, tablet, and phone

What's included in IT Team Knowledge Base

Complete application ready to deploy once you add your infrastructure documentation. Everything technical teams need to preserve expertise through structured documentation—all organized from your knowledge foundation.

Matrix: Technical Documentation Foundation

Organize unlimited IT content types in flexible structures:

  • System Configuration Documentation: Server specs, network architecture, database configs organized by environment and data center with version tracking
  • Runbook Management: Operational procedures, incident response playbooks, maintenance checklists teams follow during outages
  • Network Infrastructure Docs: Network diagrams, switch configs, firewall rules helping engineers understand topology
  • Security Protocol Library: Access policies, compliance procedures, security assessments ensuring consistent implementation
  • Deployment Documentation: Release procedures, rollback plans, environment configs enabling confident deployments
  • Vendor and License Tracking: Software licenses, support contracts, vendor contacts preventing surprise renewals
  • Troubleshooting Knowledge: Previous incidents, root cause analyses, diagnostic procedures, resolution patterns
  • Architecture Documentation: System designs, data flows, integration patterns, technical decisions and rationale

Flows: Team Documentation Workspace

Pre-built workspace combining multiple collaboration methods:

Main capabilities:

  • AI-powered technical search understanding infrastructure terminology
  • Structured documentation templates for servers, networks, security, deployments
  • Real-time collaboration with live updates and change visibility
  • Smart organization by data center, system type, environment, criticality
  • Version control with comparison, rollback, and audit trail

Integrated Experience: Search understands technical relationships. Templates enforce consistency. Collaboration prevents conflicts.

Deployment Options: Internal portal at docs.engineering.company.com, embedded in Slack/Teams, integrated with existing IT tools

Inbox: Knowledge Management & Requests

Manage technical team coordination and documentation needs:

  • Internal collaboration on infrastructure changes and solutions
  • Documentation requests identifying missing content
  • Subject matter expert assignment for efficient documentation
  • Gap tracking monitoring which infrastructure areas lack documentation

AI & Automations

Intelligence layer powering all capabilities:

  • Technical Concept Understanding: Natural language search recognizing infrastructure relationships and system dependencies
  • Documentation Generation: Create structured docs from engineer notes maintaining technical accuracy
  • Related Content Discovery: Surface relevant runbooks and previous incidents when viewing infrastructure
  • Auto-Categorization: Organize content by system type and data center automatically
  • Outdated Content Detection: Identify documentation needing updates based on system changes
  • Search Pattern Analysis: Track what engineers search for, identify documentation gaps
  • Change Notifications: Alert documentation owners when infrastructure changes

📚 Learn more: Knowledge Work Platform | Digital Experience Applications | AI & Automation | Conversations Inbox

How MatrixFlows makes IT Team Knowledge Base work

This is how the live system works under the hood:

MatrixFlows gives you four tools to build IT Team Knowledge Base. Matrix organizes infrastructure documentation. Flows creates team workspace. Inbox manages requests. AI helps with search and content creation. Everything connects so technical knowledge stays current automatically.

Organize technical content in Matrix

Start with Matrix where IT team documents infrastructure. Create tables for servers, networks, security policies, and deployment procedures. Store system architecture diagrams. Document vendor relationships. Not random wiki pages - structured docs matching actual infrastructure.

Organize by Data Center → System Type → Specific Server. Or by Application → Environment → Configuration. Your structure reflects real infrastructure instead of confusing IT hierarchy.

Your entire technical organization contributes managing related areas. Network engineers document switches. Security team adds policies. DevOps maintains deployment docs. Database admins document schemas. Everyone works in same workspace without access restrictions.

Technical organizations with multiple offices structure by Region → Data Center → System. Under each system organize by Configuration, Procedures, Troubleshooting. When engineers search for specific data center network info, they see only relevant regional documentation.

Build technical workspace in Flows

Use Flows to create internal IT knowledge portal. Start with Technical Documentation Hub template. Customize in hours. Add IT branding. Organize by technical domains instead of random categories. Set up search for technical terminology. Configure access based on security requirements.

Deploy to docs.engineering.company.com. Embed in Slack workspace. Add to engineering onboarding. Engineers access technical knowledge where they already work instead of another system.

Once deployed, the application updates instantly when infrastructure changes. Migrated to new servers? Update docs today. Changed network topology? Revise diagrams this afternoon. Updates take minutes without change control cycles.

IT teams without documentation specialists control everything using visual tools. Add infrastructure docs. Update procedures. Organize by system. Configure security. All done through interface without coding.

Handle documentation requests in Inbox

When engineers need documentation that doesn't exist, requests flow into Inbox. Team sees what information is missing and who needs it. Assign to subject matter expert who knows the system. Track documentation requests like project tasks.

In the running system, experts respond faster because they see what engineer actually needs. Engineer needs deployment procedure for specific service. Current docs cover only partial process. SME documents missing steps.

Every documentation request improves workspace automatically. Engineer requested firewall rule documentation. Security team creates comprehensive firewall policy guide. Next engineer needing same information finds completed documentation without duplicate requests.

Automate with AI

AI helps write technical documentation from existing sources. Engineer provides server specs and notes. AI generates structured documentation matching your technical style maintaining accuracy.

AI search understands technical relationships automatically. Search for "production database" and find related backup procedures and security protocols. AI knows these concepts connect even though documentation doesn't explicitly link them.

Automate documentation updates and notifications in the deployed system. Server configs change - system sends update notification to documentation owner. Infrastructure team deploys new service - workflow creates documentation template.

Organizations running this application report AI drafting infrastructure documentation much faster. Suggests related docs when engineers add new content. Identifies outdated documentation based on system changes.

Why IT Team Knowledge Base improves automatically

Traditional technical documentation gets stale within months. Organizations using this system see continuous improvement.

  1. Document → Engineers create infrastructure docs in Matrix organized by systems
  2. Search → Team finds technical information through Flows workspace with AI understanding concepts
  3. Request → Engineers identify documentation gaps through Inbox with context
  4. Improve → Experts fill gaps and system gets smarter based on patterns

In the first few weeks: Initial documentation accessible with basic organizationBy month 2-3: Coverage improves after filling gaps based on search patternsOver time: Comprehensive technical coverage matching actual infrastructureLong-term: High search success rate with mature documentation continuously updated

This works because the deployed application connects everything. Most technical teams use Confluence for some docs and wiki for others. Information stays fragmented. Gaps never get identified. Updates happen randomly.

MatrixFlows builds the loop into platform. Search patterns reveal documentation gaps. Requests identify missing knowledge. Contributions improve findability. Better documentation reduces questions. Cycle continues.

Implementation timeline

Deploy IT Team Knowledge Base in 3-5 days:

Simple implementations launch in 3 days with pre-built templates. Medium complexity takes 1 week for custom taxonomy and security configuration. Complex setups complete within 10 days with full infrastructure documentation migration.

Your technical team handles everything without consultants. Start with template. Import existing docs. Structure by infrastructure. Configure security. Train team. Go live when ready. Every plan includes unlimited team access.

📚 Learn more: Matrix Technical Foundation | Flows Workspace Builder | Inbox Collaboration | AI & Automations

💡 One Foundation, Multiple Uses:Instead of separate tools for documentation, collaboration, and version control, MatrixFlows unifies everything. Build workspace in Flows, organize infrastructure in Matrix, manage requests in Inbox—all connected automatically.

🎯 Why MatrixFlows Is Different:

  • Unlimited team collaboration without per-user costs
  • Pricing scales with company size, paid plans based on company size
  • Structured templates for infrastructure documentation
  • AI search understanding technical concepts
  • System improves automatically through usage patterns

Results you can expect from IT Team Knowledge Base

Teams using the application in production see these outcomes:

Most technical teams see improved knowledge access within first week. Here's what typically improves:

For IT Engineers

  • Example Search Time Reduction: Find system configs faster - some teams report finding documentation in under 30 seconds instead of hours
  • Faster Problem Resolution: Solve infrastructure issues faster with instant access to runbooks and previous incidents
  • Better Onboarding: New engineers become productive faster - access to complete infrastructure documentation from day one

For IT Teams

  • Example Documentation Speed: Document systems faster - some teams report AI helping structure technical content much quicker
  • Preserve Expertise: Retain infrastructure knowledge when senior engineers leave - documented expertise survives team changes
  • Eliminate Duplicate Work: Stop re-solving problems already documented - search finds previous solutions instantly

For IT Leadership

  • Example Cost Impact: Some organizations reduce time wasted searching - same team maintains more infrastructure with better documentation
  • Faster Onboarding: New technical hires productive faster - comprehensive documentation enables self-service learning
  • Better Compliance: Complete audit trail of infrastructure changes - security team tracks modifications for requirements

📊 Example Scenario: One technical team reported big reduction in documentation search time with faster new engineer onboarding

⏱️ Common Outcome: IT staff save hours weekly searching for documentation - teams save 10-15 hours monthly not recreating existing solutions

💰 Example Impact: Some organizations avoid $40-80K duplicate technical work annually per team through centralized knowledge

How MatrixFlows IT Team Knowledge Base compares to Confluence, Notion, and GitHub Wiki

Here's how this deployable system compares to alternatives:

Most IT teams compare documentation platforms based on technical features. Here's how MatrixFlows differs from Confluence, Notion, and GitHub Wiki.

MatrixFlows vs Confluence

Confluence is the standard wiki for technical teams with strong Atlassian integration. However, search struggles with technical terminology. No structured documentation for infrastructure. Pages become walls of text nobody wants to update.

MatrixFlows IT Team Knowledge Base was built for structured technical documentation. Your entire IT organization contributes without per-user fees. AI search understands technical relationships. Create structured docs for servers and networks.

Choose MatrixFlows when you need entire IT organization documenting infrastructure without per-person monthly costs.

MatrixFlows vs Notion

Notion offers flexible workspace with clean interface popular with technical teams. However, built for general knowledge not technical infrastructure. No version control for critical system docs. Search doesn't understand technical concepts.

MatrixFlows IT Team Knowledge Base enables unlimited technical team collaboration without per-seat costs. Version control built-in for infrastructure changes. AI search understands technical terminology and system dependencies.

Choose MatrixFlows when you need infrastructure documentation with version control and technical search at scale.

MatrixFlows vs GitHub Wiki

GitHub Wiki comes with GitHub repos offering simple markdown-based documentation. However, GitHub Wiki has no search beyond basic text matching. No structured data for infrastructure. Each repo has separate wiki creating fragmentation.

MatrixFlows IT Team Knowledge Base provides organization-wide infrastructure documentation platform. AI-powered search across all technical documentation. Real-time collaboration without Git merge conflicts.

Choose MatrixFlows when you need searchable infrastructure knowledge spanning multiple systems and teams.

The biggest difference: Confluence focuses on wiki pages. Notion on flexible workspaces. GitHub Wiki on per-project markdown. MatrixFlows prioritizes structured infrastructure documentation with unlimited technical team collaboration.

Create your IT Team Knowledge Base today

Stop losing infrastructure knowledge in scattered wikis and tickets. IT Team Knowledge Base helps technical teams document systems and find solutions faster. Deploy structured technical documentation that preserves expertise when engineers leave.

Every plan includes:

  • Infrastructure documentation and unlimited team collaboration
  • AI-powered technical search understanding system relationships
  • Real-time coordination for IT knowledge work
  • Version control and change tracking for critical infrastructure

Paid plans based on company size when ready. No per-user fees.

🚀 Start Today: Create IT Team Knowledge Base and reduce search time

⏰ Quick Setup: Deploy complete technical documentation workspace in 3-5 days

💡 What you get: Unlimited users on every plan with unlimited IT staff includes knowledge management and AI search

Create your MatrixFlows workspace today →

‍

In this post:
Frequently asked questions

Frequently Asked Questions About IT Team Knowledge Base

Explore answers about knowledge bases for IT teams — from documenting system configurations and technical solutions, to preserving infrastructure knowledge during team changes, and what makes modern platforms different.

Our IT team's runbooks are in wikis, architecture docs are in Google Drive, and incident procedures live in people's heads. How do we get all of that into one searchable knowledge base?

IT staff resolve incidents faster when runbooks live in one place tagged by system and environment — because tribal knowledge in wikis and Slack disappears when the author leaves. An admin searching "database failover production" finds the runbook with exact steps. A network engineer searching "VPN gateway architecture" finds the current topology diagram with last-updated date.

Confluence works for IT wikis but accumulates stale pages that nobody maintains — after two years, half the runbooks reference decommissioned systems. SharePoint stores architecture documents but provides no system-level taxonomy for IT-specific search. GitHub wikis capture some runbooks but fragment knowledge across repositories with no cross-repo search capability.

Your IT team imports runbooks, architecture docs, and incident procedures into MatrixFlows tagged by system, environment, and service tier. AI search covers all IT knowledge from one search bar — runbooks, architecture decisions, vendor documentation, and postmortems. When a system changes, your team updates the runbook once and every IT staff member searching for that system finds the current procedure.

We manage dozens of systems across staging and production environments. How do we make sure IT staff always pull up the right runbook for the right system and environment?

System and environment tags on every runbook ensure procedures match the exact environment — because running a production runbook against staging creates outages that compound the original incident. When an admin searching "restart authentication service" specifies production, every result filters through production-specific procedures with the correct hostnames, thresholds, and escalation contacts.

Confluence pages can be organized by space but most IT teams don't maintain environment-level tagging consistently — production and staging runbooks live in the same space with naming conventions as the only differentiator. SharePoint document libraries store runbooks as files with no environment metadata. GitHub repos separate by project but not by environment within the same system's documentation.

In MatrixFlows, IT staff search against system and environment tags — production, staging, development, disaster recovery. AI search filters every result through these tags before matching the query. When a system upgrades and runbooks change for one environment, your team updates the tagged procedure and only that environment's search results reflect the change — other environments keep their existing procedures until explicitly updated.

Can one IT team knowledge base handle runbooks, incident postmortems, architecture decision records, and vendor documentation — each with different structures?

Each IT content type works better with its own structure — because a runbook needs sequential steps with rollback while a postmortem needs root-cause analysis with action items. IT staff find the right resource faster when search results match expectations: a runbook shows its system, environment, and last-tested date, a postmortem shows its severity and date, an architecture decision shows its status and rationale.

Confluence treats every IT document as a page — a runbook looks identical to a meeting note looks identical to a postmortem. GitHub wikis handle code-adjacent documentation but lack structured content types for operational knowledge. SharePoint document libraries store files but provide no structural distinction between a vendor contract and an architecture diagram in search results.

The pre-built template includes content types configured for IT teams — runbooks with system tags and rollback procedures, postmortems with severity and action items, architecture decisions with status and rationale, and vendor docs with contract dates and support contacts. AI search in MatrixFlows surfaces the right content type for each query. IT staff find the runbook during an incident and the postmortem during the review — each structured for its job.

Our IT department has infrastructure, security, and helpdesk teams who each manage different systems and procedures. Can one knowledge base serve all three without information overload?

Team-function tags show each IT sub-team only documentation relevant to their systems — because helpdesk staff seeing failover runbooks creates confusion and infrastructure engineers wading through password guides wastes time. Infrastructure sees server and network procedures. Security sees compliance frameworks and vulnerability response playbooks. Helpdesk sees user support procedures and escalation paths. Shared IT policies appear for all three functions.

Confluence spaces can separate IT functions, but shared documentation like security policies or vendor contacts requires duplication across spaces that drifts. SharePoint sites per IT function create the same duplication problem. GitHub repos organize by project and codebase, not by IT operational function — infrastructure and security docs for the same system live in different repos with no unified search.

MatrixFlows applies function and system tags so your IT department maintains one knowledge base while each team sees relevant content. Infrastructure sees failover and scaling runbooks. Security sees threat response and audit procedures. Helpdesk sees user support guides and escalation workflows. Cross-function content like vendor SLAs appears for all teams. One update, every function's view stays current.

How does an IT team knowledge base help us respond to incidents faster, and how do we keep runbooks current as our infrastructure changes?

Incident response speeds up when the on-call engineer finds the right runbook in seconds — and analytics surface which procedures are stale since the last infrastructure change. Each runbook gap your team closes prevents a future incident from becoming a scramble, and each postmortem documented prevents the same root cause from recurring.

Confluence provides no analytics connecting IT search behavior to incident response outcomes — you track MTTR in your monitoring tool but can't see whether knowledge gaps extended resolution time. GitHub wikis have no usage analytics at all. SharePoint shows document downloads but cannot identify which systems lack runbook coverage or which procedures are stale.

IT team analytics in MatrixFlows surface which system searches return no results, which runbooks haven't been updated since the last infrastructure change, and which incident types lack postmortems. Your team fills gaps based on the systems and scenarios generating the most search failures during incidents. When your infrastructure changes, stale runbook alerts surface before the next on-call rotation discovers them during a real incident.

What does an IT team knowledge base cost when every IT staff member — plus on-call contractors — needs access?

MatrixFlows uses company-wide pricing based on company size, not per-user fees. Every IT team member — full-time staff, on-call contractors, and managed service partners — gets full access to search, contribute, and use AI answers at no additional per-user cost. Paid plans scale with your organization.

Confluence charges $6-$11 per user monthly. GitHub Enterprise starts at $21 per user monthly. Per-seat pricing forces IT leaders to decide whether contractors and part-time on-call staff get knowledge base access — so the people most likely to need runbooks during off-hours incidents are the ones without access to find them.

We have runbooks in Confluence and architecture docs in Google Drive. How fast can we get an IT team knowledge base that staff can search during incidents?

Import your most critical system runbooks first — the ones your on-call team needs during a 2 AM incident. The pre-built IT team template tags each runbook by system and environment automatically, so production and staging procedures stay separated from day one. Function-based visibility keeps infrastructure, security, and helpdesk content organized without manual folder structures. Add postmortems and architecture docs as the team builds the habit. No developers required.

© 2026 MatrixFlows