Product Guide · Knowledge and Strategy
Knowledge base
The knowledge base is the material Scripe writes from: what your company does, who your content is for, what each profile stands for, and the documents, websites and meeting notes behind them. What is in it shows up in ideas and drafts as facts you can recognise, not generic claims.
It is for admins who set up a workspace, solo creators filling in their own profile, and agencies setting up each client. Team members add material for the profiles they work on. Agency clients do not see the knowledge base.
Open it from Settings → Content & branding → Knowledge.
What is in it
Essential items
Three items sit at the top of every knowledge base. They always stay and cannot be removed:
- Company: what your company does, for whom, and why it wins. One for the whole workspace.
- Target Audience: who your content is for. One for the whole workspace.
- Positioning, per personal profile: the questions behind that profile's content. Scripe prefills the answers from the profile's LinkedIn history the first time you open it; adjust anything.
A profile can follow the workspace's target audience or have its own: in the profile's Positioning, turn on Define its own target audience. Leave it off and the profile picks up every change to the workspace audience.
How these items relate to topics, tone of voice and branding is explained in Strategy.
Profile folders
Every personal profile that finished its setup, and every Company Page, has its own folder. It holds what belongs to that profile alone: its published posts (Post history), anything uploaded for it, and anything shared with that profile only. Material shared with the whole workspace, or with several profiles, stays in the main list.
The profile's settings show the same folder under Knowledge, read-only; each row opens in the knowledge base.
Folders and documents
Add material with New content:
| Source | What Scripe reads |
|---|---|
| Text note | Text you type or paste, at least 100 characters |
| From any file | PDF, PPTX, DOCX, TXT, Markdown, audio and video, up to 10 files at once and 2 GB per file. Images and multi-column text in PDFs are not read. |
| From any website | A page and the sub-pages you select. Scripe checks it again every 7 days. |
| From Notion | The pages you select. Scripe checks them again every 7 days. |
| From YouTube | What is said in the video, transcribed |
| GitHub repository, Google Drive, Granola | Kept in sync; see Synced sources |
Create folders and subfolders to keep material organised. A folder's items take the folder's visibility.
Who sees what
Every item has a visibility: the whole workspace, or chosen profiles.
- Admins can share an item with the whole workspace or with chosen profiles.
- Members share with the profiles they work on.
- A synced source's folder keeps the visibility it was connected with.
- Essential items are visible to every profile.
A profile's writing reads what is shared with the whole workspace, what is shared with that profile, and what belongs to it. It never reads another profile's private material.
What Scripe does with it
- Ideas: For You and the ideas Ask Scripe suggests ground themselves in your knowledge base, one search per idea. An idea can cite a document; hovering the citation shows the passage and opens the document.
- Drafts and hooks: when Scripe writes a post or hooks, it searches the profile's knowledge base for what the post is about.
- Ask Scripe: the chat knows the folders you can see. It can list documents in a folder, read a whole document, and search by meaning, also in a colleague's profile you work on. Ask it "what is in my knowledge base from Granola?" and it lists the folder.
A profile's own LinkedIn posts reach its writing as writing samples, so the post history is left out of the searches behind drafts and ideas. Ask Scripe's knowledge search includes it.
Removing posts from the post history
A profile's Post history folder holds its published LinkedIn posts. To stop Scripe using a post, for example one written for a former employer:
Open the profile's Post history folder
It is inside the profile's folder.
Select the posts
Select one or more posts.
Press Remove from knowledge base
Confirm. The post stays published on LinkedIn and stays in your post history.
Scripe then stops using the post everywhere it learns from the profile's posts: as knowledge, as a writing sample and as an example of past results. Restore it from the folder's synced status under Removed posts. A post you had picked as a writing sample may have to be picked again after restoring; one you had switched off stays off. See Synced sources.
Limits and plans
- GitHub, Google Drive and Granola need Solo, Advanced or Business. See Plans.
- Deleting a folder deletes everything in it and cannot be undone; you confirm by typing DELETE.
- Synced items can only be changed at their source.
Edge cases
- A workspace with one profile: sharing with "every profile" is the same as the whole workspace, so that profile's folder holds only what belongs to the profile itself.
- Light profiles have no profile folder.
- A Company Page has a folder like a personal profile, but no Positioning item.