Documentation

Portal readiness, honestly labelled

There is no live customer portal today — this page is the map of what documentation exists, what's planned, and what will require a login once there are customer accounts to log into. Nothing below is presented as available unless it actually is.

✦What's available now

Real, working pages you can read today

The Peaders Method

Available. Our full delivery and governance process.

The Peaders Nexus

Available. The lifecycle and orchestration model.

Trust Center

Available. Security, data handling and evidence status.

Glossary

Available. Plain-English terms as we use them.
01Documentation map

What a customer portal will cover, once it exists.

Planned capability. This is the intended structure, not a live product. Each section below will only go live once it's real, tested, and has something behind it.

Getting started

Onboarding steps for a new engagement — account setup, first integration, first agent live.

Governance setup

Configuring your decision tiers and approval routing before any agent goes live.

Use-case registry

A record of every agent deployed for you, what it's scoped to do, and its current status.

Agent role design

How each agent's authority and tools are defined and reviewed.

Integration guides

Connecting your CRM, inbox, databases and APIs with scoped, revocable access.

Evaluation & assurance

How we test agents before release and what evidence you receive.

Admin

User access, tenant separation, and account-level controls.

Support & incidents

How to reach us, our incident-response route, and status communication.

Release notes

What changed, when, for the agents running in your account.

02 — Portal readiness controls

What has to be true before a portal ships.

Planned capability. These are the conditions we hold ourselves to before any customer-facing portal goes live — not features that exist today.

  • Identity & tenant separation — each customer's data and agents are isolated from every other customer's.
  • Evidence retention — audit logs kept for a defined, disclosed period.
  • Human approval visibility — you can see what's pending your sign-off, not just what already ran.
  • Support & release visibility — a real incident route and real release notes, not placeholders.
Planned documentation and portal structure
DOCS

Need something from this list today?

Tell us what you need and we'll get it to you directly — the honest answer, not a placeholder page.

Talk to us →