Keep Client Isolation
Dedicated client locations are the clearest real ForgeFX convention. CAT, Vermeer, GE Healthcare, WMATA, CBRN-AR, EWAT, John Deere, and JLG all resolve as separate client/project sites or subsites.
Internal Research · 13 Jul 2026
SharePoint · Salesforce · Project Delivery
From Historical Sites to a Repeatable Client-Project Blueprint
A read-only evidence review of real ForgeFX SharePoint patterns—and the conventions Acme should standardize for future simulation-development projects provisioned from Salesforce.
10+ SITES VALIDATEDSLACK + TEAMS + JIRAOFFICIAL MICROSOFT GUIDANCENO LIVE SITES MODIFIED
Direct Answer
Standardize the New URL Shape
Legacy paths are inconsistent: /CAT, /TeamSite/JLG-Sim, and /sites/JohnDeere. Future sites should use modern /sites/<stable-account-alias> Team sites.
One Account, Many Projects
Internal sales explicitly asks for opportunity-level organization for large repeat clients such as John Deere and Vermeer. Use one Account site with a governed workspace per active delivery Opportunity.
Respect System Boundaries
Salesforce owns commercial identity, Jira owns execution, Slack/Teams owns conversation, and SharePoint owns the durable document, decision, deliverable, approval, meeting-artifact, and status record.
Recommended Canonical Pattern
Salesforce Account → Client Site → Opportunity Project Workspace
Account: stable client boundary and access perimeter. Opportunity: a unique delivery workspace identified by readable slug plus immutable Salesforce Opportunity ID. Lists and libraries: fixed structure, parameterized project data.
Observed Evidence
| Sample | Locator | Observed Convention | Confidence |
|---|---|---|---|
| John Deere | /sites/JohnDeere | Modern dedicated client site; collaboration home shared as project landing page; machine/module artifacts, storyboards, review folders, Jira links, and explicit approvals. | High |
| Caterpillar | /CAT | Dedicated legacy client site. The analogous /sites/Caterpillar path returns 404, proving that URL generation must account for legacy reality during migration. | High |
| Vermeer | /Vermeer | Dedicated client site; project/reference repositories and agreements can be the effective source record even when names differ from Salesforce Opportunities. | High |
| GE Healthcare | /gehc + subsites | Account-level boundary with multiple project-specific child sites—a historical signal that repeat accounts need project separation. | High |
| CBRN-AR | /sites/CBRN-AR | Dedicated project site whose equipment/module lesson content acts as programmer-facing requirements. | High |
| Halliburton | Slack production channel, 8 Jul 2026 | Phase-labeled CAD source batch used for production handoff. | High |
| Sales operations | Slack, 29 May 2026 | SharePoint described as the comprehensive access layer; opportunity folders requested for large multi-project clients. | High |
| Salesforce links | Slack + FRG-2368 context | Account and Opportunity pages expose SharePoint links. Current derivation replaces spaces in company names with hyphens; missing folders yield expected 404s. | High |
Fixed Blueprint vs Parameterized Project Data
Fixed Every Time
- Private Microsoft 365-connected Team site
- Project management template
- Home, dashboard, requirements/decisions, deliverables/reviews, issues/risks/changes, documents, status, meetings, contacts, archive
- Owners, ForgeFX members, client group; no anonymous links
- Two accountable ForgeFX owners
- Versioning, shallow taxonomy, quarterly review, closeout
- Links to Salesforce and Jira
Parameterize Per Deal
- Account and Opportunity IDs, names, slugs, and URLs
- Contract/SOW, commercial stage, delivery dates
- Project manager, sponsor, technical lead, client contacts
- Phases, milestones, modules/equipment, platforms, locales
- Jira, Slack/Teams, Fireflies, GitHub, and source links
- Classification, retention, client domains, guest decision
- Acceptance gates and archive disposition
Minimum Salesforce Mapping
| Salesforce Source | SharePoint Destination | Rule |
|---|---|---|
Account.Id | Provisioning Metadata | Immutable identity and deduplication key. |
Account.Name | Site title / client metadata | Display value; changing it must not silently rename the URL. |
Proposed SharePoint_Site_Alias__c | Site alias | Persist once after normalization. |
Proposed SharePoint_Site_URL__c | Canonical site URL | Write the actual provisioned URL back to Salesforce. |
Opportunity.Id | Project metadata | Immutable project key; pair with readable slug. |
Opportunity.Name | Project title | Human label, not sole identity. |
StageName / CloseDate | Commercial metadata | Keep separate from delivery status and milestone dates. |
Amount | Internal only or excluded | Never surface to client users by default. |
Proposed SharePoint_Project_URL__c | Canonical project URL | Write after provisioning; use for the Salesforce header link. |
Important: proposed field API names are recommendations and require direct Salesforce schema verification.
Provisioning Lifecycle
01
Qualify
Deduplicate Account, confirm Opportunity, select stable alias.
02
Authorize
Approve owner, client-access posture, and classification.
03
Provision
Create/reuse client site and opportunity workspace; record IDs.
04
Configure
Populate people, milestones, modules, links, and permissions.
05
Validate
Test roles, links, flows, rules, versioning, and notification.
06
Operate
Maintain trackers, decisions, approvals, status, and access.
07
Close
Capture acceptance, obligations, handoff, and lessons learned.
08
Archive
Remove guests, apply retention, lock where appropriate, update Salesforce.
What the Evidence Does Not Prove
No tenant-wide status cadence, retention standard, sensitivity-label policy, or uniform guest-access model was verified. The connector validated site locations and libraries but did not expose list schemas, navigation, permissions, or external-sharing configuration in this run. Caterpillar exists at /CAT; the modern-looking path does not. Treat all proposed controls as blueprint recommendations until a direct tenant configuration audit confirms them.
Source Coverage
Internal
SharePoint/Graph, Slack, Teams/Fireflies-posted context, Jira/Confluence, Outlook, Google Drive, and local ForgeFX skill/history files.
External
Official Microsoft Project management template, information architecture, governance, and inactive-site lifecycle guidance. GitHub, YouTube, X, and academic lanes were low-value for this private operational question.