← Back to app

Help — MyDataWork

MyDataWork is a workspace for data analysts. It catalogs the files and cloud assets behind your work, visualizes how they connect, tracks use cases and business outcomes, and helps you communicate the value your data work delivers.

Getting Started

• Register at mydatawork.com — new accounts start on the free 90-day Explorer trial automatically. Paid Solo and Team plans are also available with a 14-day free trial.
• On first login, the setup wizard opens automatically. Pick one path: Use demo data to explore a populated workspace immediately, Connect local files via the Windows Connector, or Connect cloud sources directly. Demo data is reversible — you can remove it any time from Setup → Connect your data, and reload it from the same spot if you change your mind.
• Dashboard tab opens first on every visit — a 10-second read of workspace health (staleness, portfolio totals, stakeholder coverage, value distribution, tool distribution, agent activity). See Asset Health Dashboard ↓ for details.
• To connect your own files: download and install the Windows Connector from the Setup tab, enter your setup code when prompted, and choose your folders. Your files appear in Assets automatically.
• To connect cloud-based assets (GitHub, dbt, Databricks, Snowflake): go to Setup → Cloud Sources and enter your credentials. No installation required.
• Once you’ve added real assets and configured a few use cases, run the Asset Estate Assessment from Setup — an AI-powered review of your workspace, first run free on every plan. See Asset Estate Assessment ↓ for details.
• Passwords must be 12 or more characters when registering. Passphrases are recommended.

Asset Health Dashboard

Dashboard is the first tab on every workspace. It surfaces six panels of workspace health at a glance — designed to be read in seconds before you dive into the rest of the app.

• Use case staleness — distribution of your active use cases across freshness buckets (under 30d / 30–60d / 60–90d / 90+d since last update). The 90+d bucket is the same threshold the Workspace Agent fires its stale-use-case rule at.
• Portfolio totals — estimated vs realized value across active use cases, plus the realization rate.
• Stakeholder coverage — how many of your active use cases have an assigned stakeholder.
• Value distribution — your use cases’ realized values plotted against the workspace mean and median (the same robust-statistics check that powers the Portfolio outlier hint).
• Tool distribution — asset count by tool family (SQL, Tableau, Excel, …) for the current view.
• Workspace Agent activity — suggestions surfaced and acted on in the last 14 days.

The dashboard reflects what you see on the Assets tab — your own assets plus any shared to the team. Admins can see the full workspace catalog on the Setup → Workspace view if needed for oversight.

Demo / real toggle — when your workspace has demo data loaded, a small segmented toggle in the upper-right lets you switch the dashboard between the demo view and your real-data view. The toggle is dashboard-only: it doesn’t change what’s shown in Assets, Use Cases, Suggestions, or the Assessment. When you remove demo data, the toggle disappears and the dashboard renders from your real data only. If your workspace has neither real assets nor demo data, the dashboard shows a "No real assets connected yet" empty state with shortcuts to Setup or to load demo data.

Asset Estate Assessment

An AI-powered review of your workspace, runnable on demand from Setup → Asset Estate Assessment. Surfaces connections worth documenting, use case opportunities, and health observations — the kind of analysis a senior analyst would write up after auditing your estate. First run is free on every plan — one free assessment per email, forever. You can re-run the assessment any time afterward; subsequent runs use AI credits like other AI features.

• What it produces — a 5-section markdown report: Estate overview (asset count, tool families, portfolio totals, realization rate, stakeholder coverage), Connections worth making explicit (lineage + structural observations), External dependencies (schema-qualified table references your work depends on but you don’t catalog), Use case opportunities (reuse and consolidation findings), and Health observations (Workspace Agent findings + automation candidates). Plus a Concrete next actions list ranking the top items.
• Demo path — preview the format any time without burning your free run. View demo assessment renders a curated example so you can see structure and depth before committing.
• When to run it — after you’ve connected real assets and configured at least 2 active use cases. The assessment is use-case-driven: value, stakeholder, and staleness analyses all key off use cases. With fewer than 2 active UCs, the Run button is disabled and an inline explainer tells you why.
• Soft-floor confirm — if you run with fewer than 10 real assets, a confirmation modal asks you to confirm. You can still proceed; the prompt is there because thin estates produce thin output and the free run is one-time.
• Export — the result is viewable inline (markdown rendered in the Assessment card) and exportable to PDF. The PDF carries the workspace name, who it was generated for, and the timestamp.
• What the assessment reads — asset metadata (names, paths, tool types, topic tags, lineage edges) and use case text (titles, objectives, descriptions, value figures, stakeholders) only. File contents are never read — the same boundary that applies to every other AI surface in the app.
• One free per email forever — eligibility is tracked per email address (hashed for privacy). If you used your free run in another workspace under the same email, you’re routed to the paid path (uses AI credits) for a second one in a new workspace.

