Admidio can manage multiple organizations. All data has always been stored as a function of one organization. After the initial installation of Admidio, one organization is available, which can be further set up. Via a wizard, any number of additional organizations can be added later.
By multi-organizational we mean that organizations that have some relationship with each other share one Admidio database. The individual organizations can have their own websites or share a common website.
Organizations that share an Admidio database can access a common person master. If a user works in more than one of these organizations, only one profile is stored for him in the database, which is displayed in all organizations. If the user updates this in organization X, organization Y can view this directly. The assignment to the organizations can be done here, as usual, freely by role assignments. Users with the appropriate rights can access the complete person master and thus make a user, who was previously only set up in organization X, conveniently also a member of their own organization through role assignment. The rights management is still role-dependent, so that a user can be an administrator in one organization and only have the right to maintain his profile in the other organization.
$g_organization
of the configuration file is preselected. To log in to the other organization, it must be selected and the user must be a member of at least one role of that organization.
If you have set up more than one organization in your database, there is only one organization from which the data for logged out users is displayed. This is the organization from the parameter $g_organization
of the configuration file. The other organizations can be selected during login and are therefore only available to logged in users.
However, if you want to run other organizations as a standalone website, where the data is displayed even when logged out, you need to set up separate Admidio installations for these organizations.
For this purpose the following steps are necessary:
adm_my_files
to the new folder adm_my_files
of your new installation. Then you have to change the variables $g_root_path
and $g_organization
accordingly. Make sure that the variable $g_root_path
in the configuration file points to the correct path of your new organization.
If the organization selection box should no longer be displayed in the login dialog, it can be switched off in the Settings under Organization with the checkbox Display organization selection.
For future updates, make sure that all installations have the same major version. So organization A has version 4.1 and organization B must then also have version 4.1. If organization B had version 4.0 there would be errors on the page. The sub-version e.g. 4.1.7 can differ, but a synchronous version is recommended here.