Mokanata Docs
Getting started

Confirm destructive actions

Deleting, removing, disconnecting or revoking something asks for a current code from your authenticator app, so a stolen session alone can't destroy anything.

Actions that can't be undone, such as deleting a record, removing a member or disconnecting a channel, ask for a fresh code from your authenticator app before they run. Someone who gets hold of a signed-in browser still can't destroy anything without your phone.

  • Who can use it: Anyone whose role allows the action. The code is always your own.
  • Before you start: Your authenticator app, set up when you created your account (see Create your account).

Confirm with a code

Start the action

Choose the action as usual, for example Delete in a row's ⋯ menu. The confirmation dialog says what will happen.

Type the code from your app

Type the 6-digit code your authenticator app shows for Mokanata into the code field in the dialog. Codes change every 30 seconds, so use the one on screen now.

Confirm

Click the red button. Mokanata checks the code first: a wrong code shows under the field and nothing happens. With the right code, the action runs.

Deleting a workspace or your account asks you to type its name or your email as well as the code.

Which codes work

Only a current code from your authenticator app confirms an action. Recovery codes and codes sent by email work for signing in, not here. If you don't have your authenticator app, sign in another way and reset it first; resetting also asks for a code, so if your app is gone, contact the workspace owner or Mokanata support.

After 5 wrong codes in 5 minutes, Mokanata asks you to wait before trying again.

When a platform admin views your account to help you, their own authenticator confirms these actions, not yours.

Troubleshooting

Next steps

On this page