8dd97dec9b
- Replace the Phase-0 "content to be completed" placeholder Usage section in every community_* README.rst with the actual features built across Phases 1-6 (routes, crons, portal pages). - Add CHANGELOG.rst (19.0.1.0.0) to every community_* module. - Note independent-vs-bundled module relationships in the root README. - Fix HANDOFF.md: Phase 8 was already committed (9a24691) and a git remote is configured, contrary to what it still said; record 9-A progress and the open gaps (missing banner.png assets, live --test-enable suite not re-run this session, no v1.0.0 tag yet).
38 lines
1.2 KiB
ReStructuredText
38 lines
1.2 KiB
ReStructuredText
======================
|
|
Community OS Membership
|
|
======================
|
|
|
|
Generic membership engine: configurable tiers, family grouping, member IDs,
|
|
renewal automation, self-service portal, and a QR membership card.
|
|
|
|
Installation
|
|
============
|
|
Install as any Odoo module.
|
|
|
|
Configuration
|
|
=============
|
|
Settings > Members > Membership Settings.
|
|
|
|
Usage
|
|
=====
|
|
* Define tiers under **Members > Configuration > Tiers** (name, code, price,
|
|
period). Each tier auto-creates its membership product.
|
|
* A partner's ``membership_member_id`` is generated on activation using the
|
|
format string configured in Membership Settings (default
|
|
``MEM-{year}-{seq}``).
|
|
* A daily cron moves members to ``renewal_due`` at the configured reminder
|
|
offsets and to ``expired`` on expiry, sending the matching email template
|
|
and creating a draft renewal invoice for review.
|
|
* Members self-serve at ``/my/membership`` (status, tier, expiry, renew,
|
|
download card) and can be verified publicly, without exposing personal
|
|
data, at ``/membership/verify/<member_id>``.
|
|
* The QR membership card is a QWeb PDF report (85mm x 54mm) whose QR code
|
|
encodes the verification URL.
|
|
|
|
Credits
|
|
=======
|
|
|
|
Authors
|
|
-------
|
|
* Metatroncube Software Solutions LLP
|