Skip to content

[Due for payment 2025-02-19] Prevent Self-Approval: Fix Unexpected Behavior for Historical Workspaces and Update Existing Approvers #53799

@marcaaron

Description

@marcaaron

cc @JmillsExpensify coming from our DM

While we have the ability to set "Prevent self approval" on a workspace. There are some ways in which this feature works unexpectedly in NewDot. Specifically, the following scenario is possible and should not be:

Historical workspace behavior

Problem

  • User has historical workspaces with themselves already set as the approver.
  • Self approval is then enabled.
  • What should we do after that? They should not be able to approve their own expenses, but we need some way to "fix" the reports currently submitted to themselves.

Solution

  • Create a modal that warns the user that any users who are currently approving their own reports will be removed as the manager.
  • Set the approver back to the "default approver" as shown here:

image

Issue OwnerCurrent Issue Owner: @JmillsExpensify

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDesignInternalRequires API changes or must be handled by Expensify staffNewFeatureSomething to build that is a new item.ReviewingHas a PR in reviewWeeklyKSv2

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions