In Loom workspaces, when a viewer/creator lite user requests to become a Creator, admins receive email notifications prompting them to approve the request. Currently, the email only presents an Approve action; there is no way to explicitly Deny the request or prevent further notifications for the same requester.

Customers do not want to simply ignore or filter these emails; they want them to stop entirely and consider the current experience a “very poor user experience.”

Current behavior

1. Viewer requests Creator role (e.g., from within Loom).

2. Admin(s) receive an email with an Approve button.

3. Admin cannot:

• Deny the request from the email.
• Mark the request as resolved/denied in-product.
• Disable or mute future emails for that requester or for the workspace generally.

4. Workaround suggested so far: customer sets up email filters/rules to ignore these emails, which they rejected as unacceptable.

---

Requested behavior / Proposed solution
Provide admins with one or more of the following capabilities:

1. Explicit Deny action

• Add a Deny button in the creator-request email and/or in the Loom admin panel.
• Once denied:
• The requester should no longer trigger repeated creator-request emails to admins for the same workspace (or at least for a configurable period).
• The status of the request should be stored (e.g., Denied) so admins have auditability.

2. “Don’t notify me again” / mute control

• In the email and/or admin UI, allow admins to:
• Stop future creator-request emails from a specific user.
• Optionally, stop all creator-request emails for the workspace (global mute toggle).

3. Workspace-level notification settings

• In the admin settings, surface a control such as:
  • “Allow users to request Creator access: On/Off”

• • “Send email notifications to admins for creator requests: On/Off”

• • “Only send creator request notifications to specific roles/admins: [configurable]”

---

Benefits / Impact

• Reduces noisy and unwanted notifications for admins, especially in large enterprise workspaces.
• Aligns with admin expectations around control and governance.
• Improves perceived UX; addresses direct feedback that the current flow feels “very poor” because it forces email rule workarounds.
• Lowers support volume for complaints about persistent creator-request emails.