CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM (Moderator: Dave Greenberg) »
  • Use case scenario #01: Chapter organizations with segragted frontend management
Pages: [1]

Author Topic: Use case scenario #01: Chapter organizations with segragted frontend management  (Read 1043 times)

nant

  • I post frequently
  • ***
  • Posts: 143
  • Karma: 4
    • Joomlapolis
  • CiviCRM version: 4.3.4
  • CMS version: Joomla 2.5.11
  • MySQL version: 5
  • PHP version: 5.3
Use case scenario #01: Chapter organizations with segragted frontend management
June 18, 2013, 02:56:30 am
In an effort to learn and share knowledge with the rest of the CiviCRM community I am preparing a set of use case scenario questions that could be the basis for a new wiki documentation section area.

My specific environment is based on:
  • Joomla 2.5.11
  • CiviCRM 4.3.4

Use case overview

A political party is organized in regional area based chapters.
Each such chapter is responsible for its own contacts.
Each contact becomes a member by completing an offline (as far as CiviCRM is concerned) form and making an offline bank payment. The payment and membership is recorded in CiviCRM Membership component. There are 2 extra fields created in the Membership data: the Party membership id number (a unique number generated externally and stored in CiviCRM) and the chapter name the member belongs to (this is a drop-down field in CiviCRM).

Each chapter has its own officers (also members) that have specific rights and obligations in terms of managing the chapter membership.

CiviCRM needs somehow to be configured in order to:

  • Allow chapter authorized members to view (and manage) chapter members from frontend (if possible)
  • Allow chapter authorized members to view (and manage) chapter members (and only chapter members) from backend area.
  • Allow chapter authorized members to send chapter related newsletters and mailings to chapter members.

Suggestions from other experts are welcomed in this discussion.
--
Nick (aka nant from CB Team)

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM (Moderator: Dave Greenberg) »
  • Use case scenario #01: Chapter organizations with segragted frontend management

This forum was archived on 2017-11-26.