90 karma · joined March 19, 2020
and ofc, feel free to reach out if your team needs help with setup
On permissioning: we default to per-user syncs that adopt the permissions of the syncing user and mirror source ACLs (e.g., Drive items a user owns or that are sharedWithMe). In practice, founders avoid leaking private docs by either (a) having each user sync their own corpus, or (b) using a centrally-scoped token limited to Shared Drives/team folders and excluding personal “My Drive.” You can also keep separate collections and only expose cross-user search behind your own checks. We’re exploring richer org-level RBAC mapping on a per-customer basis (e.g., mapping Drive/SharePoint groups to index ACLs), but the above works today.
@Weves: Thanks, appreciate it!
we originally built this for our previous agent startup as an internal solution to ensure agents could find the relevant data on apps they're using. We then pivoted to this after some early positive reactions and decided to open-source it.
here's a short demo: https://tinyurl.com/demo-airweave
we're two engineers/friends based in Amsterdam, NL. We just launched the project, so it's rough around the edges ofc, but we're very eager to get some feedback!
feel free to reach out to me personally if you like this! - https://www.linkedin.com/in/lennertjansen/ - https://x.com/lennertjansen