--- title: Salesforce Updates Call — Quarra Stone (2025-09-29) type: article created: '2025-09-29' updated: '2025-09-29' source_docs: - raw/2025-09-29-call-w-twistellar-quarra-salesforce-90463130.md tags: - meeting - salesforce - quarra-stone - twistellar - automation - sharepoint - prospect-numbers - opportunity-teams layer: 2 client_source: Quarra Stone industry_context: b2b-services transferable: false --- # Salesforce Updates Call — Quarra Stone (2025-09-29) Working session with Twistellar (Sergei Logvin) to address urgent Salesforce issues for Quarra Stone and plan next steps for SharePoint folder automation. ## Attendees - **Mark Hope** — Asymmetric (mark.hope@asymmetric.pro) - **Karly Oykhman** — Asymmetric, account manager (karly.oykhman@asymmetric.pro) - **Sergei Logvin** — Twistellar, external dev lead (s_logvin@twistellar.com) ## Overview Two urgent issues were escalated by the client (Stephen Rousseau, standing in for Lincoln who is on vacation in Hawaii): only Lincoln could create opportunities due to a permission restriction, and the lead section was not generating prospect numbers. The call resolved the immediate plan for both fixes and deferred the SharePoint folder automation to a Friday client call. ## Key Decisions ### 1. Remove Opportunity-Creation Restriction (Urgent) A permission had been set allowing only Lincoln to create opportunities. This is to be disabled immediately so all users can create opportunities again. Sergei flagged this as an urgent task for his team. ### 2. Auto-Generating Prospect Numbers on Leads The prospect number field currently exists on the **opportunity** object but was being populated manually (likely from a spreadsheet). The agreed approach: - Add a new **"Prospect Number"** field to the **lead object** - Auto-generate on lead creation: sequential, unique, non-editable - Starting value: **P21150** (last known opportunity prospect number was P21138; gap added for safety) - On lead conversion, **map the prospect number to the corresponding opportunity field** - Leads that are never converted will consume a number — this is acceptable > *"We want here at this moment in the lead, when we have a lead, we want to go ahead and create a prospect number for the lead... when the lead is converted to an opportunity, we want that prospect number to go over as one of the fields that's mapped to the opportunity."* — Mark Hope ### 3. SharePoint Folder Automation — Deferred to Friday The client currently creates folders in SharePoint manually, naming them using the prospect number (plus some portion of the client/project name). The desired end state is automatic folder creation triggered by opportunity creation (or possibly lead creation — to be confirmed). Three technical options under consideration: 1. SharePoint connector from Salesforce 2. Folders created natively within Salesforce (Dimitri's suggestion) 3. Linux VM or Node.js web app as middleware The preferred approach will be discussed with the client on Friday. Asymmetric does not have a strong preference on the bridge mechanism — what matters is the folder ending up in the right place with the right name. > *"I don't think we really care what process, what the bridge is between needing the folder and having the folder. What really matters is that we end up with a folder in the place they want it, with the name on it that they want."* — Mark Hope Sergei noted a possible nuance from a prior call recording: there may be **two folder-creation triggers** — one at lead creation and one at opportunity conversion. This needs to be confirmed with the client. ### 4. Opportunity Teams — Enabled Opportunity Teams feature has been enabled. Any Salesforce user can be added to a team regardless of role. Open question: whether external partners (e.g., architects) can be added as **guest users** without requiring a full Salesforce license. Sergei to research. ### 5. Additional In-Progress Tasks - Creating two new user accounts as requested - Renaming field **"Primary Stone Type" → "Primary Material Type"** and adding a new picklist value on the lead object ## Action Items - [ ] **Sergei Logvin** — Add "Prospect Number" field to lead object: auto-generated, unique, non-editable, starting at P21150. Map to opportunity on lead conversion. Mark as urgent. - [ ] **Sergei Logvin** — Remove opportunity-creation restriction (Lincoln-only permission). Flag as urgent for team to implement ASAP. - [ ] **Karly Oykhman** — Contact Stephen Rousseau re: Friday call at 11am ET. Inform him of the two immediate fixes (opp creation + prospect number automation). Request his attendance to discuss folder creation workflow. - [ ] **Sergei Logvin** — Research adding external users (e.g., architects) to Opportunity Teams via guest user option in Salesforce. ## Open Questions - **Folder creation trigger:** Does the folder get created at lead creation, opportunity creation, or both? Confirm with Stephen on Friday. - **Folder naming convention:** Prospect number + what else? Client to clarify. - **Folder location:** SharePoint path/directory where folders should be created — client to provide API credentials or access details. - **External guest users in Opportunity Teams:** Is a guest user license required, or is there a lighter-weight option? ## Related - [[clients/current/quarra/_index]] — Quarra Stone client overview - [[clients/current/quarra/sharepoint-folder-automation]] — Folder automation scoping (to be created after Friday call)