Best Of

I recommend using the Domo Governance Datasets Connector to keep track of all your existing content. The "Datasets" report is especially helpful since you can more easily see names and descriptions of all the datasets in your instance.

If you don't do so already, I encourage you to use a standard naming convention across all datasets so you can easily see different attributes of your datasets such as department. That way you can more confidently search for whether data exists to fit a particular need.

My organization wants to be able to collaborate with one of our customers to develop performance metrics that combine their data with our own. We are considering providing members of their technology team access to our Domo instance so that they can accomplish any of the following tasks:

1. Create/edit datasets from their own systems (ODBC, file upload, API connector, etc.)
2. View/edit dataflows that use the datasets they own
3. View/edit cards and pages that use the inputs/outputs of the dataflows they have access to

It's also critical that we keep their access very limited because of the amount of proprietary data that we already have in Domo that they should not be able to see. This is my current plan for managing this initiative, but I am open to feedback or suggestions:

1. Create a shared user for the external team using the default Editor role
2. Add the user to a new group that includes any internal collaborators
3. Run all relevant internal datasets through dataflows to remove sensitive information (financial information, customer names, etc.)
4. Share the cleansed outputs of the dataflows with the group so everyone can access downstream dataflows
5. Share any datasets created by the user with the group
6. Create dedicated page(s) for the group to add/edit cards

I'm open to input from anyone who has had a similar situation or if I'm missing any crucial for security. We haven't had much use for custom roles or PDP, so I'm curious whether I should consider those options as well. Thanks!