Secoda integration
Connect Secoda to service workflows to manage catalog users and groups and answer lineage questions on request.
What it connects
- Retrieve users, groups, and teams to confirm catalog access before a change.
- Pull catalog resources when someone asks where a dataset or table lives.
- Retrieve lineage for a resource to see which upstream sources feed it.
- Pull documents and collections when a question needs written context.
What it automates
- Create or update users when people join or change roles on the data team.
- Remove users during offboarding so former staff no longer have catalog access.
- Update group membership and manage teams to keep access aligned with responsibilities.
- Create and edit documents and collections when teams request new catalog content.
In practice
- A new analyst needs Secoda access. After approval, STLabs creates their user and adds them to the right group for their team.
- When an employee leaves, STLabs removes their Secoda user during offboarding, so catalog access closes along with their other accounts.
- An analyst asks which tables feed a revenue dashboard. STLabs pulls the lineage from Secoda and replies with the upstream resources.
- A team asks for a collection to organize its documentation. After approval, STLabs creates the collection in Secoda and links it on the ticket.