Two Ways to Connect Your Assets

📁 Local File Folders

Install the Windows Connector once. It runs silently in the background, scanning the folders you choose and keeping your workspace current automatically.

Best for: Excel, SQL, Python, Power BI, Tableau, Alteryx, CSV files on your PC or synced cloud drives (OneDrive, Google Drive, Dropbox).

☁️ Cloud Sources

Connect directly to cloud platforms using an API token. No installation required — works on any device.

Supported: GitHub repositories, dbt Cloud projects, Databricks workspaces, Snowflake databases.

The Windows Connector

The MyDataWork Connector is a small background process that scans your chosen folders and sends file metadata to your workspace. It starts automatically when you log in to Windows.

• Install once from the Setup tab — download, run the installer, enter your setup code.
• Use Connect folders (Assets or Setup tab) to add or change folders at any time.
• Use Rescan now (Setup tab) to pick up recent file changes immediately.
• The Connector never reads or transmits file contents — only names, paths, file types, and basic metadata.
• Cloud-synced folders (OneDrive, Google Drive, Dropbox, Box) are fully supported.

Cloud Sources

Connect cloud platforms directly from Setup → Cloud Sources. No installation required. Each source type needs an API token or credentials.

Source	What's indexed	Credentials needed
GitHub	Data files (.sql, .py, .ipynb, .xlsx, .csv) across repositories	Personal Access Token with repo read access
dbt Cloud	Models, sources, and exposures from dbt projects	dbt Cloud API token and account ID
Databricks	Notebooks and jobs from your workspace	Workspace URL and personal access token
Snowflake	Tables and views from your databases	Account, username, password, database, schema

Cloud source assets appear in the Assets tab alongside your local file assets, with a badge showing their source (GitHub, dbt, Databricks, or Snowflake).

What gets cataloged through your cloud connections

When you connect Snowflake or Databricks to MyDataWork, you’re connecting more than raw tables. You’re cataloging the work products of every tool that writes into those warehouses — which, in the modern data stack, is most of them.

This is one of MyDataWork’s core design choices: integrate with the warehouse, not the dozen tools that use it. When your stack evolves, MyDataWork follows automatically. If it lands in your warehouse, it lands in MyDataWork.

Tools whose work products are cataloged via your warehouse connection

These tools persist their outputs as tables, views, materializations, or model artifacts in Snowflake or Databricks. When you connect your warehouse, MyDataWork catalogs those objects automatically — schema, columns, lineage, freshness — with no tool-specific integration needed.

Transformation

• dbt (Cloud or Core) — compiled models, snapshots, seeds
• Coalesce — visual transformations compiled to tables and views
• Matillion — pipeline outputs landed in target schemas
• Prophecy — visual data engineering, particularly strong on Databricks

Analytics and BI builders

• Sigma — warehouse views, materializations, input tables, CSV uploads
• Hex — Snowpark dataframes, published datasets

ML and data science

• Dataiku — recipe outputs, dataset materializations
• DataRobot — batch prediction tables, deployed models as Snowflake UDFs
• Alteryx — workflow outputs
• Datameer — published views and tables

Data movement (the landing zone for your warehouse)

• Fivetran — replicated source tables from SaaS apps and databases
• Airbyte — open-source equivalent of Fivetran

Tools that read from the warehouse rather than write to it

These tools query your warehouse but persist their own state — dashboards, semantic models, extracts — in their own cloud. MyDataWork catalogs the source-of-truth tables they depend on, so you can see what data feeds each dashboard and what would break if a column changes. The dashboards themselves live in those tools’ own admin consoles.

• Tableau
• Power BI
• Looker
• ThoughtSpot

Tools whose data lives in their own backend

