Knowledge
This page covers two tabs of a Force's workspace: Shared Knowledge, which is what everyone on the team can read and has learned, and Resources, which are the connected systems the team can use. Both are also steps 3 and 4 of the setup wizard.
Shared Knowledge
Open a Force and choose Shared Knowledge. Having no knowledge yet is fine.
Knowledge bases
Admins see Knowledge bases, with a count of how many are connected.
Connect an existing knowledge base
Click Connect existing. In the Connect knowledge bases drawer, search and pick one or more. Each appears as a card tagged Public, Project or Private. A knowledge base you connect is given to all current members at once, and new hires get it by default.
Or upload files
Click Upload files, choose who can use it (Public, Private or Project), name it ("e.g. AP runbooks"), and drop files in. See Step 3 for the full steps. The new knowledge base connects automatically.
Remove one (optional)
Click the X on a card. It "Stops new hires getting it; current members keep it."
Empty: "No knowledge bases yet." Errors read "Could not connect that knowledge base." or "Could not update the connected knowledge bases."
What the team knows
This section is the team's shared memory. "This is one shared memory, held by the team." What the team works out goes into its own memory space, and every member recalls it. It has four parts.
| Section | What it shows |
|---|---|
| What they can read (granted by you) | Knowledge bases with document counts and who has them, tools (Reads only or Reads and writes), and systems (read only, read and change, or draft for approval). Empty: "Nothing granted yet." Warnings point out knowledge bases that are missing or unreadable |
| What you told them (coaching, in your words) | Copies of the instructions you gave each member, with the member's name and time. A badge says Out of date or Extra copy when it differs from what runs now. Admins can Edit the member or Remove the copy. Empty: "No standing orders yet." |
| Shared knowledge (asserted for this team) | General facts added for the team, each with Remove. Empty: "No general knowledge has been added to this team yet." |
| What they have worked out (from the team's own cases) | Decisions recorded as precedents: the question, "Decided: …", the step, who decided (You decided or They decided) and a badge such as Worked out by them or Stated by a person |
A precedent is recorded whenever a case reaches a decision step. Empty: "This team hasn't worked anything out yet." If the Force has no project you see "This team has no memory space, so nothing it decides is being recorded". Link the Force to a project from the workspace header.
Remove an entry. Click Remove, then confirm "Remove this from the team's memory?" with Remove from memory. A toast says "Removed from this team's memory." Long lists show "Showing the N most recent of M", and the rest are still recalled.
Non-admins see "Only a team admin can change what this team knows."
Resources
Choose the Resources tab. It asks Which systems may this Force use? and starts with "This team acts as you." (or as the owner).
Whose accounts the team uses
The Force always runs as its owner. It uses the owner's connected accounts, plus any accounts teammates have lent. Every row says whose account it is: "Your own account", "(Name)'s own account" or "(Name)'s account, lent to this team".
| Group | Meaning |
|---|---|
| Shared systems (tag Org-wide) | Set up once by a platform admin. Shows whether it can read only or read and change records |
| Accounts this team signs in as (tag Per person) | Each person's own connections. A tag shows Connected, Not connected or Lent to this team |
To connect or disconnect an account, use Manage connectors (Settings → Connectors) as the owner. Only the owner can change what the team is connected to. Others see "Only (owner) can change what this team is connected to."
Warnings you may see:
- "You haven't connected any of these, so this team can't reach your mailbox or CRM on your behalf."
- "Some members reach fewer of these than the team does."
- "Some members sign in as a specific account", with what to fix.
Teammates lending connectors
Ask a teammate
Admins pick a name under Choose a teammate… and click Ask. A toast says "Asked. They decide — only they can switch it on, from their own connectors page."
They switch it on
Only the lender can start or stop lending, from their own Settings → Connectors. The row then shows Lending.
Stop at any time
A lender can withdraw at any time. The team stops using it then. Removing a teammate also ends their loan.
Statuses are Lending, Asked, Declined and Stopped. With nobody lending you see "Nobody is lending yet."
Teammates may hire on my AI key
The owner can switch on Teammates may hire on my AI key. It is off by default. When on, teammates can hire AI employees that run on the owner's AI key, so the owner is billed. Only the person who is billed can change it. Copying a Force turns it off. If a teammate who pays for a member leaves the project, that member stops until moved to the owner's key.
Tips
Back to Agent Force.