![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
'Default' Access Groups
Title:
'Default' Access Groups
Area:
access groups
Summary:
I have several access groups that I put just about everybody in, and it would be convenient to be able to say 'these groups are default -- everybody I give access to should go in here automatically'.
Description:
The summary basically says it all. Some things I would note:
* You can remove people from the groups. So if you do want to give access to someone and not have them in your defaults, you can grant access, then go remove them from the groups they shouldn't be in.
* The UI page that lets you grant access to someone and shows you your groups should show the default groups checked when it loads so you don't have to do it.
* Granting access through the AJAX pop-ups should automatically put people in the default groups.
But, as always, all of this can be discussed and changed through the process of suggestions. I put it to you, dear community!
This suggestion:
Should be implemented as-is.
35 (71.4%)
Should be implemented with changes. (please comment)
0 (0.0%)
Shouldn't be implemented.
0 (0.0%)
(I have no opinion)
14 (28.6%)
(Other: please comment)
0 (0.0%)
no subject
no subject
no subject
no subject
As it is, though, people with design experience are really hard to come by around here...
Edit: Not that experience is necessary. Read the above statement as 'people who are good at design and like to do it and want to volunteer for Dreamwidth are hard to find' regardless of whether they've ever done it or not.
no subject
Before today, I might have volunteered, but I suddenly have what may be two paying gigs, so those come first. I do urge you to think of it as User Experience (UX) because it's not just UI or graphic design or IA or anything, it's all of it put together with the back end functionality.
I would be up for working with others to gather requirements and look at how other systems handle this multi-dimensional management stuff. I find Twitter's list UX surprisingly good, but that's probably operent conditioning from six years of using LJ's list interface, that is: the bar is set pretty low.
no subject
no subject
no subject
I realize not everyone thinks it should work this way, but it's much harder to 'notice' the users' absence than to remove their presence, IMO.
no subject
no subject
no subject
no subject
no subject