Three permission-related issues were identified and addressed during the [1]. Two are resolved; one is in progress.
Status: Resolved
User affected: Steven Rousseau
Symptom: Error message when clicking the Convert button on a Lead record:
"You do not have access to the Apex class named convert lead LWC controller"
Root cause: A backend Flow action referenced an Apex class that was not accessible to the user's profile. This was introduced during earlier backend configuration work.
Fix: Mark Hope corrected the Flow to use an accessible Apex class.
Residual issue: The standard Salesforce "Convert" button remains visible on the Lead layout alongside the custom convert button, causing confusion about which to use. The standard button should be removed from the layout, as the custom button is the intended path.
"If he's clicking on the old button, then we clearly need to get rid of it." — Mark Hope
Status: Resolved
Symptom: Opportunity owners were unable to edit their own Opportunity records.
Fix: Mark broadened the sharing/permission rules so that any user who owns an Opportunity can edit it. Previously, permissions were too restrictive.
Notes: Lincoln can request further restrictions if needed, but the current posture is intentionally broad to unblock the sales team.
Status: In progress
User affected: Steven Rousseau
Symptom: Steven received an "insufficient permission" error when attempting to add a comment to a Task he owned on his own Opportunity.
Desired behavior:
- Any user should be able to add a comment to any Task
- Users should not be able to edit or delete another user's comment
- The comment field auto-stamps entries with a timestamp and username (already implemented)
Complication: The comment field is a single large text box rather than a structured comment thread, which makes enforcing per-entry edit/delete restrictions technically complex.
Next step: Mark is investigating whether Apex or Flow can enforce add-only behavior while preventing modification of existing comment content. If not feasible, the fallback is a documented convention: "Add your comment above; do not delete anyone else's."
"I'll see if I can make it where you can add comments, but you can't edit or delete anybody else's comments." — Mark Hope
As a related note, the task comment field now auto-inserts a timestamp and username on save. To ensure new comments appear at the top of the field (Salesforce defaults the cursor to the bottom):