Our team is really struggling to troubleshoot issue when the owner of a DataMesh or Data Shuttle is out of the office. Please allow multiple Admins and/or Editors (or, at the very least, Viewers) for these critical tools.
Sign in to see the current vote count, add your own vote, or leave a comment.
@kelly.m Nothing I've heard recently about adding sharing of DataMesh workflows! You can at least transfer ownership of those workflows.
Incorporating Datamesh roles or multiple owner capabilities into Smartsheet would significantly enhance its functionality and collaborative potential. Datamesh roles would allow for more granular control over data access and manipulation, ensuring that team members can interact with the data in ways that align with their specific roles and responsibilities. This would not only improve data governance but also streamline workflows by reducing bottlenecks associated with data permissions. Additionally, having multiple owner capabilities would facilitate shared ownership of critical projects, promoting accountability and continuity even if one owner is unavailable. This feature would be particularly beneficial for complex projects that require input and oversight from various stakeholders, ultimately leading to more efficient project management and better outcomes.
This could be a valuable tool, but hesitating allowing use as with only a single admin, it doesn't allow for oversight of what is being done or support. Also adds a risk if an employee leaves.
I second this as well. I use Data Mesh quite a bit and it's a risk to only have one person to be able to have access to a single Data Mesh at a time as if an unintended consequence occurs with the Data Mesh and the person who owns it is on vacation, there is no way to fix it until they get back.
We would also appreciate sharing DataMesh config with other admins. We have multiple admins in our teams and transferring ownership often is cumbersome.
IMO Datamesh shouldn't have even been made available to Smartsheet users since the Datamesh configs cannot be shared. For this reason, use of the Datamesh app in a business environment is a complete security risk. It would be a surprise to me if Datamesh hasn't been used by a disgruntled employee to sabotage their employers data in some way, shape or form. It's too bad that Smartsheet has not prioritized development of the Datamesh Config Sharing to provide the most basic level of security for its customers and users.
Very much agree!
I reached a cell reference maximum in a sheet due to the amount of lookup formulas we had. Data mesh seems like a good replacement so we avoid that maximum, but I can't move the process to data mesh without a level of comfort that someone else other than me (from initial setup) can maintain it. I would love to see it like what the dynamic views have in share settings:
New user to Data Mesh on SS… Has there been any update on this? This is a horrific implementation of any enterprise capability, let alone a core data management tool. I couldn't agree more with user "sandy." that DataMesh shouldn't even have been released without at least multiple user "view" permissions for configs and super admin access to all users' instances. Any employee with Admin access can do whatever they want in this environment without oversight or control. For a small team, this is a nuisance and issue as it means people either have to be in front of the same computer screen or have a virtual call and share screens to work on configs. Honestly, this is so bad, that if I had any way to move my current client off of Smartsheet to another solution, I'd do it. Unfortunately, since they've gone through training and bought a license, they want to stay with it. Smartsheet… This is truly an unforgivable oversight in the world of SaaS tools. You shouldn't have released this with such as GLARING oversight.
I have a workflow with nearly 40 automations, half of which are email-based requests for updates with various sets of triggers. While I know the automations work, due to months of testing, when our system went live to the institution, I became very worried that the automations wouldn't run and I'd have no idea whether or…
Description: When users upload multiple photos in one action via the Smartsheet iOS mobile app, all files are assigned the same generic name and timestamp. This makes it difficult to identify individual photos and creates confusion in workflows that rely on accurate, unique file naming. Why This Matters: Industry Standard:…
We are recently starting to use the Smartsheet API and Data Shuttle for maintaining Dashboards. We have discovered that the Data Shuttle workflow will notify the owner when the process completely fails, however it will not send notifications wuth a partial failure indicated by the Yellow Caution sign. Since many of our…
