Skip to content
Knowledge management

Account knowledge that stays true

Process docs, client context, and technical detail live beside the work that changes them, so the wiki stops rotting the week after it is written.

Join the waitlist
Northwind StudioOS3
Knowledge
Internal
Brand & positioning
Alder Bay
Harbor & Co
Meridian Health
Weekly notes
Care portal rebuild
Proposal
Discovery notes
Portal spec
Key features
Scheduling
Access requests
Decision log
Go-live checklist
Integrations
Kestrel Lending
Meridian Health / Care portal rebuild /Portal specExport PDF

Access requests

How a care team member requests portal access, how Meridian reviews it, and who gets notified when it is granted.

WalkthroughOpen in player
4 min 43 sec · 1.2×
A. Reyes

In one sentence

A care team lead requests access in the portal, Meridian's admin reviews and approves it, and only then does the account go live.

  • Spaces per client and team

    Client context, internal process, and technical docs organized the way the agency actually works.

  • Linked to live records

    Docs reference real projects, contracts, and tasks, so a rename or a change in scope propagates.

  • Freshness tracking

    Every page carries a confidence state. Stale pages surface instead of quietly misleading someone.

Capture

Knowledge written once, found by everyone

Search runs across documents, tasks, threads, and files at the same time. New hires stop asking the same five questions in their first week.

sso rollout14 results
AllDocsTasksThreadsFiles
DocSSO rollout runbookMeridian HealthIdentity provider setup, staged cutover, and the rollback path if login fails for a tenant.
TaskAdd SSO to release 1Member PortalScope change requested by legal. Linked to the client thread it came from.
ThreadRE: Portal launch dateEmail · 1dClient asked whether SSO lands in the first release or the follow-up.
Fileidp-mapping.csvAug 12Attribute mapping shared by the client IT team during the migration kickoff.

Maintenance

Pages that update themselves

When a project ships a change the doc describes, the knowledge agent drafts the revision and routes it for approval. Ownership stays human; the drudgery does not.

Knowledge baseSSO rollout runbookReview needed
Knowledge agent drafted a revision after Legacy Core Migration shipped
Step 3. Provision users manually in the admin console before cutover.
Step 3. Users sync from the identity provider on first login. Manual provisioning is only needed for service accounts.
Approve revisionEditv7 → v8
Last verified Aug 12 by A. Reyes

Knowledge agent

Documentation debt, paid down continuously

It reads the work happening around each page and proposes the edit while the context is fresh.

Meet the agents →
  • Updated the staging URL in Northwind onboarding.
  • 3 pages marked stale after the Q3 process change.
  • Drafted a runbook from last week's incident thread.

Stop re-explaining the account

Join the waitlist and we will migrate your existing wiki as part of onboarding.

Join the waitlist