Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Omni – Open-source workplace search and chat, built on Postgres

github.com

Post reply on HN
Print view View original

31–40 of 54 posts

Re: Show HN: Omni – Open-source workplace search and chat, built on Postgres

#34

Post by zaphoyd »

How are you managing multiplayer and permissions? I see in the docs that you can add multiple users and that queries are filtered by the requesting user such that the user only sees what they have access to. The docs aren't particularly clear on how this is being accomplished.

Does each user do their own auth and the ingest runs for each user using stored user creds, perhaps deduplicating the data in the index, but storing permissions metadata for query time filtering?

Or is there a single "team" level integration credential that indexes everything in the workspace and separately builds a permissions model based on the ACLs from the source system API?

Re: Show HN: Omni – Open-source workplace search and chat, built on Postgres

#37

Post by prvnsmpth »

zaphoyd wrote: post #34

How are you managing multiplayer and permissions? I see in the docs that you can add multiple users and that queries are filtered by the requesting user such that the user only sees what they have access to. The docs aren't particularly clear on how this is being accomplished. Does each user do their own auth and the ingest runs for each user using stored user creds, perhaps deduplicating the data in the index, but s…

So it depends on the app - e.g., Google has domain-wide delegation where the workspace admin can provide service account creds that allow us to impersonate all users in the workspace and index all their files/email. During indexing, we determine the users/groups who have permissions file and persist that in the db. (It's not perfect, because Google Drive permission model is a bit complex, but I'm working on it.) This model is much simpler than doing per-user OAuth.

In general, the goal is to use an org-wide installation method wherever possible, and record the identify of the user we are impersonating when ingesting data in the ACL. There are some gaps in the permission-gathering step in some of the connectors, I'm still working on fixing those.

Re: Show HN: Omni – Open-source workplace search and chat, built on Postgres

#39

Post by prvnsmpth »

philippemnoel wrote: post #38

(ParadeDB maintainer here). This is super cool. Congrats on the project, and I'm excited to see ParadeDB be used to power this kind of use case. If there's anything else you need to ship Omni, don't hesitate to reach out to me!

Thanks Philippe! You guys have been super helpful on slack!
Post reply on HN