AFFiNE for IT Services

IT documentation for client projects.

IT documentation explains how a system is built, configured, operated and handed over. Use AFFiNE to connect architecture diagrams with configuration notes, decisions and support procedures. A useful handover identifies the current owner, source references, unresolved issues and the next action for the receiving team.

30-minute Google Meet Workflow, deployment and team fit

Illustrative workspace: Solution brief — portal migration

Workspace view
Solution brief — portal migrationImplementation workspaceTechnical handoverSupport knowledge noteMeeting notes

Page · solution team · synthetic example

Solution brief — portal migration

Scope
Replace the document entry point
Decision
Retain existing identity provider
Handover
Operations questions

Open design question: confirm retention needs with the client.

Same project · Edgeless canvas
Solution brief — portal migration — illustrative canvasNodes: Users, New portal, Doc store, Identity provider, Ops handover. Connections: Users to New portal; New portal to Doc store; New portal to Identity provider (sign-in · retained); Identity provider to Ops handover (questions).
Users
New portal
Doc store
Identity provider
Ops handover
sign-in · retained
questions
  • The new entry point in scope, between users and the existing document store.
  • The decision to keep the current identity provider, drawn on the sign-in path.
  • Questions for the operations team are linked from the diagram to the handover.

Edgeless

Implementation workspace

Draw the system components and their connections. Explain the design choices, assumptions and unresolved questions in a solution brief beside the diagram.

Assumption
Existing identity service
Option
Shared document entry point
Question
Confirm retention needs
Same project · Edgeless canvas
Implementation workspace — illustrative canvasNodes: Client need, System map, Options, Decision, Retention needs?. Connections: Client need to System map; System map to Options; Options to Decision (chosen); Retention needs? to Decision (blocks).
Client need
System map
Options
Decision
Retention needs?
chosen
blocks

Page + table

Technical handover

Keep project scope, configuration notes and a delivery checklist together. Use a table for owners and open items, updated by the project team.

ItemOwnerStatus
Document migration pilotDelivery teamReview assumptions
Retention needsSolution architectOpen question
Operations proceduresConsultantDrafting

Manually maintained table · no ticket automation

Same project · Edgeless canvas
Technical handover — illustrative canvasNodes: Users, New portal, Doc store, Identity provider, Ops handover. Connections: Users to New portal; New portal to Doc store; New portal to Identity provider (sign-in · retained); Identity provider to Ops handover (questions).
Users
New portal
Doc store
Identity provider
Ops handover
sign-in · retained
questions
  • The new entry point in scope, between users and the existing document store.
  • The decision to keep the current identity provider, drawn on the sign-in path.
  • Questions for the operations team are linked from the diagram to the handover.

Page

Support knowledge note

Link the architecture overview, operating procedures and unresolved issues from one handover page. Check the sharing or Markdown export path before delivery.

System context
Architecture notes
Operations
Known procedures
Open items
Questions for the next team

Markdown export available · test the sharing method first

Embedded Edgeless frame

Markdown export — test the result before delivery

Same project · Edgeless canvas
Support knowledge note — illustrative canvasNodes: Users, New portal, Doc store, Identity provider, Ops handover. Connections: Users to New portal; New portal to Doc store; New portal to Identity provider (sign-in · retained); Identity provider to Ops handover (questions).
Users
New portal
Doc store
Identity provider
Ops handover
sign-in · retained
questions
  • The new entry point in scope, between users and the existing document store.
  • The decision to keep the current identity provider, drawn on the sign-in path.
  • Questions for the operations team are linked from the diagram to the handover.

Page

Meeting notes

Turn recurring support questions into reusable pages. Include the configuration, the reason it was chosen and a link to the implementation notes.

Why this configuration?

Design rationale, written once and linked from support notes.

