-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Users design #11
Comments
Closed
User rights override group rights? |
Yes, they do. |
It ended up being really different with no granular control over everything. Well, maybe someday. Closing for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It was promised that MycorrhizaWiki would provide advanced user management. This issue is devoted to the design of the users. I'll use RFC 2119 here to look cool and classy.
User groups
users
SHOULD NOT be able to edit critical hyphae like templates.Suggested groups
MycorrhizaWiki MAY ship with these groups preconfigured, but wiki owner MAY change them.
admins
This is the most powerful group.
mycorrhiza
, the wiki's avatar user, and the wiki creator SHOULD be here.moderators
These are important users that were trusted with keeping peace and order on the wiki.
users
Regular users.
guests
Unauthorized users are considered as part of this group.
Overriding rights on per-hypha basis
admins
SHOULD be able to override rights per hypha branches. For example,admin
(∈admins
) decided that hyphaSecret plans
and its subhyphae shall be unavailable for everyone butadmins
. They would make such request:Edit, rewind and delete rights will be derived from write rights.
Another example. The aforementioned
admin
decided that everyone butguests
and userfungimaster
shall have access to hyphaHappiness
. They would make such request:Usage
When a user (or a guest) makes a request, MycorrhizaWiki SHALL match the user against per-hypha rights (if present) and then against per-group rights. If they don't have enough rights, they SHALL be informed about that and the request SHALL abort.
Storage format
Good old JSON of course.
TODO
The text was updated successfully, but these errors were encountered: