-
Identify PDP Policies with no members (individuals or groups)
We've all seen this happen… you have a PDP policy set and a user leaves the company… there are no members left in the PDP policy. Would be nice to have a way to identify these cases in the PDP Domo Stats dataset. Today you'd have to go to each PDP policy and scroll through looking for the orphaned items. If I'm missing…
-
Include User Landing Page in "People" DomoStats
It's great that we can set a landing page and mobile landing page for each user in the admin settings but there is no way to globally view all set landing pages outside of clicking into each user profile. With 300 users we need this added as a column into DomoStats to assist with administration. Thanks!
-
Separate "from" email addresses for Alerts/Scheduled Reports and User Management
I've recently had multiple users in our instance claim not to have received a password recovery email after clicking the "Forgot Password" button from the login screen. We eventually found that the email had been moved to a different folder because they had an inbox rule for scheduled reports and both emails were being…
-
Connect DomoStats Across Instances
Need the ability to get Domostats for multiple instances under the main instance. We use separate instances to keep our clients info separate from others while our company utilizes the main instance as storage of all information. The issue is keeping track of users login information and who is in these instances are not…
-
PII Detection
While there is a 3rd party solution in the app store (PII Vault), I think Domo should have automated built in PII governance tools integrated into the toolkit. There could be a UI in the governance toolkit where you tick off various standard PII patterns to look for (SSN, Phone, Birthday etc) or even let you define a…
-
bricks that can be edited by more than one user
Currently DDX Bricks can only be edited by the creator of the "App" This is by design, and can be found documented in the "Getting Started with Domo Bricks" article. idea: make DDX bricks editable by all owners and admin, and allow the checkbox on card details to restrict access to non-owners.
-
DOMO Role
Hello, This request refers to the possibility of granting a user with Developer access to specific objects (datasets, pages, cards), and Participant role to the rest of the instance. Is this possible? Thanks, K.Nagesh
-
"Delete This Update" for Dataset Owners
Dataset owners should be able to delete specific updates without being Admins. Currently, dataset owners can delete the entire dataset, but not specific updates unless they are Admin users. The "Delete This Update" option is only available to Admins,
-
Audit Domo Configuration Changes
I don't see changes to the domo security configurations (specifically authentication settings changes) in the activity logs. We have enabled mfa, but then it was somehow disabled and we would like to audit for these types of changes. I spoke with Domo support and they have suggested that we request this functionality in…
-
Trigger Toolkit jobs from schedule
We have a group management toolkit job that uses a webform as the configuration dataset. The issue is that the toolkit job only runs when the configuration dataset updates. Since it isn't the configuration data that is changing, but rather the group referenced in the webform configuration data, our job didn't run for 2…
-
Ability to turn off the "REQUEST MORE ACCESS" button for Social users
We have over 1,200 social users and it is a headache to deal with so many users clicking this button on a weekly basis.
-
Tool Tips for Consumption Model and/or 'Online Shopping' model
Working with Telus Communications reviewing the Consumption Model recently. In order to simply their charge-back system and allow individual groups to grasp, understand, and manage their own buckets of execution credits, it was suggested: "Might be a good idea to add Tool Tips for any credit/execution consuming tasks,…
-
Group Ownership of BeastModes
Recurring request from more than one Enterprise level account is to allow Group Ownership functionality of Beast Modes. There is not currently a way to lock them down and there are a lot of manual steps involved with changing permissions, etc. Allowing group ownership would be a major time saver and help with overall ease…
-
Page sharing grant for Participant Users
We are using the Domo sandbox, so we have a sandbox instance and a production instance. In our production instance, all of our users are participants. We would like a user grant that would allow participant users to share pages that they own. This would give our users more ownership and control of their pages, and there…
-
Ability to share pages (not just cards) without Manage All grant for Domo Everywhere
My company whitelabels Domo as an offering within our software to allow our customers to report on their data from our product. Each customer has their own subscriber instance that we push a pre-defined set of data sets and dashboards to. I have a Customer Editor role, which grants the "Edit Cards" and "Edit Pages"…
-
Limit options in page filters
I do not need all the fields from the dataset or all the BEAST MODES created to be available for the end-user, as they might get confused with the hundreds of fields available in the drop-down. I want to restrict the fields that I want to show to the customer on the page level based upon the business. I might use many…
-
Improved CSS for Page Modals on Groups
When creating a new group it is sometimes difficult to see which dashboards and cards to add to the group especially if the names are lengthy as they get cut off by a wrap style. I suggest a CSS change to allow the modal to be most of the view width. Existing Modal Improved Modal The CSS changes are quite simple:…
-
Adding field to show beast modes not used in a card
Adding a field to the Governance: Beast Modes with Field dataset, that includes Beast Modes not used in a card. Currently there is no reporting to identify beast modes not used in a card without going into Beast Mode Manager, that could be used for Domo instance clean-up.
-
Extend the grants section for setting up roles to include 'Certified' content
It would be good to have a grant / setting so that you could prevent users/roles/groups from seeing uncertified content. If it was added at a grant level for Roles then we could create custom Groups such that some users can see uncertified content, and others can't. This could be separated out by what the object type is…
-
Dataset Views Governance
The versioning history available on Dataset Views is only accessible when editing the view and doesn't appear to be included in any Governance reports. In addition, the version history view lacks key information such as old/new calculated field syntax and user info. Finally, the version history view appears to attribute…
-
add group owner (and related fields) to the governance dataset groups
see case
-
Hide Dashboard User Access List
I would like to propose adding the ability to hide the section of the Dashboard title bar that shows the users that have access to the page. Ideally, I'd want to either hide this section, by default, from anyone that did not have sufficient permissions to grant others access to the dashboard or have the ability to set the…
-
More Granularity in the 'Manage' Role Grants
We have end users with the required access to view all data assets in Domo to fulfill their job description. For example, we have some users that need to be able to see all datasets and dataflows in lineages with the ability to navigate freely as part of their job as Technical Program Managers. However the only way to…
-
Provide details on when Domo will attempt to run a dataset again
As an Admin or Editor I want to see the details of when Domo will attempt to run a dataset again. In order to know if I should try to manually kick off a dataset, or wait for Domo to run it. Currently the Interface shows this when there is an isssue: When clicking view details, it takes you to the History tab. I would like…
-
Allow users to manage financial year uploads
We have multiple customers using different financial years within domo and from time to time they like to either completely change these or make small modifications such as pushing a 53 week into the following year etc. If would be great if we could manage these sets ourselves rather than having to create tickets with domo…
-
Add ability restrict export of individual cards
We need the ability to restrict the download of specific cards without turning download off for users across the instance. Can this feature be considered? Another way to do it would be to embed in the PDP permissions of a policy. That way we can assign which policies can export.
-
DOMO GOVERNANCE PAGE OVERLAY
It would be really nice as an Admin to look at a page/dashboard and see some sort of overlay giving governance information. For example, look at a page/dashboard and see a color highlighted overlay showing the most used/least used card, or see a number pop up of who the users are that are viewing the card most recently.…
-
Changing Dataflow Owner
If someone owns a dataflow they should be able to go in and change the owner from themselves to another person. Currently, only an admin or someone with the "manage all dataflows" grant can do this.
-
Share edit permission for Domo Brick code
I've tried adding other members of our team as Admins on the Domo Brick app I installed and also tried adding them as Owners on the resulting card within the main Admin settings, but they still are unable to edit the brick without doing a "Save As" and creating another card. I'm requesting to add the option to share Domo…
-
Splash Page for when page needs maintenance
Ever needed to make a few changes on a dashboard that is in production without having the users see behind the curtain? Small enough to feel like using Sandbox staging doesn't make sense? I think being able to toggle a "Splash Screen" with a few customizable fields to show that a page is under maintenance for a short time…