Administer FactVerse Scout
Scout is included with DFS Pro. Platform administrators make the purchased capabilities available to a tenant, and tenant administrators activate the permitted modules and assign user access.
Required Inputs and Tenant Preparation
Before enablement, confirm:
- the customer tenant and purchased DFS Pro capabilities
- the authorized data sources, equipment and model scope
- the people responsible for operation, domain review, approval and release
- the approved model service and data-processing policy
- support owners for sources, models, data and applications
Browser users sign in through the FactVerse platform. API and MCP credentials are configured separately for approved integrations; see Integrate Scout.
Enable Scout
- Make DFS Pro and Scout available to the customer tenant.
- Activate the permitted capabilities for that tenant.
- Assign responsibilities using the tenant's role model.
- Confirm that authorized sources, equipment attributes and models are selectable.
- Configure the platform model service for Scout analysis.
- Test access with representative viewer, operator, reviewer and release accounts.
Menu visibility confirms discovery of the module. Validate each required read, write, review and release action with the intended account.
Assign Responsibilities
| Responsibility | Required access |
|---|---|
| View tasks and evidence | Scout read |
| Create tasks, discover sources and propose changes | Scout write plus access to selected sources and assets |
| Resolve equipment identity | Relevant MDM read and review access |
| Inspect model fields | Model read, MDM read and DFS source read |
| Review and apply model proposals to a draft | Scout approval, model write and MDM read |
| Approve a dataset or semantic release | Release approval |
| Apply or restore a semantic release | Scout deployment, model write and DFS source write |
These rows describe responsibilities and can be mapped to the customer's existing roles. Use least-privilege access. Dataset and semantic releases require separate authorized people for approval and application.
Configure AI Analysis
Scout uses the platform AI service and a model endpoint that supports its structured analysis responses. Configure the endpoint, model name, adapter and provider credentials through the approved platform administration process.
Verify from the running application environment:
- Network and TLS access to the configured route.
- Successful authentication with the service credential.
- A complete Scout analysis response using permitted test data.
- A clear error in the task when the service is unavailable.
Private deployments have additional network and data-boundary considerations; see Deploy Scout in a Private Environment.
Verify Enablement
- A viewer can open tasks and evidence but cannot change them.
- An operator can create a task and read only authorized sources.
- An MDM or domain reviewer can resolve the intended decisions.
- An approver can inspect the exact release plan.
- A different release operator can apply the approved plan.
- Unauthorized tenants, sources and actions remain inaccessible.
- A small Scout investigation returns a usable analysis or a specific clarification request.
Exploration can begin from an authorized source. Business-readiness and dataset-onboarding tasks also use the corresponding published business requirements.
Change or Remove Access
Review active bindings, subscriptions, datasets and pending approvals before changing user or tenant access. Assign an owner for any required runtime cleanup and verify the result through the supported workflow. Keep task and release history available to authorized reviewers according to the customer's retention policy.
Use Troubleshoot and Accept Scout for the go-live check and hand over the source, model-service, data, model and application support contacts.