# Idea OP-1979 - Reauthentication ("danger zone") on critical operations

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-1979

## RICE

| Attribute | Value |
| --- | --- |
| Reach |  |
| RICE Score |  |
| Votes |  |

## Requires

_No work packages_

## People

| Attribute | Value |
| --- | --- |
| Assignee | Niels Lindenthal |
| Accountable | Niels Lindenthal |
| Product manager |  |

## Details

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Target versions | Wish List |
| Module |  |
| Priority | Medium |
| List |  |
| Interest by |  |
| Labels |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |

## Description

**As an** OpenProjectc.com user  
**I want to** be forced to reauthenticate  
**so that** someone taking over my session can not make those changes and I think twice before making those changes.

**Acceptance criteria**

  - There is a “danger zone” (like in GitHub) for critical commands where the user has to provide his password again such as:
      - Changing email address
      - Changing password
      - Deleting organization
      - Deleting repository
      - \[…\]

**Note**  
This is split off from <mention class="mention" data-id="16546" data-type="work_package" data-text="#16546">#16546</mention>