These tools store their data in their own cloud, not in your warehouse. To catalog them in MyDataWork, replicate their data into Snowflake or Databricks first — typically via Fivetran, Airbyte, or a similar service. Examples:

• Smartsheet, Airtable, Monday, Notion
• Salesforce, HubSpot, NetSuite
• Most SaaS app data

Direct connectors not dependent on a warehouse

MyDataWork also catalogs assets from these sources directly:

• Local files via the desktop Connector (Excel, CSV, Python notebooks, code files, and more)
• GitHub repositories
• Cloud file storage (Google Drive, OneDrive, SharePoint, Dropbox)

A practical example

A team uses Snowflake as their warehouse, dbt to transform data, Sigma to build analytics, DataRobot for ML predictions, and Tableau for executive dashboards. They also use Smartsheet for project tracking.

When MyDataWork connects to their Snowflake:

• dbt models, snapshots, and seeds are cataloged automatically
• Sigma’s warehouse views, materializations, and input tables are cataloged
• DataRobot prediction tables and deployed models are cataloged
• The Snowflake tables Tableau queries are cataloged — the Tableau dashboards themselves are not, since those live in Tableau
• Smartsheet data is not cataloged unless the team replicates it to Snowflake first

The strategic point

The modern data stack consolidates around the warehouse. By cataloging what lives in your warehouse, MyDataWork covers the work products of essentially every modern data tool — without you waiting for tool-specific connectors, and without losing coverage as your team adopts new tools.

Frequently asked questions about supported tools

Question	Answer
Does MyDataWork support [my specific tool]?	MyDataWork integrates with your data warehouses (Snowflake, Databricks) and with local files via the desktop Connector. Most modern data tools (dbt, Sigma, Hex, Dataiku, DataRobot, Alteryx, Fivetran, Matillion, Coalesce, Prophecy, Datameer, Airbyte) write their work products as tables and views into your warehouse, and those outputs are cataloged automatically when you connect your warehouse — no tool-specific integration needed. BI tools (Tableau, Power BI, Looker, ThoughtSpot) query the warehouse rather than writing to it; MyDataWork catalogs the source-of-truth tables those dashboards depend on. Tools whose data lives in their own backend (Smartsheet, Airtable, Salesforce, HubSpot, etc.) require replication to your warehouse first via Fivetran or Airbyte. See What gets cataloged through your cloud connections for the full breakdown.
What if my team adopts a new tool you’ve never heard of?	If the new tool persists its outputs to Snowflake or Databricks, MyDataWork catalogs those outputs automatically — no waiting for a tool-specific connector. This is the design choice: MyDataWork integrates with the warehouse, not the dozen tools that use it. If the new tool stores data only in its own backend, replicate it to your warehouse via Fivetran or Airbyte and the resulting tables become cataloged like any other warehouse object.

Managing Cloud Sources

To remove a cloud source, click Remove next to the source in Setup → Cloud Sources. A confirmation dialog gives you a choice:

• Keep assets in my workspace (default) — disconnects the source but preserves all imported assets in your Assets tab. You can manage them individually later.
• Also remove all assets from this source — disconnects the source and soft-deletes all assets imported from it. Removed assets can be restored individually at any time — use cases, lineage edges, and stakeholder links are all preserved.

For GitHub connectors configured with multiple repositories, “Also remove all assets” applies to all repos in that connector.

What Metadata Tells You

From metadata alone — without ever reading file contents — MyDataWork can tell you which Excel models feed which Power BI dashboards, which SQL scripts populate which reports, and how your entire data landscape is connected.

• File name and path — where it lives and what it's called.
• File type — Excel, SQL, Python notebook, Tableau, Alteryx, CSV, and more.
• Sheet names (Excel) — understand what's inside without opening the file.
• Column names (CSV) — see the structure at a glance.
• SQL tables — FROM/JOIN references show which tables a query touches.
• Notebook signals — embedded SQL and imports extracted from .ipynb files.
• Cloud asset paths — repository, project, workspace, and schema context from cloud sources.
• External dependencies — data sources detected in your files that are not currently cataloged as assets are flagged with an amber "Not in catalog" badge in the Assets tab, and shown as ghost nodes in the Lineage visualization. These represent invisible dependencies your work relies on that are not yet tracked in your workspace.
• Added by — for Team workspaces, each asset shows which team member connected it, so you always know who owns each piece of work.
• File size and creation date — for files scanned by the v1.1 Connector, the asset detail panel shows the file's size (formatted KB/MB/GB) and its creation date. On Linux, where the filesystem doesn't expose a true creation timestamp, the modification date is shown instead and labeled "Modified".

