A folder is a boundary
Select the folders each AI connection can read. Granting a parent folder includes its subfolders. Content outside that scope stays unavailable to the connection.
Your knowledge deserves
thoughtful boundaries.
Know what you’re sharing, who can access it, and how to turn that access off. Here’s how control works in folders.id.
Revocation takes effect immediately
Access is resolved on every request. Revoking a connection blocks its next request, without waiting for a token to expire. It does not delete copies already retrieved by an AI provider.
A record you can review
AI searches, reads, and refused requests are recorded. Review the activity in your workspace to understand which connection requested information and what happened.
Access follows the person
An AI connection or personal token cannot reach further than the person who authorized it. If that person loses folder access, their credentials lose that access too.
Suspicious content is surfaced
Extracted text is screened for prompt-injection patterns and flagged on the file. Screening is an additional signal for review; it does not guarantee that every malicious instruction will be detected.
Separate credentials, separate scope
Give scripts and integrations their own tokens, permissions, and folders. Manage and revoke credentials independently as your workflows change.
Make room for better work.
Start with a folder. Fill it with knowledge.
Find answers. Bring your team along.