User Manual

Frequently asked questions covering installation errors, SSL and CSRF setup, user login problems, roles vs groups, 2FA recovery, AD/LDAP troubleshooting, email configuration, and common Django/Nginx errors.

SecBoard uses Platform Roles (who the user is, dashboard view) and Access Groups (what they can do, module-level boolean permissions). Both layers are independent and additive. Superusers bypass all checks.

Configure Nginx as a reverse proxy for SecBoard: set up Gunicorn as a systemd service, obtain an SSL certificate with Certbot, deploy the HTTPS Nginx config, and enable production mode in credential.py.

Configure SecBoard email infrastructure: add a Mail Server (SMTP/IMAP), create a Mail Account, verify with a test email, and assign accounts to invitations, contact auto-reply, risk reports, and access notifications.

Configure basic platform parameters: site name, domain, protocol, project type, public page visibility, interface language, and contact information (address, phone, social links).

Complete your SecBoard setup: first login with the superuser account, update your profile, change the default password, enable 2FA, and invite your team.

Deploy *_build.tar.gz on a clean Linux host: Python 3.12 (SOABI/glibc gates), venv, migrate, collectstatic, Gunicorn (SecBoard.wsgi:application) behind nginx, TLS, optional Celery/Redis. Full runbook: DEPLOYMENT_INSTRUCTIONS.md; post-deploy app setup: PROJECT_SETUP_GUIDE.md.

Minimum and recommended server requirements for SecBoard: OS, CPU/RAM/disk, Python, MySQL (default) or PostgreSQL (on request), Nginx, Gunicorn, Redis, Celery, ports, and a quick check script.

A concise overview of the SecBoard platform: what it is, its 12 integrated modules, key concepts (roles, multilingual support, Knowledge Base), and next steps.