Asset Status Badges

Assets in the Assets tab may show status badges indicating their current state:

• Removed (red) — Removed by user. The asset was manually removed from the workspace. Restore it from the asset detail panel, from the Assets tab's "Removed" relevance filter, or from any use case's Assets & People tab where it appears in the "Linked assets that have been removed" section.
• Infrequent (yellow) — The asset has not been updated or accessed in approximately 90 or more days, indicating it may be stale by age.
• Source unreachable (orange) — The Connector tried to scan this asset but could not reach its source location. Common causes: network share disconnected, VPN dropped, file server unavailable, or permission denied. The asset’s metadata is from the last successful scan, shown as “Last synced” in the asset detail panel. The badge clears automatically once the source becomes reachable again and the next scan succeeds.

Hover over a Source unreachable badge to see the specific error type: path not found, permission denied, timeout, or OS error.

Supported File Types

Type	Extensions	What's extracted
Excel	.xlsx, .xlsm	Sheet names
CSV	.csv	Column names
SQL	.sql	Table references (FROM / JOIN)
Python notebooks	.py, .ipynb	Embedded SQL tables, imports
Alteryx	.yxmd	Connection hints
Tableau	.twb, .twbx	Connection hints
Power BI	.pbix, .pbit	File name and path
ThoughtSpot	.tml	Object kind (worksheet / model / answer / liveboard), tables and connections referenced
Dataiku	.zip (DSS project export)	Project name, recipe count, dataset count
Looker	.lkml (.view.lkml, .model.lkml, .dashboard.lkml)	Object kind, dimensions, measures, connection, sql_table_name references
GitHub	All data file types	File path, size, last modified
dbt Cloud	Models, sources	Model name, project, materialization
Databricks	Notebooks, jobs	Notebook path, language, last modified
Snowflake	Tables, views	Table name, schema, row count, last altered

ThoughtSpot, Dataiku, and Looker integrations support file-based metadata extraction. Cloud-native instances of these tools require export or local file access.

AI-Powered Features

MyDataWork includes several AI-powered features that require AI to be enabled in your workspace. Go to Setup → AI Assist to enable AI. Once enabled, the following features become available:

• Use Case Recommendations — AI analyzes your use case descriptions, linked assets, and progress notes to surface ideas and improvements specific to your work.
• Leverage: Find reuse opportunities — Identifies consolidation and reuse opportunities across your use cases.
• Leverage: Identify automation candidates — Analyzes your use cases and assets to identify business processes that could be candidates for intelligent automation. Results are saved and can be shared via email.
• Leverage: Discover marketplace data — Recommends external datasets from your configured cloud providers (AWS, Google Cloud, Snowflake, Azure, Databricks) that could enrich your use cases. Configure your cloud providers first in Setup → Cloud Providers.
• MyDataWork Assistant — A context-aware chat assistant available from the teal button in the bottom-right corner of every screen. Ask it anything about navigating the app, understanding your workspace, or deciding what to do next.
• Workspace Agent — Proactive observation across six rules. The Suggestions tab has an Analyze button that surfaces workspace state worth your attention: missing stakeholders, recently-added assets not linked to a use case, removed assets still in use, stale use cases, high-value use cases tracking below estimate, and assets serving many use cases (hidden infrastructure). You're charged 1 credit per suggestion surfaced — a run that finds nothing costs nothing, and most runs cost just a few credits. The ceiling is 8, reached only when all six checks find something at once. First run is complimentary.
• Leverage: Migration Assist — Analyzes your assets or use cases to identify opportunities to migrate or modernize tools. Choose single asset analysis to evaluate specific files, or use case analysis to evaluate an entire workflow end-to-end. Results include recommended alternatives, migration effort (Low/Medium/High), estimated benefit, key risks, a suggested next step, and a confidence rating. Results are saved and shareable via email. Requires AI enabled in Setup → AI Assist.

All AI features share a daily credit quota. Solo users receive 5 AI credits per day. Team plan users receive 20 per day. Credits reset daily. The Assistant draws from the same quota.

