TLDR: Is dokuwiki a reasonable solution for non-airtable user account management? Or is there something better?
As I'm trying to build my application for a social maker related nonprofit organization that has about 105 members that cycle in and out, some are leaders in the group (9 board members, 4 officers, 6 area leads, etc), I want to have airtable data available to all registered members such as read only the member list and their contact information, and other people that can have access to member maintenance. And each member would be able to update their own information (self help). But with 100+ members, giving each an airtable account would be difficult to manage.
But then I realized we have a wiki page that supports user management, and I might be able to embed forms and views in certain pages that require different access. I'm curious if any of you see a flaw with this idea, or if there's a better solution.
Background: There's a free open source wiki product called dokuwiki (see https://www.dokuwiki.org/dokuwiki). You can see mine at https://wiki.chattlab.org. We use it as a way to document our makerspace. It has built in user management that you can have for general public or specialized namespaces like 'user', 'admin', 'janitor'. It has a fairly robust system to handle lost passwords, and assignment of multiple roles, so a person can be 'user' and 'janitor', but not 'admin'. This would allow you to embed airtable forms on pages that they have to sign in to see. The one drawback would be that you have to either pay for someone to host your dokuwiki unless you have your own server. Dokuwiki does a great job of identifying security issues and sending out updates.
Jeff Johnson
President, ChattLab Makerspace
