Quarra Stone — Opportunity Teams Configuration
Overview
Salesforce Opportunity Teams was enabled for Quarra Stone as part of a broader Salesforce buildout managed by [1]. The feature allows internal Salesforce users to be formally associated with specific opportunities, and is being extended to explore access for external partners such as architects.
Implementation is handled by [2] (Sergei Logvin).
Feature Enablement
Opportunity Teams was enabled in the Quarra Stone Salesforce org during the September 2025 working session. No role-based restrictions were applied at enablement — any licensed Salesforce user can be added to an Opportunity Team regardless of their role in the system.
External Partner Access
Use Case
Quarra Stone works with external parties (e.g., architects) who are not Salesforce licensees but may need to be associated with an opportunity and receive notifications as work progresses.
Proposed Approach
Rather than purchasing additional full licenses, the proposed solution is to create guest users in Salesforce for external partners. This would allow:
- External stakeholders to be added to Opportunity Teams
- Notifications to be routed to them when relevant events occur
- Visibility into team membership without granting full system access
Status
As of the 2025-09-29 call, Sergei (Twistellar) was tasked with researching the guest user approach and confirming feasibility. No implementation has occurred yet.
Action Item (open): Sergei Logvin to research adding external users (e.g. architects) to Opportunity Teams via guest user option in Salesforce.
Configuration Notes
| Setting | Value |
|---|---|
| Feature | Opportunity Teams |
| Enabled | Yes (2025-09-29) |
| Role restriction | None — any Salesforce user eligible |
| External access | Under investigation (guest user model) |
| Implementer | Twistellar (Sergei Logvin) |
Related Articles
- [3]
- [4]
- [5]
- [6]
Source
Discussed during the [7] with Mark Hope, Karly Oykhman (Asymmetric), and Sergei Logvin (Twistellar).