Leverage Tab

The Leverage tab is your AI-powered analysis hub. It offers four modes, each requiring AI to be enabled:

• Find reuse opportunities — Select use cases and generate AI analysis identifying where work overlaps or could be consolidated.
• Identify automation candidates — Select use cases and generate a list of processes within your work that could potentially be automated by an AI agent. Each opportunity includes a title, description, related assets, estimated value, complexity level, and a suggested next step. You can share any opportunity via email directly from the app. All generated opportunities are saved and accessible in the archive below the results, even after navigating away.
• Discover marketplace data — Select use cases and generate recommendations for external datasets available on your configured cloud platforms that could improve or enrich your work. First configure your cloud providers in Setup → Cloud Providers. Recommendations can be dismissed individually and previously generated recommendations are saved in an archive section.
• Migration Assist — Analyze individual assets or full use cases to identify tool modernization opportunities. Two analysis modes: select individual files grouped by tool type (single asset analysis), or select a use case to evaluate all its linked assets as an end-to-end workflow (use case analysis). Each recommendation includes current tool, recommended alternative, migration effort rating, estimated benefit, key risks, suggested next step, and a confidence rating. Low or Medium confidence results include an explanatory note. Results are saved in an archive and can be shared via email. Configure in Leverage tab → Migration Assist mode.

Workspace Agent

The Suggestions tab includes a proactive observer that scans your workspace on demand and surfaces six categories of state worth your attention. Click Analyze and the agent runs every rule eligible for your plan, producing suggestions with deep-links to the relevant asset or use case.

The six rules group into three categories:

• Cleanup (patient, not urgent):
  • Active use cases that have at least one linked asset but no stakeholder assigned.
  • Active use cases that haven't been updated in 90+ days — worth reviewing whether they're still active or can be archived.
• Activity (something changed and needs attention):
  • Recently-added assets (within the last 14 days) that aren't linked to any use case yet, where keyword overlap suggests a best-fit existing use case.
  • Assets removed within the last 30 days that are still referenced by an active use case or a lineage edge — broken dependencies that may not have been intentional.
• Insight (strategic observation):
  • Active use cases with high projected value, low realized value (< 25% of estimate), and no updates in 60+ days.
  • Assets linked to three or more active use cases — the "hidden infrastructure" of your workspace where governance attention is warranted.

Each suggestion can be dismissed with a reason (not relevant, already handled, revisit later) and reacted to with 👍/👎 feedback. Auto-resolve: when a suggestion's condition no longer applies (you assign the stakeholder, link the asset, restore the removed asset), it's automatically marked resolved on the next run.

Your first Analyze run is complimentary. Subsequent runs draw from your daily AI credit pool, with a ceiling of up to 8 credits per run (shown above the Analyze button before you click). In practice runs usually consume far fewer credits because most rules don't find candidates.

Use case notes URL

Each use case has a Notes URL field on the Overview tab. Paste a Google Doc, Notion page, Confluence URL, or any HTTPS link where you keep notes for this use case. When set, an "Open notes ↑↗" button appears in the panel and a small ↑↗ indicator shows next to the use case in the list view.

Team Workspaces

• Add members — The workspace admin creates accounts by entering name, email, and a starter password in Setup → Members. Share credentials with the member directly. They should change their password on first login via Account settings.
• Manage members — The admin can view all members with usage stats (assets, AI credits), remove members, and see seat usage. Removing a member deletes their workspace access but preserves their content for the remaining team.
• Transfer admin — Click “Transfer admin” next to any member to hand off workspace ownership. You become a regular member. There is always exactly one admin per workspace. If the admin leaves without transferring, contact support.
• Seat limits — Team Starter: 2–5 seats. Team Growth: 6–10 seats. The admin counts as one seat. When at the limit, the add-member form shows a message to remove a member or upgrade.
• Asset ownership — Each asset shows who connected it (Added by: [name]) so team members know who owns each piece of work.

Team Collaboration

Team workspaces are private by default for every role — including admins. Each member’s assets and use cases are visible only to that member; the team admin sees the same private-by-default view of their own work. The asset list defaults to a merged view showing your own assets plus any asset another team member has explicitly shared to the team.

