Project-first workflow
Open a metadata ZIP or supported project folder, then index metadata for Flow, dependency, permission, deployment, and report analysis.
Local-first Salesforce workbench
Open a project to begin
Analyze local Salesforce metadata, Flow XML, Apex, package files, and project exports in your browser.
Local-first notice
Console by OzCrypt analyses local Salesforce files in your browser. It does not connect to your Salesforce org and does not upload your metadata.
How this workflow works
- Open one Salesforce project in Workspace mode.
- Use Tool Library to discover tools.
- Use context actions from object/field/file rows for targeted prefills.
- Use standalone tools for independent or shareable tasks.
Quick tips
- Project Context is the shared local index/schema/selection used by workspace tools.
- Standalone routes intentionally do not inherit workspace project context.
- Metadata-aware suggestions come from locally indexed metadata only.
- Analysis is best-effort for partial or unknown metadata shapes.
Use Role mode to prioritize workflows for Developer, Architect, Tester, Consultant, Client/Business, Release/CAB, or Support. It changes recommendations, not project data.
Workspace mode uses opened project context. Standalone tool routes support upload/paste/manual input for quick tasks.
Your metadata stays in this browser. Console by OzCrypt does not upload files or log in to Salesforce.
Project already opened
Use Project Dashboard for goal-based next steps, then run tool-specific analysis from Explorer or Project Index selections.
Local browser tools
No Salesforce login
No upload
Static analysis boundary
Analysis is based on local metadata files. It helps with review, but does not replace Salesforce validation, tests, security review, or runtime permission checks.
Import Wizard
Choose Salesforce metadata to index
Open a Salesforce DX project root, metadata folder, ZIP, or selected metadata files. Console by OzCrypt only reads what you choose in this browser.
Ready to import
Select the folder that contains sfdx-project.json when possible. If that is not available, force-app/main/default, a metadata ZIP, or selected metadata files can still be indexed for local analysis.
For real-project fixture QA, sanitize certs, credentials, tokens, sensitive endpoints, and customer-identifying content before import.
Project Index
Project Dashboard
Mode: Workspace (shared project context)
See what Console by OzCrypt detected locally, then choose your next best action.
No project opened
Use Project Dashboard or Import Wizard to build a local project index.
Open a Salesforce project folder, metadata ZIP, selected files, or use the sample project to see goal-based recommendations.
Open a project to see detected metadata coverage and common missing folders.
Open a Salesforce project folder, metadata ZIP, or selected files to build the reusable workbench index.
Select a row in Project Index to run contextual actions.
Workspace > File Preview
File PreviewPreview selected metadata
When project indexing is connected to the file tree, selected metadata previews will appear here. Uploaded files are still handled locally in the browser.
No file selected
Open a Salesforce project folder, metadata ZIP, or analyzer upload, then select a metadata file to preview it.
Run a scan to see invalid XML, missing subflows, unsupported metadata, and deployment review prompts.
Analyzer summaries and copy/download feedback appear here as modules run.
Generated Markdown, CSV, and JSON report status will appear here.
Workbench UI events stay local in memory for this preview.