How Profiles Control What Each AI Agent Can Access in Takibi Base
A Profile in Takibi Base bundles a tool's API keys with its document permissions, so every key in that Profile reads exactly the folders you assign to it. To scope access, create a separate Profile for each tool that needs different reach, then open its Access tab, choose Edit, and select the folders it should read. Folder access automatically extends to documents you add later once they are indexed; project-level access is broader and Takibi asks you to confirm it.
What a Profile actually holds
A Profile is the unit that ties two things together:
- Keys — the credentials a tool uses to call Takibi.
- Document permissions — the folders those keys are allowed to read.
Because permissions live on the Profile rather than on individual keys, every key inside a Profile inherits the same access. That is why the recommended pattern is one Profile per tool with a distinct access need, instead of one shared Profile for everything.
Setting folder access step by step
- Create a Profile for the tool you are connecting.
- Open the Profile's Access tab and choose Edit.
- Select the folders the Profile should be able to read.
- Confirm if you are granting project-level access, which is wider than folder access.
Expected result: when that tool asks a question through the CLI or API, Takibi searches only the sources the Profile can read.
Folder access vs. project access
| Access level | What it covers | Confirmation |
|---|---|---|
| Folder access | The selected folders, plus documents added to them later once indexed | Not required |
| Project access | Future folders and documents outside folders as well | Takibi asks you to confirm the broader access |
The distinction matters because folder access is forward-looking within a folder, while project access reaches beyond any single folder. If a tool should never see a new folder you create later, keep it on folder access.
What the agent gets back
When a tool asks a question, Takibi returns matching passages, citations, and an evidence support score. A CLI call looks like this:
$ takibi ask -q "What is our refund policy?" --json
The response includes spans with the exact passage text, a documentId, documentName, chunkId, and title, plus a citations array and a support score (for example 0.4, with supportVersion: "v1"). If no matching evidence is found, Takibi returns no passages — the agent gets source text and a citation for each passage rather than an unsourced answer.
Common sticking points
- New documents aren't searchable immediately. Folder access includes documents you add later once they are indexed. Check whether a file is indexed, converting, or quarantined before assuming access is broken.
- Permissions are per Profile, not per key. If two tools need different access, splitting keys inside one Profile won't work — create separate Profiles.
- Project access is easy to grant by accident. It covers future folders and documents outside folders, so confirm deliberately.
- Demo changes don't persist. Sample workspace edits reset on refresh, and uploads, imports, downloads, and billing require your own workspace.