Delete Entry Field "Allow the following users…" setting does not work without Allow User Delete enabled, and is overridden when it is

[zackkatz]

When Delete Entry is added as a field in a View, the field setting “Allow the following users to delete the entry” does not allow the Entry Creator to see or delete their entry unless the View-level Allow User Delete setting is also enabled.

However:

• Enabling Allow User Delete at the View level overrides the field-level visibility control entirely.
• This makes the field-level setting redundant and misleading in its current location.

Expected Behavior

• The View should have a single, centralized place for configuring who can delete entries.
  • This should be the Delete Entry tab in Settings
• If configured to allow Entry Creator deletion, the entry creator should:
  • See the Delete Entry control.
  • Be able to delete their own entry.
  • Not require a separate global toggle that overrides the visibility logic.

Actual Behavior

1. Field-level Allow the following users to delete the entry → Entry Creator:
   • ❌ Does not display the delete control.
   • ❌ Does not permit deletion without Allow User Delete enabled at the View level.
2. Enabling Allow User Delete at the View level:
   • ✅ Displays the delete control.
   • ⚠️ Overrides the field-level visibility rules entirely.

Steps to Reproduce

1. Add a Delete Entry field to a View.
2. In the field settings, set Allow the following users to delete the entry to Entry Creator.
3. Disable Allow User Delete in the View settings.
4. Log in as the entry creator and view the entry:
   • ❌ No delete control is visible.
   • ❌ Entry cannot be deleted.
5. Enable Allow User Delete in the View settings.
6. View the entry again as the creator:
   • ✅ Delete control appears.
   • ⚠ Field visibility rules no longer apply.

Screenshot

Top: Field-level setting. Bottom: View-level setting.

---

Proposed Change

• Move the “Allow the following users to delete the entry” option from the field settings into the View settings.
• Let the View settings determine who can delete entries.
• Use conditional logic (at the field level) solely for controlling the visibility of the delete button — not the permissions.
• This approach aligns the UI with actual behavior, removes redundancy, and makes it clearer where deletion permissions are managed.