Share, meet, and learn with your peers.
Ask questions, help other users, get involved.
Take full advantage of all the forum has to offer.
Browse discussions by category.
Help shape Domo by sharing your product ideas.
Blogs & Groups
Get tips and best practices from Domo users.
Events & Meetups
Network and swap stories at virtual & hybrid events.
Take challenges, build Domo skills, win prizes.
Domo Ovation Awards
See how community members rock their Domo.
Domo For Good
Help a non-profit with a meaningful data project.
Browse thousands of articles in Domo's comprehensive KB.
Get answers on how to use or troubleshoot Domo.
Here's what you need to know to start using Domo.
Data Creators & Analysts
Learn to analyze data and create reports for others.
Learn to create, view, and interact with data.
Learn to integrate, govern, and build data assets.
Get detailed instructions about how to use Domo.
Stay current with new product enhancements.
See how to complete key tasks with Domo.
Get product assistance from Domo Support.
Find training for your role in many formats, and get Domo certified.
Learn to use Domo
Get training that fits your budget and needs.
Get on-demand eLearning modules for your role.
Get remote live training in a public or private class.
Book a trainer to come get the team up to speed.
Get Domo certified and build your resume.
Start your free trial to start developing on Domo.
Docs & APIs
Use Domo to connect, process, and access data at scale.
Manage Client IDs
Log in to manage client IDs
That did it! Thank you!
Identifying all datasets connected to a credentials account
It's been some time since this question was posed and I have the same question. Anyone have any thoughts?
Data Permissions - Restrict Access to Underlying Data