Related
Implementation note
Same project · Edgeless canvas
Meeting notes — illustrative canvasNodes: Users, New portal, Doc store, Identity provider, Ops handover. Connections: Users to New portal; New portal to Doc store; New portal to Identity provider (sign-in · retained); Identity provider to Ops handover (questions).
Users
New portal
Doc store
Identity provider
Ops handover
sign-in · retained
questions
  • The new entry point in scope, between users and the existing document store.
  • The decision to keep the current identity provider, drawn on the sign-in path.
  • Questions for the operations team are linked from the diagram to the handover.
Illustrative workspace — synthetic content, not a product screenshot or a customer case study. In Edgeless: drag objects, use Hand to pan, or Ctrl/⌘ + scroll to zoom. Drawing tools are visual references.
  • Explain architecture choices beside the diagram

    Shown in workflow 01

  • Keep implementation scope and owners visible

    Shown in workflow 02

  • Reuse answers to recurring support questions

    Shown in workflow 04

From task to workspace

IT documentation from architecture to support.

Build a solution brief, track implementation notes, prepare a handover and reuse support answers.

Task-to-feature map for the four examples on this page
TaskDocsEdgelessTablesTeamExportOutput
01 · Solution architectWrite software architecture documentationDocsEdgelessSolution brief
02 · Delivery leadOrganize implementation documentationDocsTablesTeamImplementation workspace
03 · ConsultantPrepare a technical handoverDocsEdgelessExportTechnical handover
04 · Support teamBuild an IT knowledge baseDocsTeamSupport knowledge note

01Solution architect

Write software architecture documentation

Draw the system components and their connections. Explain the design choices, assumptions and unresolved questions in a solution brief beside the diagram.

Task
Explain a proposed architecture to the client
In AFFiNE
System relationships drawn in Edgeless; each choice explained in the page
Output
Solution brief

Features used

EdgelessSynthetic example

Solution brief

Solution brief — illustrative canvasNodes: Client need, System map, Options, Decision, Retention needs?. Connections: Client need to System map; System map to Options; Options to Decision (chosen); Retention needs? to Decision (blocks).
Client need
System map
Options
Decision
Retention needs?
chosenblocks
Assumption
Existing identity service
Option
Shared document entry point
Question
Confirm retention needs
Illustrative layout with synthetic content — not a product screenshot.

02Delivery lead

Organize implementation documentation

Keep project scope, configuration notes and a delivery checklist together. Use a table for owners and open items, updated by the project team.

Task
Start a delivery with the current discussion in one place
In AFFiNE
Scope page with a simple table maintained by the team
Output
Implementation workspace

Features used

Page + tableSynthetic example

Implementation workspace

ItemOwnerStatus
Document migration pilotDelivery teamReview assumptions
Retention needsSolution architectOpen question
Operations proceduresConsultantDrafting

Manually maintained table · no ticket automation

Illustrative layout with synthetic content — not a product screenshot.

03Consultant

Prepare a technical handover

Link the architecture overview, operating procedures and unresolved issues from one handover page. Check the sharing or Markdown export path before delivery.

Task
Leave the client team a handover they can navigate
In AFFiNE
Handover page linking architecture notes and the canvas; Markdown export tested before delivery
Output
Technical handover

Features used

PageSynthetic example

Technical handover

System context

Architecture notes

Operations

Known procedures

Open items

Questions for the next team

Embedded Edgeless frame

Markdown exporttest the result before delivery

Markdown export available · test the sharing method first

Illustrative layout with synthetic content — not a product screenshot.

04Support team

Build an IT knowledge base

Turn recurring support questions into reusable pages. Include the configuration, the reason it was chosen and a link to the implementation notes.

Task
Answer a recurring question once, with its reasoning
In AFFiNE
Reusable page in the shared workspace, linked to the implementation note
Output
Support knowledge note

Features used

PageSynthetic example

Support knowledge note

Why this configuration?

Design rationale, written once and linked from support notes.

RelatedImplementation note

Illustrative layout with synthetic content — not a product screenshot.

From example to evaluation

