Great job with the UI. Looks really clean. One concern many data teams might have with this is around how something like verifies that the queries are correct before sharing it with the rest of the company. Have you thought about a solution for that?
So right now a user can create a query, save it, and share it with their teammate for verification. Their isn’t currently a more automated workflow to do this, but it is something we are definitely exploring.
You're spot on. One thing we're doing to deal with the long tail of integrations is opening up an API to customers.
We're also considering open sourcing that part of the product, but haven't made a firm decision on that yet. Would love to chat if you're open to it. We're definitely looking for people in product. Feel free to send me an email to etai@secoda.co
We have pretty advanced RBAC in Secoda. You can make anyone a viewer, guest, admin or editor in the workspace. Viewers and Editors are only able to see the information. Secondly, we allow you to create "groups" for different functions in the organizations (ie. marketing, sales etc.). You can choose to share any resource with a specific user or group. This works similar to the RBAC that Notion uses, which only means that the right people are seeing the right information in Secoda. Lastly, we allow data teams to create "collections" of information, which can be shared with specific groups or specific users. Without sounding bias, I think this is where Secoda excels as a product.
2. What about PII? Some data needs to be stored, but cannot be viewed except for very, very few people and with a strong audit tail. This is a more specialized case for #1.
We have an ability to auto tag PII on a table and column level. Any PII data won't be viewable without permission from the admin.
3. How do you see the tool "spread" the most within companies? I would assume that easy sharing is how people learn about this, then try it themselves... but would love to hear what you actually see.
Usually the Slack integration is the best way to spread Secoda. With our Slack integration, any employee can search for information by pressing /secoda in Slack. You can also push information from Slack to Secoda and vice versa. This exposes Secoda to new employees in the place they work.
Ideally, no team has to answer the same question twice once they start using Secoda. In reality, there's times when are question looks similar but is defined differently. We're trying to suggest resources to people who ask questions so they become more self service. Similar to Intercom knowledge hub for data.