The Assets tab has a toggle — All (default, your own + shared), Mine (only your own), and Shared (only team-shared) — so you can focus on what’s relevant. Admins additionally see a Workspace tab that exposes the full workspace catalog when needed for onboarding, audit, or oversight tasks. Use of the Workspace view is explicit, not the default. The Use Cases tab has an All / Mine toggle (plus the admin-only Workspace tab); use-case sharing is on the roadmap and a Shared option will appear there when it ships.

• Sharing an asset — Open any asset you created in your Assets list and click Share to Team in the detail panel. A small blue “shared” label appears next to the asset in your list. The asset now also appears in the Shared tab for all team members.
• Browsing and copying shared assets — Switch to the Shared tab at the top of the Assets view. Browse assets shared by other team members, each showing “Shared by: [name].” Click Copy to mine to create an independent copy in your own private view that you can link to your use cases and build lineage from. Copies are fully independent — no live sync.
• Unsharing — The person who shared an asset (or the team admin) can click Unshare to remove it from the Shared tab. Copies already made by other members are unaffected.
• Mutation rules — Each member can only edit, remove, restore, share, or unshare assets they created. The team admin can edit anything in the workspace via the Workspace view. Lineage rebuilds and workspace exports are admin-only.
• Admin Workspace view — Admins use the Workspace tab on the Assets and Use Cases tabs (and the workspace-wide toggle on the Suggestions tab) to surface every member’s work for oversight, audit, or onboarding. Outside that opt-in view, admins see only their own work plus team-shared assets — the same default view a regular member sees.
• Demo data — The demo data loader is open to any member on a paid plan. Each member can import their own demo set into their own private view.
• For team admins: Team Metrics — The Team Metrics panel in Setup → Workspace management shows team-level visibility: total assets across the team, how many have been shared, how often shared assets are being copied, a reuse multiplier, the most-reused shared assets by copy count, and a 30-day activity timeline showing shares and copies per day. Per-member breakdowns are not shown — sharing should feel safe, not measured.

Data Portability

Export your entire workspace as a JSON file for backup or migration. Go to Setup → Data portability.

• What’s exported: All assets, lineage edges, stakeholders, use cases (with objectives, progress measurements, baseline/current/target values, priorities, effort estimates, target dates, and communication logs), saved AI recommendations, and action plans.
• Import: Import a previously exported JSON into any workspace. Data is merged — existing items are updated by matching on path (assets) or title (use cases), new items are added. Nothing is deleted during import.
• Plan limits on import: If the import would push your workspace over its plan’s asset limit (300 for Solo, 2,000 for Team), the import is rejected before any changes are made. The error message shows how many assets you’re importing vs. your cap.
• Lineage: Lineage edges are imported directly and do not require a manual rebuild.
• Plan field: The export includes your plan for reference, but importing does not change the destination workspace’s plan.

Privacy

The Connector sends only file metadata to your workspace — never file contents. Your files stay on your machine. Cloud source connectors read only the asset catalog information exposed by each platform's API — never the underlying data.

MyDataWork never reads, copies, stores, or transmits the contents of your files. Only names, paths, types, sizes, and modification dates are collected. All AI features — including the Asset Estate Assessment, Workspace Agent, Leverage analyses, and the in-app assistant — send only asset metadata (names, paths, tool types, topic tags, lineage edges) and use case text (titles, objectives, descriptions, value figures, stakeholder names) to the AI model. File contents are never sent.

Demo data is fully synthetic. Loading demo from the wizard, the Setup tab’s “Load demo data” button, or the Dashboard’s empty-state button creates fabricated workspace data (assets, use cases, lineage) for exploration. It carries no real customer information and can be removed any time from Setup → Connect your data with no impact on the rest of your workspace.

Value quality and robust statistics

MyDataWork includes lightweight statistical checks designed to help you present use case values you can stand behind in stakeholder conversations.

• Per-field outlier detection: When a use case's estimated or realized value is significantly higher or lower than your other use cases — measured using median absolute deviation, a standard robust statistics method — a small amber prompt appears below the field asking you to confirm the figure. This requires at least 4 use cases with non-zero values to activate.
• Portfolio value distribution: In the Portfolio tab, a Value distribution section shows both the mean and median realized value across your selected use cases. When mean and median diverge significantly, it signals that one use case may be disproportionately affecting your portfolio total. This requires at least 3 use cases with non-zero realized values.
• Leverage selection hints: When selecting use cases for AI analysis in the Leverage tab, informational notes appear if any selected use case has no baseline recorded or if progress has exceeded its original target. These are prompts to review your data before generating — they do not block analysis.
• These checks are always on — no configuration needed. They appear contextually when the data warrants it and stay silent when everything looks consistent.

