Independent Group Management and Invites
under review
Speck of the Cosmos
One thing we'd like to do is to allow other chapters in our org to use a central wiki.js install to create their own spaces in the wiki that are private to them. (Not because they're secret but because it's not relevant to others). Can we set up group managers that can add and remove people? Also can we get an invite link that allows existing members of the website to automatically join that group and thus have access to that space?
Might be a different request, but can we auto generate private areas and groups based on categories in our auth management system? Like during setup the Atlanta group gets created and a private area automatically added? (Even script access to that would be good).
Sam Frank
We'd also really appreciate this feature. We have many clients on a single wiki, and we'd love for them to be able to add their own staff to their own group, but not have access to manage other groups.
David Laban
The first part of this sounds similar to the "workspaces" + "workspace managers" concept that our client wants in whatever platform they pick.
I can shim the "workspaces" part of it by having each top-level folder be a "workspace", and have groups that represent read-only/read-write access to each workspace.
I can't replicate the "workspace managers" concept, under the current implementation. It may be possible to extend the permissions system so that each group can have a "workspace-xyz" tag, and then have a "write:group-membership" permission, that can be filtered by group-tag (a bit like how page-rules works).
It might be worth taking a step back, and constructing a first-class concept of workspaces though.
@Spec of the Cosmos: to your other points:
* Our client's current platform has a "request to join workspace" system, but we have identified this pain point in the existing platform "Accepting requests to join a workspace creates a lot of overheads for workspace managers". This might want a bit of UX input.
* Generating workspaces and the associated roles sounds like a job for the graphql api. We will probably need to have a script to "create a workspace with these members" if we decide to migrate to a wiki.js-based platform. We would be looking to upstream as much of our work as possible, so hopefully we will end up producing something that can be used for your purposes.
Nicolas Giard
under review