Configure BookStack Roles, Permissions, and Initial Documentation Structure

[sinke237]

📝 Description

This ticket covers the post-deployment configuration of the BookStack instance for Rust Cameroon. After deployment, the next steps include setting up user roles, access permissions, and the initial structure of the documentation (both public and private).

This setup is critical for organizing content securely and ensuring different teams (management, technical, partners, etc.) can access the appropriate sections of documentation.

🔗 Dependency: This ticket depends on:
#23

---

🎯 Objectives

• Establish clear user roles and access policies.
• Separate public-facing content from internal docs.
• Ensure role-based access control is functioning as intended.

---

📦 Tasks

• Launch the deployed BookStack application and verify basic access

• Configure the application to have the community name, logo and colors

• Create the following roles with appropriate permissions:

  • Admin
  • Editor
  • Viewer
  • Management
  • Technical Team
  • Partners
  • Participants-2026 (to let them journal)

• Create user accounts or groups and assign to roles

• Set up initial documentation areas:

  • Public: General project info, public guides, contributor onboarding

  • Private:

    • Internal working group docs
    • Management-level strategies and reports
    • Technical team planning / implementation notes

• Test role-based access control:

  • Confirm that each role can only view/edit the intended content
  • Verify that private content is hidden from unauthorized users

• Document the role matrix and permission levels for future admins

---

📎 Notes

• Use BookStack’s built-in role management UI to fine-tune permissions.
• Keep a copy of the role-permission matrix in the wiki itself under an admin-only page.
• Roles can be refined later as usage patterns evolve.