This approach is inspired by robust statistics, a field concerned with producing reliable estimates even when data contains outliers or errors.

Jira integration

MyDataWork can push use case summaries to Jira as new issues or comments on existing issues. This is useful when your organization uses Jira for project tracking and you need to keep it updated without maintaining two separate records.

• Setup: Go to Setup → Integrations. Enter your Jira instance URL (e.g. https://yourcompany.atlassian.net) and your API token. For Jira Cloud, use email:api_token format. For Jira Data Center, use a Personal Access Token.
• Pushing a use case: Open any use case, click the Overview tab, and click Send to Jira. Enter your Jira project key and optionally an existing issue key to update. Leave the issue key blank to create a new issue.
• What gets sent: Use case title and status, objective and progress percentage, estimated and realized value, stakeholder names, linked asset names and types, and a direct link back to your MyDataWork workspace.
• One-way only: MyDataWork sends to Jira. Jira does not write back to MyDataWork. Your MyDataWork workspace remains the source of truth.

Mobile access

MyDataWork works in mobile browsers with no app download needed. Once your desktop is set up, you can manage your portfolio from any device.

• What works on mobile: View your asset portfolio, browse asset details and lineage, track use case progress, update metrics, export portfolio as PowerPoint or PDF, review documentation, and use the AI assistant.
• Desktop only: Connector installation and setup, asset discovery scans, file system browsing, and advanced configuration all require a Windows desktop.
• Supported browsers: Safari (iOS 14+), Chrome (Android 10+), Edge Mobile, and Firefox Mobile.
• Tips: Use landscape mode for detailed views. Bookmark your workspace for quick access. Once your desktop connector is running, all discovered assets are available on mobile automatically.

Plans & Subscriptions

Question	Answer
What plans are available?	MyDataWork offers a free Explorer plan and four paid plans. The Explorer plan is a 90-day free trial with no credit card required — 1 seat, 30 user-added assets, 3 AI credits per day with a 60-credit total cap. The paid plans are Solo Monthly ($20/month, 1 seat, 300 assets, 5 credits/day), Solo Annual ($192/year, same caps as Solo Monthly), Team Starter ($900/year, 2-5 seats, 2,000 assets, 20 credits/day), and Team Growth ($1,440/year, 6-10 seats, same caps as Team Starter). Paid plans include a 14-day free trial. Visit mydatawork.com or go to Account → View plans & billing for current pricing and plan details.
How do I upgrade?	Go to Account → View plans & billing, or visit /app/billing. Click Start free trial on any plan to begin.
How do I cancel?	Go to Account → View plans & billing → Manage billing. Monthly Solo plans continue until end of period. Annual plans are non-refundable. Canceling is different from deleting — see below.
What happens to my data if I cancel?	Your workspace data is retained for 30 days after cancellation. You can resubscribe during this period and resume where you left off. Contact contact@mydatawork.com to export during this period. This is different from account deletion, which removes all data immediately.
What’s the difference between canceling and deleting?	Canceling your subscription stops future charges but keeps your data for 30 days — you can resubscribe and pick up where you left off. Deleting your account permanently removes your account, workspace, and all data immediately with no recovery option. If you just want to stop paying, cancel your subscription — don’t delete your account.
Annual plan refunds on deletion?	Annual plans are non-refundable. If you delete your account mid-cycle, your subscription is canceled immediately and any remaining prepaid time is forfeited.
How do I add team members?	As the workspace admin, go to Setup → Members. Enter the team member's name, email, and a starter password. Share credentials with them directly. They should change their password on first login.

Troubleshooting

Problem	Solution
Setup file does not open on Windows	Right-click the downloaded .exe and choose Run as administrator. If Windows shows a security warning, click More info then Run anyway.
No files appear after setup	Wait 30–60 seconds and refresh. The first scan can take up to a minute for large folders. Make sure you selected the correct top-level folder during setup.
'Another process is running' error	The Connector is already running from a previous install. The new installer will stop it automatically — click Next to continue.
Open file does not work	The Connector must be running in the background. Check Task Manager. If not found, go to Setup and reconnect your folders.
I need to add or change a folder	Go to Setup → click Connect folders. You can update your folder selection at any time without reinstalling the Connector.
"Connect folders" shows an error / the Connector is serving another workspace	A single Connector installation can serve multiple workspaces. Go to Setup → Connect Data, find the right-side Connector panel, and click Add this workspace to Connector. The Connector adds this workspace to its config and starts scanning here too — no reinstall needed. Once added, try Connect folders again.
I forgot my password	On the login page, click Forgot password? and enter your email. A reset link will be sent — it expires after 60 minutes.
I need to upgrade or manage my subscription	Go to Account → View plans & billing to start a free trial, upgrade, or manage your subscription.
Cloud source not syncing	Check that your API token has the correct permissions (repo read for GitHub, API access for dbt/Databricks). Click Scan now in Setup → Cloud Sources to trigger a fresh sync.
AI features not working	Go to Setup → AI Assist and confirm AI is enabled (status shows "enabled" in teal). If disabled, click Enable AI. Also confirm your daily quota has not been reached — usage is shown in the same section.
Automation candidates or marketplace recommendations not generating	Confirm AI is enabled in Setup → AI Assist. For marketplace recommendations, also confirm you have selected at least one cloud provider in Setup → Cloud Providers.
I shared an automation opportunity but want to share it again	Previously generated opportunities are saved in the archive section of the Leverage tab under "Identify automation candidates." Expand any past opportunity and use the Share button to send it again.
External dependencies not showing in lineage	Enable the "Show external dependencies" toggle above the lineage visualization in the Lineage tab or above the lineage preview in the Assets tab. The two toggles are independent — enabling one does not affect the other. Both default to off.
Ghost nodes not appearing in exported lineage diagrams	In the Portfolio tab export section, check the "Include external dependencies in lineage" checkbox before clicking Export now. This option defaults to off to keep standard exports clean.
Migration Assist returns no results or an error	Confirm AI is enabled in Setup → AI Assist and that your daily quota has not been reached. If analyzing a use case, ensure at least one asset is linked to that use case — Migration Assist needs asset tool type information to generate recommendations.
'Connector not found' on mobile	This is expected. Connectors only run on Windows desktop. You can still view all previously discovered assets, manage use cases, and export from mobile. Set up the Connector on a desktop first.
Small text or buttons on phone	Use landscape mode or a tablet for a better experience. MyDataWork is optimized for touch interfaces but detailed views work best in landscape.
How do I delete my account?	Go to Account settings and click “Delete my account” at the bottom. The deletion dialog includes an optional feedback form (reason and comments), then requires a confirmation checkbox. Your account and all workspace data will be deleted immediately and permanently — this cannot be undone. Active subscriptions are canceled automatically. Annual plans are non-refundable and remaining prepaid time is forfeited. Team admins must transfer ownership or remove all members first. Super-admin accounts cannot be self-deleted. After deletion you are redirected to the login page with a confirmation message.
Send to Jira button is grayed out	Jira has not been configured yet. Go to Setup → Integrations, enter your Jira instance URL and API token, and click Connect. Once connected the button becomes active on all use case Overview tabs.
Jira push fails or shows an error	Check that your Jira API token has permission to create issues and add comments in the target project. For Jira Cloud use email:api_token format. For Jira Data Center use a Personal Access Token. Verify your instance URL includes https:// and has no trailing slash.
I don't see the value quality checks or Portfolio distribution section	These features require a minimum number of use cases with non-zero values to activate — at least 4 for the per-field outlier hints and at least 3 for the Portfolio value distribution summary. With fewer use cases the checks run silently to avoid false positives. Add more use cases with estimated and realized values to see these features.
‘Rate limit exceeded’ message	Some actions have daily or hourly limits to ensure system reliability: lineage rebuilds (5 per day), Jira pushes (20 per hour), exports (10 per day). Wait for the limit to reset or contact support if you need higher limits.

Download the Connector

The Windows Connector is required only for local file folders. Cloud sources (GitHub, dbt, Databricks, Snowflake) do not require the Connector.

Download Connector for Windows

Still stuck? Email contact@mydatawork.com. We aim to respond within 2 business days.