Salesforce Quora Prep & EYDN.app Kickoff — 2026-03-19

Overview

Working session between Mark and Karly to knock out Salesforce to-dos ahead of an upcoming meeting with Lincoln Durham at Quorra, and to kick off a new project: testing and branding the ^[1] wedding planner.

Attendees: Mark Hope, Karly Oykhman
Client: ^[2]
Recording: Fathom

Key Decisions

• Primary Contact field will be a lookup (not required) on the Opportunity object, surfaced on both the Lightning record page and the Compact Layout (so it appears in the "New Opportunity" modal).
• Task Details field created via API as a text area; FLS must be explicitly set to visible after API creation — it defaults to hidden from all profiles.
• Permission documents will be sent to Lincoln Durham as AI-generated artifacts, framed clearly as AI recommendations rather than the team's own opinions, so he can review and decide.
• Lincoln Durham's admin profile flagged for downgrade in the recommendations doc — full System Administrator access for a Director of Sales is a security risk.
• EYDN.app branding will be generated by Karly using Claude, then handed off to Mark to apply to the app.
• Next Quorra meeting strategy: use the permission docs as a starting point, let Lincoln talk through what he wants, record with Fathom, then feed the transcript to Claude to automate implementation.

Action Items

• [ ] Email Lincoln Durham the permissions summary + AI recommendations (including the admin downgrade suggestion); request his review and decisions — @Karly
• [ ] Deactivate Jessica's user account in the Quorra Salesforce org — @Karly
• [ ] Add Task Details field to the Task Compact Layout (so it appears in the create modal) — @Karly
• [ ] Test EYDN.app end-to-end; compile a list of bugs and feature suggestions for Mark — @Karly
• [ ] Generate EYDN.app brand guide (logo, colors, fonts) via Claude; send to Mark — @Karly
• [ ] At next Quorra meeting: record with Fathom, walk through permissions with Lincoln, then use transcript + Claude to implement changes — @Mark & Karly

Salesforce Work Completed

Opportunity: Primary Contact Lookup Field

Requirement: Lincoln Durham wanted a field on Opportunity to designate a single main point of contact.

Implementation:
1. Created a Primary Contact lookup field on the Opportunity object (lookup target: Contact).
2. Added the field to the Opportunity page layout, positioned near Opportunity Owner.
3. Added the field to the Lightning record page via the App Builder (Fields tab, not Components).
4. Added the field to the Compact Layout so it appears in the "New Opportunity" quick-create modal.
- Claude surfaced this: the modal pulls from the Compact Layout, not the full page layout.

Notes:
- Field was not marked required — Lincoln did not specify that requirement.
- The traditional page layout and the Lightning record page are separate; both needed to be updated.

Task: Details Text Area Field

Requirement: Add a free-text notes field to the Task object.

Implementation:
1. Created a Details text area field on the Task object via the Salesforce API (the Task object does not expose a "New" button in the standard Object Manager UI — use Setup > Activity Custom Fields or API).
- Note: Long Text Area is not valid on Activity objects; use standard Text Area.
2. Added the field to the Task page layout.
3. Resolved a visibility issue (see Troubleshooting below).

Troubleshooting — Field Not Appearing:
- Root cause: Fields created via API default to hidden in Field-Level Security (FLS) for all profiles.
- Resolution: Manually updated FLS to make the field visible, then did a hard refresh (Ctrl+Shift+R).
- This is a known gotcha: always check FLS after creating fields via API.

Remaining: Task Details field still needs to be added to the Task Compact Layout (create modal). Left as an action item for Karly.

Permission Sets: Analysis Documents

Requirement: Define new permission sets for Quorra users. Lincoln needs to review the current state before decisions can be made.

Approach: Rather than building permission sets blind, the team used the Salesforce API + Claude to generate two documents for Lincoln to review:

Key recommendation flagged: Lincoln Durham is currently a System Administrator. As Director of Sales, this is a security risk — one accidental click in Setup could break flows, validation rules, or field mappings org-wide. Recommendation: downgrade to a Core Executive profile.

Framing guidance: Send these to Lincoln as "AI recommendations" — not the team's personal opinion — so he can evaluate and decide what he agrees with.

Both documents saved to: Shared Drive > Projects > Salesforce > Quorra Stone

Next step: At the next meeting, walk through the docs with Lincoln, let him talk through his decisions, and use the Fathom recording + Claude to automate implementation.

New Project: EYDN.app Wedding Planner

Current State

EYDN.app is a functional prototype built by Mark. Core infrastructure is in place:
- Database configured
- Auth working (email confirmation + 2FA)
- Features include: wedding setup wizard, seating chart (drag-and-drop guests to tables), guest management, status pipeline, and an in-app chat/AI assistant

The app is expected to be buggy — it was built quickly and hasn't been thoroughly tested.

Known bug found in session: "Add a Table" button on the seating chart does not work.

Karly's Tasks

1. Bug testing: Use the app as a real user would. Document every broken feature, error, or confusing behavior.
2. Feature suggestions: Brainstorm additions — graphs, calendars, dashboards, connections between objects, anything that would make it more useful.
3. Branding: Use Claude to generate a brand guide (logo concept, color palette, typography). Send the completed guide to Mark, who will apply it to the app.

Transcript Excerpts

On the permission strategy:

Mark: "If you send him this, you should just say, hey, these are the recommendations from AI, and you don't have to agree with all of them, but this is what it recommends."
Karly: "Okay. Yeah."
Mark: "You don't want him to think that we think that."
Karly: "We think that he's going to break everything, so we need to remove it."
Mark: "Yeah. Although that's probably true."

On the next meeting strategy:

Karly: "I think what I would focus on tomorrow is the permissions and just say, let's go through these together and decide what you want to do. And then what I would do is don't try to write it all down. Just say, talk me through it. What do you want? What do you want to stop? What do you want to add? What do you want to change? And then we'll just take the Fathom, and then we'll give it to Claude Code and say, implement this stuff."

On EYDN.app:

Mark: "I just tried to get it working. So the database is working. The auth, you just saw the authorization where you have to put in a code and everything. That's all working. And then all the tables are configured here. So what you should do is just go through it, start to whack on it, and anything you see, just start making a list of stuff."

Related

• ^[3]
• ^[4]
• ^[5]
• ^[6]
• ^[7]