ANTE User ManualProject Knowledgebase
The Knowledgebase is the main document of a client project. It is one living page that always shows the latest plan the client and your team have agreed and finalized: the people, the scope, every setting and business rule, the company policies and the key dates. It never holds history. When someone asks "what do we do about overtime?", this is the page that answers it.
What It Is
Open a project and click the Knowledgebase tab, which sits right after Overview. The first time anyone opens it, the page is created for you from a ready-made template with every section in place. Each project has exactly one Knowledgebase.
Only agreed and final information belongs here, written as the current agreement. How it got there (what changed, who agreed, when) is kept in the version history and the Activity Log instead. A question the client still has to answer goes in Client Pending, working notes and meeting minutes go in a Note, and a fact only your team should see goes in an Internal note inside the right section (see Internal Notes).
The Sections
The sections always appear in this order and cannot be renamed, removed or reordered. The Glossary is the only optional one.
| Section | What it holds | Columns |
|---|---|---|
| Project at a glance | Client, modules used, go-live date and other key facts | Item, Details |
| People and roles | Everyone involved on both sides and what each is responsible for | Name, Side, Role, Responsible for, Contact |
| Scope | What is covered and what is not | Two bulleted lists: In scope and Out of scope |
| Agreed configuration and business rules | Every signed-off setting, with one sub-heading and table per module (Payroll, Timekeeping, Leave and so on) | Setting, Agreed value, Basis |
| Company policies | Client policies the system must follow, in plain words | Policy, What it means in ANTE, Effective, Source |
| Integrations and data migration | Systems connected and data brought over from the old system | Item, Agreed approach, Owner |
| Timeline and milestones | The agreed key dates | Milestone, Date, Owner, Notes |
| Glossary | Client terms and abbreviations | Term, Meaning |
For example, a row in the Timekeeping table of the configuration section reads: Setting "Overtime rounding", Agreed value "Rounded down to the nearest 15 minutes", Basis "Company policy handbook, section 4.2". Write each fact in one row only. When an agreement changes, overwrite that row with the new agreed value; do not keep the old value or a remark such as "previously 30 minutes" in the page. There is no decision log and no date-agreed column: dates stay only where they are part of the plan, such as a policy's Effective date or a milestone date. See Changing an Agreement.
Changing an Agreement
The Knowledgebase is always the latest agreed plan, so a change replaces the old value instead of adding to it. Edit the row or section so it states the new agreement, for example "Overtime is rounded down to the nearest 15 minutes". The page holds no history: no "previously", no "changed from", no version numbers and no update dates.
The story of the change is kept elsewhere. Every decision belongs in the project's Activity Log, where the Decisions filter lists each one with who agreed, when and where. Past versions of this page are in History.
Editing
The page uses the same block editor as Notes. Type / for the block menu. Changes save automatically about a second after you stop typing; the header shows Saving, Saved or Save failed.
Tables
Click inside any table and a small toolbar appears above it. Use it to add a row above or below, add a column to the left or right, delete the current row or column, switch the header row on or off, or delete the whole table. Keep the column headings of the knowledgebase tables as they are, because the format depends on them.
Callouts and Their Tones
A callout highlights a single point. Open the callout's menu to choose its tone.
| Tone | Use it for |
|---|---|
| Default | A plain highlighted note with no particular meaning |
| Information | Context that helps read the table above it |
| Agreed or done | A confirmed outcome or agreement, such as a parallel run that matched |
| Warning | A condition the client must keep to, such as a cutoff date |
| Critical | A rule that gives a wrong result if it is broken |
| Internal (hidden from client) | For your team only; never shown to the client |
Internal Notes
Choose Internal note from the block menu, or switch a callout's tone to Internal (hidden from client). The block shows a Not shown to client label. When the client opens the share link, the system removes every Internal note before the page is sent, so it never reaches their browser. Place an Internal note inside the section it concerns.
Besides Internal note, the block menu has Info callout, Warning callout and Decision. Decision inserts an Agreed or done callout that starts with "Decision: ", ready for you to type the agreement. In the Knowledgebase itself, write only the current agreement and record the decision in the Activity Log (see Changing an Agreement).
The Outline
A sticky On this page list on the left shows every section and module sub-heading. Click an entry to jump to it. On narrow windows (900 pixels or less) the outline collapses to save room.
History and Restore
Every save keeps a version. A normal edit by the same person within ten minutes extends the latest version, so a long editing session is one entry rather than dozens. Click History in the header (or the clock icon, whose tooltip and dialog are titled Version history) to see the versions, newest first, with who changed it, when, where the change came from (web, Claude or a restore) and a short summary.
- Click History.
- Click a version to preview it. The preview is read-only.
- Click Name this version to give it a short summary, for example "Before the November payroll changes".
- Click Restore this version and confirm in the "Restore version N?" dialog to bring that version back. Restoring does not delete anything: it saves a new version holding the old content, so you can undo a restore from History too.
Each new version also adds an entry to the project's Activity Log, naming the sections that changed (the Knowledgebase updates filter). A decision that changes the plan adds its own entry, dated the day it was agreed, to the Decisions filter.
Export and Print
Use the Export as markdown icon button in the header (hover for its tooltip) to download the whole page as a text file, and Print to print it or save it as a PDF. Both include every section, including Internal notes, so share the output carefully.
Showing It to the Client
The header shows a chip: Visible on client link or Hidden from client. Click it to open the Share dialog, where the Knowledgebase switch controls whether the client sees a read-only Knowledgebase tab on the share link. The switch is off by default. The client page shows the same outline, but never the Internal notes.
Only Internal notes are hidden from the client. Write every other line knowing the client may read it.
Who Can Edit
Project members with the Creator or Moderator role can edit, and so can company administrators with full access. Other members of the project can read the page but not change it. People who are not on the project cannot open it. Sharing, pinning and deleting are not available, because access follows the project.
Working with Claude
Claude, connected through the Ante connector, can read and update the Knowledgebase in this same fixed format. It records agreed settings one row at a time, overwriting the old value, and records each decision that changes the plan in the Activity Log in the same step. It refuses wording that describes history (such as "previously" or "changed from"). It writes a change summary for every change, which appears in History and the Activity Log. It cannot restore versions; that is done here in the app.
How It Connects
Set up first
- Creating a Project — the Knowledgebase belongs to a project and is created the first time someone opens its tab.
Gets its data from
- Notes — meeting minutes and working notes are written there; the agreed outcome is copied into the Knowledgebase.
- Project Details — Client Pending answers and completed tasks are the source of what gets recorded.
Feeds into
- Sharing a Project — the Knowledgebase switch decides whether the client sees it on the share link.
- Activity Log — every new version adds an entry, and every decision is recorded there with who agreed and when.