How to grant "Staff" permission so users can make Info pages
I've granted the user Kitch (in the SoundFlow forum) moderator role, because that feels like how I would make him a Staff member.
But when he clicks the "More" button to try to make an info page, it just disappears, the ability to make an Info page doesn't show up for him.
Is there anything else I should do to make him a Staff member?
- KajMagnus @KajMagnus2020-10-07 19:08:49.346Z2020-10-07 22:23:34.361Z
I'll fix that; nothing you can do about it.
I made Info Pages editable only by admins, by default, but not moderators. Probably this should be configurable, some day, and, for now, Mods & Admins is a better default, so I'll change that.
Will be fixed in an upcoming version, this Friday probably.
(What would you think about letting Core Members create & edit Info Pages?)
- CChristian Scheuer @chrscheuer
I'd be great to have Core Members be able to create & edit info pages.
I only made Kitch a moderator to give him access to make Info pages, which seems like too much of a jump to be forced to make.
Maybe we need an info page on Talkyard.io that describes the access levels (or even better, when you select the membership levels) and what they give access to.
The names are nice, but often I'm very unsure what they imply.- CChristian Scheuer @chrscheuer
FWIW, Kitch appears in the "Staff" group on our site after I made him moderator. So I'm not sure if this really is a bug somewhere?
It says "Only staff can create these:" in the drop down when selecting the "More..." button.- KajMagnus @KajMagnus2020-10-09 04:46:06.856Z2020-10-09 05:05:53.562Z
That's how it's supposed to work — that "Only staff can ..." .
And now I'm fixing things, so it will work like so, for real.I'd be great to have Core Members be able to create & edit info pages.
How interesting, I would have guessed you'd say it wouldn't matter or even was better if they couldn't.
There's also this old topic:
What if there was these two new permissions: 1) Create-&-edit-info-pages, and 2) Reply-on-info-pages.
Then, you could grant Create to Core members, and Reply to Everyone.There just needs to be a config setting for showing author names on Info Pages / Articles or not,
and then those "Article" topics will start working like you wrote?
(B.t.w. now I started thinking that maybe "Article" is a better name than "Info Page".)Maybe it'd make sense with a topic type "Announcement" too.
It'd be like an Article, but an announcement icon, not an article icon.
E.g. if a new version of [the software / product] got released?***
The above — Articles, Announcements, Info Pages, and the new permissions, in a way adds a "2nd permission system"?
There're permissions related to Question / Idea / Problem / Discussion pages — things that everyone typically can create, incl "random strangers".
And then there're permissions related to more official looking pages, that typically can be created only by members of the organization: Articles, Announcements, maybe Blog posts some day.
I wonder if this 2-types-of-... authorship & permissions? makes sense, hmm. Personally I don't remember having seen this anywhere else.
(inside —> out, and outside —> in.
From the organization —> inform the audience, or From outside —> ask the organization)***
info page on Talkyard.io that describes the access levels (or even better, when you select the membership levels) and what they give access to
I agree
- In reply tochrscheuer⬆:KajMagnus @KajMagnus2020-10-11 15:34:02.000Z
Now this works for moderators too, not just admins. (I upgraded Prod earlier today.)
Later there will be a way to give this permission to Core Members too (or even Trusted Members, maybe for specific categories only, depending on what the admins want).
- CChristian Scheuer @chrscheuer
Wonderful, thank you!
- Progresswith handling this problem