Use the reference section when a DFS workflow needs exact configuration, access, or integration details. Start with the task guide or recipe first, then use these pages to confirm fields, permissions, and endpoint families.
Reference lookup flow
Reference pages
| Page | Use |
|---|
| Connector Types | Choose the right source connector for files, APIs, databases, IoT streams, industrial protocols, and facility systems. |
| Mapping Fields | Check the fields used when mapping source paths to assets, points, dataset fields, work records, or other operational targets. |
| Permissions | Confirm the DFS read, write, delete, BI, and governance permissions needed for an operator, reviewer, or integration. |
| API Surface | Plan API-level integrations around DFS Lite connectors, DFS Pro datasets, fusion tasks, review queues, pipelines, audit, and BI. |
Common lookup paths
| Question | Start here |
|---|
| Which connector should I use for this source? | Connector Types |
| Which fields must be reviewed before saving a mapping? | Mapping Fields |
| Why can a user see a dataset but not validate it? | Permissions |
| Which endpoint family supports a planned automation? | API Surface |
Related workflow pages
| Page | Use |
|---|
| DFS Lite Connectors | Operate connector lifecycle before checking connector reference details. |
| Mapping Source Fields | Build and review mappings before checking mapping field definitions. |
| DFS Pro Datasets | Create governed datasets before planning dataset-level API integrations. |
| Review Queue | Review uncertain records before automating review actions. |
Validation use
Use reference pages to confirm a specific choice before implementation or review: connector type, required fields, permission boundary, endpoint family, and downstream impact. The reference pages should support a workflow decision, not replace the workflow review.
Review checklist
| Check | Why it matters |
|---|
| Connector type matches the source | Avoids selecting a connector family that cannot represent the source protocol, update pattern, or payload shape. |
| Mapping fields are complete | Keeps target identity, timestamp, unit, transform, and confidence review visible before sync or dataset creation. |
| Permission boundary is clear | Separates operators who can read or run sync from stewards who can validate, delete, govern, or publish outputs. |
| API surface matches the task | Prevents an integration from calling a low-level endpoint when a governed workflow or review queue is required. |
| Reference decision is linked back | Keeps task pages, recipes, and run records aligned with the configuration choice. |
When to return to a workflow
After checking a reference page, return to the workflow or recipe that created the question. The implementation record should mention which reference decision was used and who accepted it. This is especially important for permissions, connector selection, mapping fields, and API-level integrations because those choices affect downstream review, audit, and support.