Knowledge
The page where a project teaches Subscriby Copilot what only you know: questions with their answers and guides you upload, cut into passages the Copilot reads whole; who may be answered from each entry, members or your team alone; the preview that shows the passages the Copilot would be handed for any question; what reads it today, the limits, and the permissions.
Knowledge is what a project teaches Subscriby Copilot beyond what Subscriby already knows about it. Subscriby knows your plans, your members and their payments; it does not know that Thursday classes start at seven, that a pause lasts three months, or where the studio is. You write those down once, as a question with its answer or as a guide you upload, and the Copilot answers from them: today when it drafts your reply in the Support Inbox and when it answers a member itself, in the inbox, your bot and the chat on your portal page; next in the panel beside every page and in your platform bot.
Knowledge is on every plan, Free included, and adding to it costs nothing. The last entry of your project's menu opens it.
What you can teach it
A question with its answer
Worded the way a member would ask it, answered the way you would answer: "When does my membership renew?", "Memberships renew on the first day of every month." The search matches on the question's words too, so word it as people do.
A guide you upload
A plain-text or Markdown file: your member guide, your house rules, your timetable. The text is read out of the file and cut into passages; the file itself is kept so you can read back what you uploaded.
Who may be answered from it
Every entry serves you and your team. Only an entry marked Members & Team serves your members, in the inbox and your bot; Team Only keeps it to the people who run the project.
A preview before anyone asks
Type a question into What the Copilot Knows and read the passages the Copilot would be handed, each with the entry it came from. It calls no model and costs nothing, so you can check an entry the moment you save it.
Adding an entry
Open Knowledge. In your project's menu, below Support Inbox, open Knowledge and press Add to Knowledge. The badge on the menu entry counts the entries the project holds.
Pick the kind. Question & Answer gives you a question and an answer box; Document gives you a name and a place to drop a file. The kind cannot change once the entry exists, so a guide that should be a question is a new entry.
Write or upload. An answer is plain words, as you would write them to a member, facts only: the Copilot quotes from here and never invents a date or an amount. A file is plain text or Markdown, up to 2 MB; the name you give it is shown on the page and written at the head of every passage, so a passage read on its own still says where it came from.
Choose who may be answered from it. Members & Team or Team Only, on two cards that say what each means. New entries start as Members & Team, because most of what a creator writes down is written for members; a note for your team alone takes one click.
Save. The entry is cut into passages and in the index the moment it is saved; the row shows Ready with how many passages it became. Edit it and the passages are cut again wherever the words changed; change only who may be answered from it and the passages simply follow.
How an entry is read
Cut into passages
The text is cut at paragraph breaks first, at the end of a sentence when a paragraph is too long, and at a space after that, into passages of about 1,200 characters, each headed by the title. Short paragraphs are packed together, so a list of one-line answers is one passage, not twenty.
Found by the question
When the Copilot needs your Knowledge it searches the passages with the member's message and is handed the five that match best, each with its entry's title, as data to answer from. Your team sees every entry's passages; a member's answer is searched among the entries marked for members and no other.
The What the Copilot Knows card at the top of the page is that search, open to you: type a question the way a member would and read the passages the Copilot would be handed, each with the entry it came from and who may be answered from it. It calls no model and costs nothing, so it is the way to check an entry before a member ever asks. A question that finds nothing says so, and the fix is an entry that answers it.
Where it is read
| Surface | What it reads | When |
|---|---|---|
| The suggested reply in the Support Inbox | Every entry, Team Only included, matching the member's last message | Today |
| Answers for members, in the inbox and your bot | Entries marked Members & Team only | Today |
| The Dashboard Panel and your bot | Every entry, as a tool the Copilot can call | Next |
| The chat on your portal page, with Let Subscriby Copilot answer members on your portal on | Entries marked Members & Team only | Today |
The suggested reply may read your team's notes because you read the draft before anything goes out; an answer a member receives without you is written from the entries you marked for them and nothing else.
Team Only or Members & Team
The default. The entry serves you, your team and your members. When Let Subscriby Copilot answer members is on in the inbox's settings, a member whose question the entry answers hears back at once, marked as automated, with the entries the answer drew on kept on the thread for you to read. Use it for the questions members ask you twice a week: the timetable, the house rules, how to pause, where the studio is, what the levels mean.
The member boundary
A member is answered by a separate agent with no tools at all. It is handed the member's own standing, your saved replies, the portal address and the passages you marked for members, and nothing else: no other member, no revenue, no settings, no Team Only entry. The filter is applied inside the search, so there is no prompt a member's message could talk its way around.
Limits
| What | Limit |
|---|---|
| Entries per project | 200 |
| File size | 2 MB |
| File types | .txt, .md, .markdown |
| Title | 160 characters |
| Answer | 50,000 characters |
| Passages handed to the Copilot per question | 5 |
In your team
Knowledge has its own five permissions, project-knowledge:view-any, view, create, update
and delete, so a role can read what the project taught the Copilot without being able to change
it. The Ability Reference lists them beside
the others. A team member needs none of them for the Copilot to read Knowledge on their behalf in
the inbox; they need the support permission on the thread, as for any reply.
Automating it
Everything the page does is open to integrations, so a help centre, a wiki or a script can keep the Copilot taught without anyone pasting:
- REST API — list, read, add, change and remove entries under
/v1/projects/{project}/knowledge; a document arrives as text. Behind the fiveproject-knowledge:*abilities. - MCP tools — let an agent read what the project taught and teach it more, with the same five operations.
- Webhooks —
knowledge.created,knowledge.updatedandknowledge.deletedsay what changed, never carrying the text. - Zapier and n8n — the same operations and events as prebuilt steps and triggers.
A PDF is not read on any surface yet; the API takes the text, the dashboard takes the text or a
.txt, .md or .markdown file.
Frequently asked
Related
- Support Inbox — where the suggested reply and the member answers live
- Copilot in Your Inbox — the draft, what it is written from, the member switch
- Subscriby Copilot — the operator, surface by surface
- Permissions & Safety — who may use the Copilot and what the model is shown
- Ability Reference — every permission, Knowledge's five included
- Knowledge API — the five routes, and the MCP tools and events beside them
How is this guide?
Last updated on
Support Inbox
Members who write to your project bot land in one inbox; answer from the dashboard or straight from the platform's chat.
Managing Subscriptions
Every subscription in your project with its status and payment history, filtered any way you need, with cancellation for active or trialing ones.