Documentation
PE Community Management Docs
Use this documentation to set up, administer, secure, operate, and contribute to PE Community Management.
Getting started
Understand workspaces, roles, and first steps.
First-run setup
Initialize the first community and Owner account.
Administration
Manage members, communication, work, and governance.
Notifications
Understand unread state, delivery, and preferences.
Automation
Configure, test, and review Task Board rules.
Encrypted chat
Manage recovery, authorized devices, and encrypted media.
Security
Review authentication, permissions, sessions, and encryption boundaries.
Architecture
Understand services, data flow, and background work.
Choose where to begin
The guides are organized by task and audience. Start with the path that matches your role or objective.
- Set up a new community: use Installation, Environment variables, Docker Compose, and First-run setup to prepare the application, initialize the community, create the Owner account, and confirm language and timezone defaults.
- Administer a community: Owners and authorized Admins should continue with Administration, Notifications, Automation, and Security for members, communication, events, Task Boards, governance, and audit activity.
- Use the Member workspace: begin with Getting started, then review Notifications and Encrypted chat for participant-facing updates, preferences, schedules, assigned work, and secure communication.
- Maintain or contribute: review Architecture, Configuration, Troubleshooting, and Contributing before operating the deployment or changing code.
Platform model
PE Community Management separates community administration from member participation. Access is permission-based and community-scoped.
- Administrative workspace: the Owner and authorized Admins manage membership, announcements, events, Task Boards, automation, notifications, storage governance, and supported audit activity according to assigned permissions.
- Member workspace: Members use participant-facing profiles, community information, assigned work, schedules, preferences, notifications, and encrypted communication made available to them.
Before you begin
- First-run setup is completed once: Prisma migrations prepare the database, then /setup initializes the first community and creates its first Owner. Initialization cannot be repeated after completion.
- Account security and encrypted-chat recovery are separate: account passwords protect application access, while encrypted-chat backups use separate recovery material that does not depend on the stored account password hash.
- Language and timezone are community-aware: setup establishes EN or FR and a timezone as community defaults. Supported user preferences may refine presentation, and date and time rendering follows the applicable community or user context.
Documentation coverage
- Installation and first-run initialization.
- Community configuration, roles, permissions, and administration.
- Notifications, communication, Task Board automation, and encrypted chat recovery.
- Storage governance, security architecture, backup and restore fundamentals, troubleshooting, and contributing.
Deployment guidance boundary
The deployment guidance covers the supported Docker Compose workflow.
Recommended next steps
Start with Getting started if you are learning the product model. For a new installation, continue with Installation and First-run setup; for an existing community, choose the administration, notification, automation, encrypted-chat, security, or architecture guide that matches your task.