|
|
|
|
|
|
by gregdoesit
1691 days ago
|
|
|
A very cool approach. When I worked at Uber, there were internal tools to query data sources. In practice, I found few people outside data scientists knew how to query the data, or know what was available. I was an engineer and barely used this tool, until a peer DS showed me how to do this. Even then I was overwhelmed by the number of tables to join, knowing what data source contained what data, or knowing which tables I had access to query or join on. A few questions: 1. How do you go about permission? This was a major question at Uber (where permission were put in place early enough). Especially with GDPR and other regulations, you cannot have anyone access any data. 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. 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. |
|
|
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.