Before you start
- The exact user, page and action involved.
- An administrator for any role/permission change; do not borrow another user’s session to work around access.
Open in your admin application
Use your installation’s admin address with one of these routes. Replace {id} with the actual record identifier.
/my-leads/unassigned-leads/users/roles/sales-representativesWork out what is missing
Identify the exact action
Record the page route and whether the issue is viewing, inserting, editing, assigning, bulk changing or communicating. A role can allow one action and not another.
Check the record context
Verify LeadID and assigned Sales Representative. My Leads is an ownership-filtered queue; absence there is not proof that the record does not exist.
Check communication conditions
The lead detail computes communication availability from ownership or permission to communicate with unclaimed leads. Missing call/message controls can reflect those conditions, not a broken phone number.
Check action-specific authorization
Ask the administrator to compare the user’s intended role with lead-insert, assignment and bulk-operation permissions. Use Users, Roles and Sales Representatives as the administrative starting points; exact permission assignments belong to the installation.
Verify after a permitted correction
With the affected user, revisit the original page and action, then test the intended positive and negative cases. Do not validate a sales-user fix solely while logged in as an administrator.
Fields & records
| Field / record | Meaning or use |
|---|---|
| UserID | Login/access identity. |
| SalesRepresentativeID | Sales ownership relationship; not interchangeable with UserID. |
| Page / action / record | Three distinct dimensions of an access report. |
Verify the result
- The intended user can perform the authorized action on the correct record.
- An unrelated or unauthorized record/action remains unavailable.
Troubleshooting
| What you see | What to check or do |
|---|---|
| Works for admin only | Reproduce with the affected role and ownership context. |
| Bulk action absent | Check specific bulk permission; standard list access does not imply bulk mutation. |
| No phone/email action | Check contact data and communication permission/ownership conditions. |
Version & scope
Procedure checked against current Feeding Frenzy forms and services. Source verification is not a claim that a live payment, message, customer transaction or full operator run occurred.
Public guides describe shared controls, records and configuration boundaries using fictional data. Tenant URLs, credentials, customer records, provider identifiers and installation-only procedures belong in customer-controlled documentation and are excluded from public pages and search.
- Version
- 2.0.0
- Change source
- Current Feeding Frenzy forms/services plus reconciled Wiki topics
- Feedback key
guide:permissions
Feedback records only the page, guide ID and yes/no choice. It never records documentation search text.
Implementation references (2)
FeedingFrenzy.Admin/wwwroot/kScripts/Leads/Lead.Details.ks.htmlFeedingFrenzy.Admin/wwwroot/Wiki/lead-management/permissions-and-sales-vs-admin.md