this post was submitted on 10 Oct 2026
56 points (96.7% liked)

Selfhosted

63148 readers
481 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
56
Dedicated admin account or normal privileged users? (lemdro.id)
submitted 1 week ago* (last edited 1 week ago) by stratself@lemdro.id to c/selfhosted@lemmy.world
15 comments fedilink hide all child comments
 

Hi all. I've been wondering about account separations while reviewing my SSO stuff. Do you all create a separate account for administrative tasks for your services? Or do you just give your normal account admin rights?

In my opinion, a different account is nice to separate impactful admin work (like provisioning users and groups) from general usage. Having this UX "barrier" also somewhat prevents doing dumb things like accidentally deactivating other people's accounts. But the downside is it can be quite inconvenient, especially if I need to administer or debug something quickly. I'm also not sure if my homelab expands, should I share the admin user credentials with other human admins or not.

What's the best topology to use? Or is there some other "accounts structure" that I've missed? I'm looking to replicate the same mapping between my identity provider and all dependent services as well (so that if an account is marked as admin on the IDP, it'll also be the admin for Forgejo or my Matrix server). So it'd be nice to settle on a plan right now.

Thanks for any responses!

you are viewing a single comment's thread
view the rest of the comments
[–] glizzyguzzler@piefed.blahaj.zone 6 points 1 week ago

I have an admin account on the server and an SSO admin login for the services. Different credentials obviously - ones an SSH key and ones a password/passkey for SSO - but it seems to fit well. My regular account is bozo level and I don’t need to worry much, I just logout or go to a private window to do admin for an specific program, which is rare but easy enough when it’s needed.

So far for the SSO services with an admin account design, I just set it up so the admin account for the service is named the SSO admin account so it maps directly when I connect the SSO to it.

And I SSH into the server for admin there as needed.

And no mixing with my regular user account!