# Gibt es eine Möglichkeit, dass Admin-Benutzer nicht im Admin-Modus sind usw.?

**URL:** https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510
**Category:** Feature
**Created:** [26. Februar 2018 um 05:35 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510 "2018-02-26T05:35:22Z")
**Posts on this page:** 13
**Page:** 1

<div class="post-metadata">

### Author: ![wolftune](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wolftune/32/103569_2.png) [@wolftune](https://meta.discourse.org/u/wolftune)
#### Post date: [26. Februar 2018 um 05:35 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/1 "2018-02-26T05:35:22Z")

</div>

Ich wünschte, es gäbe eine Möglichkeit, dass Moderatoren und Administratoren eine normale Benutzererfahrung haben und den Mod- oder Admin-Modus nur bei Bedarf aktivieren.

Am wichtigsten ist: Ich bin Administrator, möchte aber keine „Antworten"-Option bei geschlossenen Themen haben. Ich möchte einen zusätzlichen Schritt durchführen müssen und bewusst wissen, dass ich etwas tue, um Aktionen auszuführen, die nur Moderatoren oder Administratoren vorbehalten sind.

Gibt es eine Möglichkeit, diese Dinge zu unterscheiden oder zumindest zu _wissen_, welche Optionen nur deshalb angezeigt werden, weil ich Moderator oder Administrator bin?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [26. Februar 2018 um 12:55 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/2 "2018-02-26T12:55:51Z")

</div>

Log out and log back in as a normal non-staff account? More typically we see this concern expressed for admins who can download the site database versus moderators.

---

<div class="post-metadata">

### Author: ![wolftune](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wolftune/32/103569_2.png) [@wolftune](https://meta.discourse.org/u/wolftune)
#### Post date: [26. Februar 2018 um 17:34 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/3 "2018-02-26T17:34:25Z")

</div>

I assume you mean “have two different accounts”, right? In our case, we’d rather not have to manage other settings, details, profiles etc. for multiple accounts. I’d also want my normal posts to be associated with me, the same user who has mod and admin permissions.

I’m not concerned about the security issues. I’m talking about problems like accidentally posting a topic in a category a moderator thought was normal but was actually mod-only for posting and thus others visit it and find they can’t reply. There’s nothing indicating to the moderator at the time of posting that this is a moderator-only action as opposed to a normal action.

For example, at Reddit, moderators can enter and leave a moderator mode so that they can participate as normal users most of the time, and only when they really want moderator actions, they turn that on and only then are their actions labeled as being done by a mod…

---

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [26. Februar 2018 um 17:52 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/4 "2018-02-26T17:52:27Z")

</div>

Some kind of ‘sudo mode’ like Reddit, Confluence, Jira, etc. do?

It’s something that would be nifty to have but we don’t support that at this time.

How I would probably handle this would be using a specific colour for categories that are not “normal” posting categories and train the staff to expect this.

---

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [26. Februar 2018 um 17:52 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/5 "2018-02-26T17:52:47Z")

</div>

There’s also the possibility to highlight staff actions taken with “Staff Colour” to distinguish staff messages from regular postings.

---

<div class="post-metadata">

### Author: ![anon61128213](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@anon61128213](https://meta.discourse.org/u/anon61128213)
#### Post date: [26. Februar 2018 um 17:58 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/6 "2018-02-26T17:58:00Z")

</div>

I have an odd idea for a workaround:  
In firefox there is a plugin called “[multi account containers](https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/)”, which can be used to have two tabs of the sites open while being logged in with different accounts.  
You could either have a second account as a normal user to see what others see and then use the first account to post and do your moderation or you could even have a second admin account and with that grant mod-rights to your fist account only when needed.

---

<div class="post-metadata">

### Author: ![wolftune](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wolftune/32/103569_2.png) [@wolftune](https://meta.discourse.org/u/wolftune)
#### Post date: [26. Februar 2018 um 18:50 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/7 "2018-02-26T18:50:27Z")

</div>

> [@supermathie](#):
>
> There’s also the possibility to highlight staff actions taken with “Staff Colour” to distinguish staff messages from regular postings.

Yes, but that make every single post from someone in the Staff group be that color, right? So, it wouldn’t let the same staff user choose when to be acting as staff.

And yes, a “sudo mode” is one way to describe what I’m asking about.

---

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [26. Februar 2018 um 18:51 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/8 "2018-02-26T18:51:32Z")

</div>

> [@wolftune](#):
>
> Yes, but that make every single post from someone in the Staff group be that color, right? So, it wouldn’t let the same staff user choose when to be acting as staff.

No, that’s an on-demand action taken in the 🔧 menu:

 ![image](https://global.discourse-cdn.com/meta/original/3X/1/c/1ce9c45c830d27c6fe2933e0c5d0d1bff51a65c4.png)

---

<div class="post-metadata">

### Author: ![wolftune](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wolftune/32/103569_2.png) [@wolftune](https://meta.discourse.org/u/wolftune)
#### Post date: [26. Februar 2018 um 18:52 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/9 "2018-02-26T18:52:05Z")

</div>

The multi-account FF plugin idea would indeed make it easier to at least _see_ the distinction via two separate accounts, but it’s not a workaround for having distinct states within one account.

---

<div class="post-metadata">

### Author: ![wolftune](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wolftune/32/103569_2.png) [@wolftune](https://meta.discourse.org/u/wolftune)
#### Post date: [26. Februar 2018 um 18:53 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/10 "2018-02-26T18:53:17Z")

</div>

> [@supermathie](#):
>
> How I would probably handle this would be using a specific colour for categories that are not “normal” posting categories and train the staff to expect this.

I assume you mean as the best workaround to consider for now, right?

Anyway, per meta.discourse… should I open a _new_ topic somewhere to function as a request for the “sudo mode” sort of option?

---

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [26. Februar 2018 um 18:59 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/11 "2018-02-26T18:59:07Z")

</div>

This was more-or-less asked for a while ago here:

> [@Requiring password before admin actions can be taken](https://meta.discourse.org/t/requiring-password-before-admin-actions-can-be-taken/52603):
>
> I was thinking that it might be beneficial to have an option to require re-entering the password, before switching into admin mode or taking admin actions. Github as an example requires this and I think the main reason is to prevent/slow down destructive action by an adversary who gained access to a device with an admin login. The second feature I would like to see is 2FA, but that is already discussed elsewhere [Two-factor local login option](https://meta.discourse.org/t/two-factor-local-login-option/12597/8) If 2FA is implemented requiring 2FA, before admin a…

---

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [26. Februar 2019 um 21:49 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/12 "2019-02-26T21:49:14Z")

</div>

7 posts were split to a new topic: [Allow marking with Staff Colour in the compose menu](https://meta.discourse.org/t/allow-marking-with-staff-colour-in-the-compose-menu/110173)

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [31. März 2022 um 09:27 UTC](https://meta.discourse.org/t/any-way-for-admin-users-to-not-be-in-admin-mode-etc/81510/13 "2022-03-31T09:27:33Z")

</div>


