Skip to content
Request a demonstration

AutoDiscover

AutoDiscover from a folder you approve

Nobody has time to organise years of files before they can benefit from any tool.

Demonstration: Calder & Rowe Manufacturing (fictional) · Manufacturing. Fictional data and a scripted answer.

The situation

Organisation
Calder & Rowe Manufacturing (fictional)
Who is asking
Head of IT
Industry
Manufacturing
What happened
The company wants its procedures and drawings found across shared drives, without the platform ever seeing HR or finance folders.

The question asked

Which shared folders should the platform be allowed to read, and which must stay out of reach?

What it reads, and who can see the result

  • Folder inventory (names and counts) registerFolder names, locations and file counts; not file contents.
Reads
Only the folders the head of IT approves, in read-only mode, after the choice is recorded.
Does not read
Any folder not approved, and nothing is written, moved or deleted.
Permission
A read-only service account created by IT for the approved folders only.
Who sees it
The head of IT and the owners of each approved folder.

Try it

Choose what the platform may read. Restricted material cannot be put in scope here, and a classification the analysis is unsure of must be verified by a person.

Read it?SourceHoldsSensitivityWhat the analysis thinks it is
Operations / Procedures
Shared drive O:
1,840 filesinternalOperating procedures clear
Quality / Audits
Shared drive Q:
920 filesinternalAudit reports and corrective actions check
HR / Personnel
Shared drive H:
6,400 filesrestrictedPersonnel files clear
Finance / Payroll
Shared drive F:
3,100 filesrestrictedPayroll records clear
Engineering / Drawings
Shared drive E:
12,600 filesinternalTechnical drawings check
Sales / Quotes
Shared drive S:
2,300 filesinternalCustomer quotations clear
Legal / Matters
Shared drive L:
2,750 filesrestrictedPrivileged legal files clear

Sources in scope
0 of 7
files in scope
0
Restricted, kept out
3 sources
To verify
0

The answer

Simulated answer. Written for this fictional case, not produced by a live model. Only the figures in it are computed, from what you decided above.

0 of 7 folders are approved for reading, 0 files.

Discovery starts from an inventory of folder names and counts, not contents [S1]. Three folders are restricted by the classification policy (personnel, payroll and privileged legal files) and cannot be added here; they stay out of reach unless their owners grant an exception through their own process [S2].

Two classifications are uncertain (audit reports and drawings) and a person must verify them before the scope is final: 0 included folder(s) still need that check. Nothing is read until the scope is approved.

Relies on: S1 · Folder inventory, shared drivesS2 · Data classification policy

Review and approval

The head of IT with the folder owners decides. Approving creates a read-only access grant for exactly the folders in scope. It does not read, move, change or delete any file, and does not widen to any other folder.

Not ready to approve. Choose at least one source to read first.

In the product this is a different person with the right permission. Here you play that role to see the rule.

What it produces

registerDraft, not approved

Approved scope

  • 0 folders, 0 files, read-only.
  • 3 restricted folders recorded as out of scope.
evidenceDraft, not approved

Scoping decision

  • Who approved, which folders and which classifications a person verified.

Limits of this example

  • The inventory is names and counts; a mislabelled folder is only as visible as its name.
  • Read-only access can be revoked by IT at any time.
  • This is a scripted demonstration on fictional data. No model was called and no real organisation, person or result is shown.