Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Should we have organization accounts?

+2
−0

I've seen many times something like "This is just my personal opinion, not of the team" when administrators such as Monica Cellio respond to posts. In my opinion, this is because of a lack of a way to distinguish the two through authorship alone.

Therefore, should shared/organization accounts be allowed? And should Codidact have one? This would give the ability to be explicit about whether one is acting on behalf of a larger group, such as Codidact or a more community specific moderation team.


On a technical level, organization accounts should probably be explicitly marked somehow as shared accounts, and be restricted from certain things like voting, earning[1] editing or moderation privileges, etc. to prevent abuse, but otherwise I don't see an issue with having them.

One could also do something like dev.to, where users can post on behalf of an organization they belong to.

Erin Besinger for The DEV Team

That way, there is clear attribution to both parties, which also helps with transparency. However, this starts to complicate access rights and such, so it probably is something to be considered down the line rather than now.


  1. but perhaps being able to be granted, for instance for a Codidact official account ↩︎

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

2 answers

+4
−0

An alternative approach would be to have the concept of organizations but not separate accounts. A user who is a member of one or more organizations could have a way, when posting, to say "on behalf of this org", and it would show up something like your "for the dev team" example. Advantages:

  • No separate account, so no need to restrict voting etc.
  • Clear attribution (we know who posted it and not just that it was official).
  • More likely to be used correctly: if you have to log in as a different user in order to post something, that's more frustrating and it invites accidents (forgot to switch back after).
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

+1
−1

What is preventing staff from using a second account, potentially using an anonymous alias? If they want to only express their personal opinions, then simply register a second account, without the admin/staff/moderator etc status attached to it.

As long as the multiple accounts aren't interacting with each other or used as "sock puppets", there's no problem with that approach.

Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

2 different approaches (2 comments)

Sign up to answer this question »