Discuss your client documentation workflow.

Talk through architecture notes, project handovers and access requirements for your team.

Book a demo

Choose a time with the AFFiNE team.

One connected workspace

Write in a page. Switch the same doc to a canvas.

The examples above use the same building blocks.

  • Illustrative example

    Docs

    Readable pages with references, images and rich blocks.

    Explore Docs
  • Illustrative example

    Edgeless whiteboard

    A canvas to show how ideas and systems relate.

    Explore Edgeless
  • Illustrative example

    Tables and team workspace

    Track what is open and edit together in shared spaces.

    Explore Teamhub

Illustrative examples of docs, whiteboards and tables — not product screenshots or industry case studies.

Deployment and evaluation

Choose how the workspace runs.

Evaluate the workload, infrastructure and AI configuration together, with the people who will operate the workspace.

Illustration of a hosted cloud workspace

Hosted workspace

Try one workflow with permitted sample material before you scale it.

  • AFFiNE web app
  • One team workspace
  • No servers to run
Discuss cloud deployment
Self-host AFFiNE

Prerequisites

1 / Docker

Install Docker and Docker Compose on your machine.

2 / Download the latest Compose file

Download compose.yml from the AFFiNE repository.

3 / Prepare the environment file

Review the environment variables for your deployment.

Self-hosted

For self-hosted AFFiNE, Docker Compose is the documented deployment path. Workspace data and uploads use the infrastructure and storage you configure.

  • Docker Compose
  • PostgreSQL
  • File or S3 storage
  • OIDC sign-in
  • Sign in through your identity providerSelf-hosted AFFiNE supports OIDC. Review workspace roles and document access against your own requirements.
  • AI is optionalSelf-hosted AI needs a configured provider and can be turned off. Bring-your-own-key is marked experimental.
  • Licensing for restricted networksAn installable license activates without calling AFFiNE’s license servers. That alone does not make every feature work offline.
  • Backup and restoreThe process is documented, including a test restore. Run it in your own environment.
  1. Will client material share a workspace with internal knowledge?
  2. How will each handover be shared or exported?
  3. Which identity provider should the pilot use?

This page makes no claim about SAML, SCIM, industry certifications, or approval for any specific workload.

Product references: AFFiNE Enterprise and documentation in English for Docker Compose, OIDC sign-in and AI configuration.

Continue exploring · General template

Existing SOP template

A general procedure template for writing down a repeatable operations task.

Before you start

Questions from your team.

How can service teams use AFFiNE as IT documentation software?

Use docs for configuration notes and operating procedures, whiteboards for architecture diagrams, and tables for owners and open questions. These examples cover documentation; asset discovery, password vaults, RMM and ticket automation remain in specialist tools.

What belongs in software architecture documentation?

Record the system purpose, users, components, interfaces and deployment context, then explain design decisions and unresolved questions. Label diagram elements and connections so another team can read them without the original author. In AFFiNE, keep the diagram beside its assumptions, source references and decision notes.

Diagramming reference (English): C4 model for software architecture.

Can we separate information for different clients?

Evaluate workspace membership, document access and sharing settings against your requirements before using client material. The example does not establish tenant isolation.

Can we evaluate self-hosting?

Yes. Docker Compose is the documented self-hosting path, with sign-in through your identity provider via OIDC. Review the Enterprise documentation with your infrastructure team, then test one representative workflow before a wider rollout.

Is AI required for this workspace?

No. These workflows use pages, canvases and tables without requiring AI. In self-hosted AFFiNE, AI needs a configured provider and can be turned off. Review the provider and data flows before enabling it.

How should our team start?

Choose one current documentation task and a small set of permitted sample material. Evaluate whether the team can find, understand and hand over the work before expanding.

A conversation about your team

Evaluate AFFiNE for client delivery.

Talk through architecture notes, project handovers and access requirements for your team.

30-minute Google Meet · Choose an available time

Prefer email? Contact sales