Define the source categories
List documents, workbook sheets, recording segments and system objects, with the owner, purpose and access permissions.
Data & access
Begin with the material in scope and the people who need it. Use this guide to turn your requirements into questions that can be checked against the service and your configuration.
01 / Before material enters
A narrow first project needs enough context to be useful. It rarely needs an unrestricted copy of every system.
List documents, workbook sheets, recording segments and system objects, with the owner, purpose and access permissions.
Remove unneeded identifiers and confidential fields first. The in-browser redaction tool is one local option; inspect its output.
Record what the sample represents, its period and known omissions. A clean example without its limits creates false confidence.
02 / People and permissions
The table below is an evaluation worksheet, not a promise that every role or control is available in every configuration.
| Participant | Discuss their access | Evidence to inspect |
|---|---|---|
| Workspace administrator | Membership, organization settings and project access. | Configured roles and the actual view available to each participant. |
| Analyst or practitioner | Sources, findings, modeling and draft outputs. | Relevant project scope and permitted editing actions. |
| Reviewer or decision owner | Evidence inspection, comments and approval. | The review workflow and the version attached to a decision. |
| Client or external recipient | The intended published material. | Eligible sharing method, selected audience and access removal. |
| Build operator | Repository, runner and release responsibilities. | Build roles, provider credentials, policy, required checks and approval scope. |
03 / Processing and AI
Application hosting, file storage, AI processing and customer-configured connections are different parts of the review.
Which parts of a source or project can be sent for analysis? Which provider handles the feature, and on what processing terms?
Which masking or privacy settings are active? What remains detectable, and what must the team remove first?
What are the lifecycles for original files, extracted content, outputs, operational records and backups?
Which formats are available? Who receives the export, how is completeness checked, and what happens to access at the end?
For published service facts, use the Security & data page and Privacy Policy. Confirm requirements that need a contractual commitment before providing sensitive material.
Review your requirements
Send the source categories, roles and processing requirements you need settled. We’ll go through them with your security or data owner and point to the published facts behind each answer.

Allow optional analytics to help us improve ProcessScout? Privacy notice