EN | FR | DE | IT | NL
previous | next | index

Managing Member Information

To update a member profile, go to your club LionsBase data folder, locate the corresponding member record and edit it.

The various information of a member profile are organized by tab:

  • General: General member information such as names and birthday

  • Private: Private address, email address and phone numbers

  • Business: Business address, company and phone numbers

  • Lions: Lions-related information such as the history of status and functions

  • Misc.: Various additional pieces of information

  • Access: LionsBase access management

General information

This form lets you manage general member’s related information. The screen is divided into two parts:

The general information for the member themselves:

General information of the member

The email address of a member on this general tab is considered the main email address and is used for contacting members via email and newsletter. Additional email addresses can be entered for information purposes in the private and business tab.


The partner of a member may either be defined using a real relation or freely:

Information about the partner of a member

As you see on the picture, the birthday of a partner may be incompletely defined by omitting the year part.


The real relation should be used instead of free information if the partner is a Lions member as well. This ensures that the information are kept in-sync automatically and among other neat bonus allows you to navigate to the partner profile page from within LionsBase mobile. In addition, if you invite your partner, they will get the event in their own personal Lions calendar as well.

Here are a few internal (and more technical) considerations regarding both ways of specifying the partner:

  • when you define a partner relation, every other partner fields (first name, last name, email and birthday) will automatically get cleared upon saving;

  • at the same time, the mirror relation will be added to the corresponding partner;

  • however, corresponding mirror fields (first name, …) on the other end will not get cleared.

Rationale is that if you temporarily assign the wrong partner and save, clearing mirror fields would effectively lead to a loss of information after your correction. In that case, only the relation is defined and will of course take precedence over statically-defined data. Those useless pieces of information for the partner will only be removed when the other member’s record is updated.

Private information

This form lets you manage private information of the member.

Personal-related information of the member

Private country & state

Oak Brook requires the country state to be defined if the private country is either the United States or the Canada. For all other countries, choosing a state is at your convenience.

Business information

This form lets you manage business-related information of the member.

Business-related information of the member

Activity Classification

NACE is the acronym used to designate the various statistical classifications of economic activities developed since 1970 in the European Union. NACE provides the framework for collecting and presenting a large range of statistical data according to economic activity in the fields of economic statistics (e.g., production, employment, national accounts) and in other statistical domains.

Statistics produced on the basis of NACE are comparable at European and, in general, world level. The use of NACE is mandatory within the European Statistical System.

NACE is the European counterpart of the world level standard ISIC. At the national level, countries are free to model their own classification to take into account the needs of the various stakeholders. For instance, in Switzerland this standard is named NOGA 2008 and is modelled after NACE rev.2. In Austria, it is named ÖNACE 2008 (or OENACE 2008).

Online tools are available to quickly find the code corresponding to a given activity:

LionsBase stores the code as a serie of digits solely, meaning that if the code you get from your national classification is, e.g., “A 01.23” (which corresponds to the growing of citrus fruits), you will have to leave out the prefix (which is just a redundant way of organizing the underlying classification) and enter “0123” in the field.

Business country & state

Oak Brook requires the country state to be defined if the business country is either the United States or the Canada. For all other countries, choosing a state is at your convenience.


A few additional miscellaneous fields:

A few additional information for the member

Public Listing

The checkbox “Public Listing” is ticked by default for all members. It lets the member be part of any public listing of members. A typical example of such a public listing is the “Members” page that is available for all clubs without being authenticated. The actual fields that are shown has to be configured within the Members plugin itself.


The state of this checkbox is only taken into account for anonymous users; authenticated members will see the whole list of members regardless of the state of this checkbox. In addition, the state of this checkbox is only taken into account for the list of members within a club, not for the list of committee members which are always rendered, regardless of the state of this checkbox.


In Austria, this checkbox is respected when it comes to exporting the list of members for the directory of members, as requested in November 2016.

Access rights

This last tab lets you manage LionsBase credentials for the corresponding member. Additional fields for the actual member authorizations are available if you are authenticated as District LionsBase Master and are described in chapter Member Authorizations.

LionsBase credentials of a member

The username should be the main email address of the member; that may easily be copied by clicking on the button next to the field. If the member happens to have no email address, we allow a special username format to be used instead: <first name>.<last name>@lionsbase (e.g., franz.muster@lionsbase). The username will be checked for uniqueness upon saving.


If you suddenly gets a “0” appended to your username when you save (e.g., franz.muster@sunburst-ltd.ch0 with the username you see in the screenshot above), this means that TYPO3 detected that your username is in fact not unique and added a “0” to make it unique again. This basically means that another member is already using that same username. This may happen if the same member is present twice in system. If this happens, you probably want to edit the other member and change their username to something else so that the username is “free” to be used again.

The member’s password may be reset with this form but best is to ask the member herself to change or reset their password using the password recovery form.

Documentation created using Sphinx 4.3.2 and integrated in TYPO3 with restdoc.