| Both sides previous revision Previous revision Next revision | Previous revision |
| en:2.0:mehrere_organisationen_verwalten [2021/01/02 21:44] – fasse | en:2.0:mehrere_organisationen_verwalten [2024/12/02 17:48] (current) – [When it is advisable to set up further organizations ?] greno |
|---|
| 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. | 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. | 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. | 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. |
| For this purpose the following steps are necessary:\\ \\ | For this purpose the following steps are necessary:\\ \\ |
| - The database is set up for the new organization as described in the previous chapter. | - The database is set up for the new organization as described in the previous chapter. |
| - Now you need to set up a new web space. To do this, download exactly the same Admidio version as in your initial configuration and place it in a new location on your server.\\ If you have been using Admidio 3.3.x so far, the new organization must also get version 3.3.x. The version 3.2.x would cause problems. If exactly this version is no longer available, the initial configuration should be updated to the latest version and then this version should also be used for the new organization. | - Now you need to set up a new web space. To do this, download exactly the same Admidio version as in your initial configuration and place it in a new location on your server.\\ If you have been using Admidio 4.1.x so far, the new organization must also get version 4.1.x. The version 4.0.x would cause problems. If exactly this version is no longer available, the initial configuration should be updated to the latest version and then this version should also be used for the new organization. Older versions of Admidio are still available at [[https://sourceforge.net/projects/admidio/files/Admidio/|Sourceforge]]. |
| - Do //no// installation or update on the new instance. | - Do //no// installation or update on the new instance. |
| - Now copy the **config.php** of your source installation from the folder ''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. | - Now copy the **config.php** of your source installation from the folder ''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. |
| - Now you can log in to the new organization with the administrator's credentials and continue setting up Admidio. | - Now you can log in to the new organization with the administrator's credentials and continue setting up Admidio. |
| 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**.\\ \\ | 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 3.3 and organization B must then also have version 3.3. If organization B had version 3.2 there would be errors on the page. The sub-version e.g. 3.3.2 can differ, but a synchronous version is recommended here. | 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. |
