--- title: Salesforce Tasks & EYDN.app Intro — 2026-04-05 type: article created: '2026-04-05' updated: '2026-04-05' source_docs: - raw/2026-03-19-quarra-sf-work-131352190.md tags: - meeting - salesforce - quarra - permissions - eydn-app - client-work - api layer: 2 client_source: Quarra Stone industry_context: b2b-services transferable: false --- # Salesforce Tasks & EYDN.app Intro — 2026-04-05 ## Overview Working session between Mark Hope and Karly Oykhman to knock out pending Salesforce configuration tasks for [[wiki/clients/current/quarra/index|Quarra]] ahead of an upcoming client call with Lincoln Durham. The session also served as Karly's introduction to the new [[wiki/projects/eydn-app/index|EYDN.app]] wedding planner project. **Attendees:** Mark Hope (mark.hope@asymmetric.pro), Karly Oykhman (karly.oykhman@asymmetric.pro) --- ## Key Decisions - **Permission recommendations framed as AI-generated** — To avoid Lincoln feeling personally targeted by the admin downgrade suggestion, the documents will be presented as AI-generated recommendations rather than Asymmetric's direct opinion. - **Task Details field created via API** — The standard Salesforce UI does not expose a "New" button for the Task object's Fields & Relationships view; API was used as the workaround. - **Lincoln's admin profile should be downgraded** — AI analysis flagged Lincoln Durham (Director of Sales) holding System Administrator access as a security risk. Recommendation is to move him to the `Core Executive` profile. --- ## Work Completed ### 1. Opportunity `Primary Contact` Lookup Field **Requirement:** Add a lookup field on the Opportunity object linking to a main point of contact. **Steps taken:** 1. Created a `Lookup Relationship` field on the Opportunity object, related object set to Contact, field label `Primary Contact`. 2. Added the field to the **Opportunity Page Layout** (classic layout editor). 3. Added the field to the **Lightning App Builder** layout for the Opportunity record page. 4. Added the field to the **Opportunity Compact Layout** so it appears in the new opportunity creation modal. **Result:** Field is live and visible both on the Opportunity record and in the creation modal. Not marked required (Lincoln did not request this). --- ### 2. Task `Details` Long Text Field **Requirement:** Add a free-text details/notes field to the Task object. **Challenge:** The Task object does not display a "New" button in the Fields & Relationships UI — a known Salesforce quirk for Activity-based objects. Additionally, `Long Text Area` field type is not valid on Activity objects directly. **Resolution:** 1. Field created via API (appropriate text area type for Activity objects). 2. Field was initially hidden from all profiles due to a field-level security issue created at deploy time. 3. Mark corrected field-level security via API. 4. Field added to the Task Page Layout manually. 5. Hard refresh (Ctrl+Shift+R) confirmed field now visible on Task records. **Remaining step:** Add `Details` to the **Task Compact Layout** so it appears in the task creation modal. Mark will handle via API; instructions also pasted into meeting chat for Karly's reference. --- ### 3. Permission Set Analysis **Requirement:** Analyze Quarra's current Salesforce permission structure and provide recommendations. **Process:** - Mark used an AI assistant (via API connection to the Quarra org) to pull all permission-related data. - Two documents generated and saved to the Quarra shared drive under `Projects > Salesforce`: | Document | Contents | |---|---| | `QR Quaristone Salesforce Permissions` | Current permission structure summary — profiles, permission sets, validation rules | | `QR Quaristone Salesforce Permissions Recommendations` | AI-suggested changes | **Key recommendation — Lincoln Durham:** > Lincoln is a Director of Sales but holds full System Administrator access. He can modify metadata, delete any record, change automation, install packages, etc. Recommendation: move to `Core Executive` profile. One accidental click in Setup can break flows, validation rules, or field mappings org-wide. **Client strategy:** Present both documents to Lincoln as AI-generated output. Frame as "here's what the AI recommends — you don't have to agree with all of it, but let's walk through it together." Use the next call to gather his preferences verbally, then implement via API. **Also noted:** Jessica (Mark's daughter) is still an active user in the Quarra org and should be deactivated. --- ## New Project: EYDN.app Wedding Planner Mark introduced Karly to [EYDN.app](https://eydn.app) — a new wedding planning application he built. The app is functional but has not been reviewed for bugs or styled. **Current features:** - Wedding setup wizard - Smart task timeline (50 auto-generated tasks) - Budget tracker - Guest list with RSVP and meal preference tracking - Vendor tracker (13 vendor categories, status pipeline) - Seating chart with drag-and-drop guest assignment - AI assistant chat **Known bug identified during session:** "Edit table" button on the seating chart does not function. **Karly's assignments:** 1. **QA testing** — Go through the full app, compile a list of bugs, broken features, and feature requests. 2. **Brand guide** — Use Claude to generate a brand guide (logo, colors, fonts) based on the app's description. Send the selected guide to Mark for implementation. --- ## Action Items - [ ] Email Lincoln the permissions summary + AI recommendations documents; note the admin downgrade suggestion is AI-generated (@Karly Oykhman) - [ ] Deactivate Jessica's user account in the Quarra Salesforce org (@Karly Oykhman) - [ ] Review EYDN.app end-to-end; compile bug list and feature feedback for Mark (@Karly Oykhman) - [ ] Generate EYDN.app brand guide (logo, colors, fonts) via Claude; send to Mark (@Karly Oykhman) - [ ] Add Task `Details` field to the Task Compact Layout via API; confirm modal visibility (@Mark Hope) - [ ] Fix EYDN.app seating chart "Edit table" bug (@Mark Hope) - [ ] Implement brand guide in EYDN.app once received from Karly (@Mark Hope) --- ## Next Client Call Notes For the upcoming call with Lincoln, Mark's suggested approach: - Walk through the permissions documents together live. - Don't try to capture everything in writing during the call — let Lincoln talk through what he wants, capture via Fathom transcript, then feed to Claude Code for implementation. --- ## Related - [[wiki/clients/current/quarra/index|Quarra Client Index]] - [[wiki/projects/eydn-app/index|EYDN.app Project]]