Sources
A source selects an acquisition method, output profile, destination, and owning workstation/account. Only enabled sources owned by the current Windows machine and user run.
| Option | Default | Accepted values | Behavior |
|---|---|---|---|
id |
required | 1-64 letters, digits, _ or - | Stable source identifier |
acquisition |
required | Folder, Scanner | Source acquisition method |
profileId |
required | Existing profile ID | Exact case-sensitive profile reference |
destinationId |
required | Existing destination ID | Exact case-sensitive destination reference |
folder |
null | Absolute path or null | Required for Folder; not used for Scanner |
completion |
StableFile | AtomicHandoff, ReadyMarker, StableFile | Folder producer-completion contract |
stableSeconds |
10 | Integer >= 1 | Quiet period for StableFile; validated even for other modes |
ownerMachine |
null | Machine name or null | Required when enabled; compared ignoring case |
ownerUser |
null | Windows account name or null | Required when enabled; compared ignoring case |
enabled |
false | true, false | Opt-in to workflow execution |
readLocalAudit |
false | true, false | For folder sources, attempt to identify a local file writer from existing Windows Security audit records; requires permission to read the log |
Workstation and user ownership
Use the workstation's Windows machine name and the operator's resolved identity, for example EXAMPLE-PC and EXAMPLE\Operator. Confirm the values in the actual account's session. Installation as SYSTEM does not transfer SYSTEM's share permissions to the operator.
A shared fleet deployment can include multiple distinct source assignments. Every path still has to pass policy validation on the endpoint, and roots may not overlap. Prefer narrowly scoped per-workstation policy where a large common policy would introduce irrelevant paths or ownership mistakes.
Scanner and folder differences
Scanner sources appear as selectable workflows in Capture. Device selection and source/DPI/color/page-size controls are user-local scanner preferences, not fields in this source policy. Managed profiles standardize the output policy; this version does not centrally lock every vendor scanner setting.
Folder sources are polled only at the top level. completion and stableSeconds are meaningful for folder processing; they do not control scanning. See Folder intake for producer responsibilities and ready-marker contents.
Optional file-writer information
readLocalAudit is off by default. When enabled for a folder source, Paperweight looks for recent matching file-write events in the workstation's Windows Security log. It does not enable auditing or grant log access. Your administrator must already have configured suitable audit coverage and access.
A match is evidence of an account that wrote the file, not proof of who scanned or originally created it. Missing, inaccessible, or conflicting records leave the writer unknown and do not stop document processing. Network shares require evidence from the file server; this preview does not collect it. Keep this setting disabled unless your organization needs the information and has approved the required access.
Note
Changing ownership or enabling a source does not migrate another user's retained jobs. Preserve local state and coordinate the change to avoid competing consumers or duplicate downstream delivery.