Create internal knowledge base

Hello everyone,

We are extremely happy to announce that we are working on this and planning to release it early next week.

How it works:

• In the dashboard Settings page, you will see a new Privacy tab

• By default, your knowledge base is public

• You will be able to set it "Private"

• After making your knowledge base private, you can add allowed email domains or individual emails outside your email domain

• At this point, anyone who wants to open your knowledge base will see a login form with your logo. They will enter their email address; if it's allowed individually or by allowed domains, we will send them a sign-in code

• They will enter the sign-in code and read the articles

Use case:

Imagine us, simplebase.co, we wanted to make our knowledge base private, so we:

• Go to the dashboard and change the privacy settings to private

• Add simplebase.co to "allowed domains" to allow everyone with simplebase.co email address to login

• Also, add our outside collaborators' emails separately to allow them to log in.

This would be a great feature!

If you are considering its implementation.

Here are the features I would like to suggest for inclusion:

1. Manage/ edit member permission

2. Control over which members can view or edit specific articles, which could be effectively combined with the first point

3. A registration system for volunteers who wish to offer assistance in editing documents (Nice to have, but not really required since it could easily be replaced by something like Google Forms or other forms platforms)

4. Displaying the contributors to an article to boost the motivation of volunteer editors

5. Allowing members to delete their accounts or allowing the site owner to delete a user's account

Dear Simple Base Development Team, please strongly consider the following, aside from the beauty and functionality that simplebase already is:

Internal Knowledge Base:

• Create a secure (password restricted) and accessible platform for internal team members.

• Implement role-based access control to ensure confidentiality.

• Design an intuitive interface for quick and efficient information retrieval.

• Enable seamless collaboration through features like commenting and version control.

Private Knowledge Base:

• Establish a restricted section with credentials for authorized personnel only.

• Implement robust authentication mechanisms to safeguard sensitive information.

• Ensure seamless integration with existing client management systems.

We believe that a knowledge base like this, not only empowers our organization but also enhances our ability to provide exceptional mental health services and all types of services.

Upvote please!

Also need the ability to hide for some users (Can be achieved via role like editor, manager, or custom role with permission :-) ) and option to hide so that the article is not publicly visible