J3.x:Access Control List Tutorial/de - Revision history

Max123kl at 07:24, 5 October 2023

2023-10-05T07:24:05Z

← Older revision		Revision as of 07:24, 5 October 2023
Line 4:		Line 4:
	==Separate ACL für Anzeige und Aktionen==		==Separate ACL für Anzeige und Aktionen==

	~~<div class="mw-translate-fuzzy">~~
	Das Joomla ACL-System besteht genau genommen aus zwei völlig getrennten Systemen. Das eine System steuert, was Benutzer auf der Website "sehen" können. Das andere steuert, was Benutzer "tun" können (welche Aktionen ein Benutzer durchführen kann). Die ACL wird für jedes dieser Systeme anders eingerichtet.		Das Joomla ACL-System besteht genau genommen aus zwei völlig getrennten Systemen. Das eine System steuert, was Benutzer auf der Website "sehen" können. Das andere steuert, was Benutzer "tun" können (welche Aktionen ein Benutzer durchführen kann). Die ACL wird für jedes dieser Systeme anders eingerichtet.
	~~</div>~~

	===Steuern, was Benutzer sehen können===		===Steuern, was Benutzer sehen können===

FuzzyBot: Updating to match new version of source page

2023-10-05T07:23:24Z

Updating to match new version of source page

← Older revision		Revision as of 07:23, 5 October 2023
Line 73:		Line 73:
	Das restliche Tutorial befasst sich mit der Steuerung, was Benutzer tun können - welche Aktionsberechtigungen sie haben.		Das restliche Tutorial befasst sich mit der Steuerung, was Benutzer tun können - welche Aktionsberechtigungen sie haben.
	</div>		</div>


	==Aktionen, Gruppen und Vererbung==		==Aktionen, Gruppen und Vererbung==

FuzzyBot: Updating to match new version of source page

2023-08-18T15:00:10Z

Updating to match new version of source page

Show changes

FuzzyBot: Updating to match new version of source page

2022-06-09T09:28:52Z

Updating to match new version of source page

← Older revision		Revision as of 09:28, 9 June 2022
Line 75:		Line 75:
	# '''Beitrag''': kann die Berechtigungen für einen bestimmten Artikel überschreiben. Diese Ebene gilt nur für Beiträge. Alle anderen Komponenten erlauben nur die ersten drei Ebenen.		# '''Beitrag''': kann die Berechtigungen für einen bestimmten Artikel überschreiben. Diese Ebene gilt nur für Beiträge. Alle anderen Komponenten erlauben nur die ersten drei Ebenen.

			<div class="mw-translate-fuzzy">
	====Konfiguration====		====Konfiguration====
	Diese erreicht man über System → Konfiguration → Berechtigungen. Die nun sichtbare Maske dient dazu, die Berechtigungen auf der obersten Ebene für jede Gruppe und jede Aktion festzulegen, wie auch in der folgenden Abbildung gezeigt.		Diese erreicht man über System → Konfiguration → Berechtigungen. Die nun sichtbare Maske dient dazu, die Berechtigungen auf der obersten Ebene für jede Gruppe und jede Aktion festzulegen, wie auch in der folgenden Abbildung gezeigt.
			</div>

			<div lang="en" dir="ltr" class="mw-content-ltr">
			This is accessed from System → Global Configuration → Permissions. This screen allows you set the top-level permission for each group for each action, as shown in the screenshot below.
			</div>

	[[Image:Screenshot_global_acl_J3_tutorial-en.png]]		[[Image:Screenshot_global_acl_J3_tutorial-en.png]]
Line 94:		Line 100:
	Der Zugriff auf Optionen ist nur für Mitglieder von Gruppen möglich, die die Berechtigung für die Aktion Konfiguration in für jede Komponente haben. Im obigen Beispiel hat die Gruppe Administrator die Berechtigung Erlaubt für die Option Konfigurieren, so dass Mitglieder dieser Gruppe auf diesen Bildschirm zugreifen können.		Der Zugriff auf Optionen ist nur für Mitglieder von Gruppen möglich, die die Berechtigung für die Aktion Konfiguration in für jede Komponente haben. Im obigen Beispiel hat die Gruppe Administrator die Berechtigung Erlaubt für die Option Konfigurieren, so dass Mitglieder dieser Gruppe auf diesen Bildschirm zugreifen können.

			<div class="mw-translate-fuzzy">
	===Kategorie===		===Kategorie===
	Auf die Kategorieberechtigungen wird im Category Manager zugegriffen: Bildschirm Kategorie bearbeiten, in einer Registerkarte oben auf dem Bildschirm. Dieser Bildschirm hat fünf Berechtigungen, wie folgt:		Auf die Kategorieberechtigungen wird im Category Manager zugegriffen: Bildschirm Kategorie bearbeiten, in einer Registerkarte oben auf dem Bildschirm. Dieser Bildschirm hat fünf Berechtigungen, wie folgt:
			</div>

			<div lang="en" dir="ltr" class="mw-content-ltr">
			Category permissions are accessed in the Category Manager: Edit Category screen, in a tab at the top of the screen. This screen has five permissions, as shown below.
			</div>

	[[Image:Screenshot_category_acl_j3_tutorial-en.png]]		[[Image:Screenshot_category_acl_j3_tutorial-en.png]]
Line 461:		Line 473:
	</div>		</div>

			<div class="mw-translate-fuzzy">
	==ACL Aktion Berechtigungs-Beispiele==		==ACL Aktion Berechtigungs-Beispiele==
			</div>

			<div lang="en" dir="ltr" class="mw-content-ltr">
			Here are some examples of how you might set up the ACL for some specific situations.
			</div>

	===Backend Beitrag Administrator===		===Backend Beitrag Administrator===
Line 612:		Line 630:


	<~~span~~ lang="en" dir="ltr" class="mw-content-ltr">===Hybrid Example===</~~span~~>		<div lang="en" dir="ltr" class="mw-content-ltr">
			===Hybrid Example===
			</div>

	<div lang="en" dir="ltr" class="mw-content-ltr">		<div lang="en" dir="ltr" class="mw-content-ltr">

FuzzyBot: Updating to match new version of source page

2022-06-09T08:40:25Z

Updating to match new version of source page

Show changes

Max123kl: Created page with "==Gastzugang zu einzelnen Menüpunkten und Modulen=="

2020-11-17T14:53:56Z

Created page with "==Gastzugang zu einzelnen Menüpunkten und Modulen=="

← Older revision		Revision as of 14:53, 17 November 2020
Line 1:		Line 1:
	<noinclude><languages /></noinclude>		<noinclude><languages /></noinclude>
	{{Joomla version\|version=3.x\|comment=Serie}}		{{Joomla version\|version=3.x\|comment=Serie }}
	{{-}}		{{-}}
	~~{{:J3.1:Access_Control_List/en}}~~

	==Separate ACL für Anzeige und Aktionen==		==Separate ACL für Anzeige und Aktionen==

Line 282:		Line 280:
	* '''Edit Own''' is the same as Edit except that it only applies to articles written by you.		* '''Edit Own''' is the same as Edit except that it only applies to articles written by you.

	==~~Allowing Guest-Only Access to Menu Items and Modules~~==		==Gastzugang zu einzelnen Menüpunkten und Modulen==

	Version 1.6 introduced the ability to create a View Access Level that is only for guests of the site (meaning a user who is not logged in). The example below shows how you can set up this new feature.		Version 1.6 introduced the ability to create a View Access Level that is only for guests of the site (meaning a user who is not logged in). The example below shows how you can set up this new feature.

Sieger66 at 19:07, 26 December 2019

2019-12-26T19:07:06Z

← Older revision		Revision as of 19:07, 26 December 2019
Line 340:		Line 340:
	# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-en.png\|center\|frame]]All of the other desired permissions are inherited.		# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-en.png\|center\|frame]]All of the other desired permissions are inherited.

	That's all you need to do. Members of this group can login to the back end and do everything in Article Manager but can't do anything else in the back end. For example, the screen below shows what a user in the Article Manager will see when they login to the back end.[[Image:screenshot_acl_tutorial_20110112-15-de.png\|center\|frame]]		That's all you need to do. Members of this group can login to the back end and do everything in Article Manager but can't do anything else in the back end. For example, the screen below shows what a user in the Article Manager will see when they login to the back end.[[Image:screenshot_acl_tutorial_20110112-15-en.png\|center\|frame]]

	==ACL Ansicht Zugriffsebenen-Beispiele==		==ACL Ansicht Zugriffsebenen-Beispiele==

Sieger66 at 19:06, 26 December 2019

2019-12-26T19:06:58Z

← Older revision		Revision as of 19:06, 26 December 2019
Line 338:		Line 338:
	# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.		# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.
	# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-en.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-en.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)		# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-en.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-en.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)
	# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-de.png\|center\|frame]]All of the other desired permissions are inherited.		# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-en.png\|center\|frame]]All of the other desired permissions are inherited.

	That's all you need to do. Members of this group can login to the back end and do everything in Article Manager but can't do anything else in the back end. For example, the screen below shows what a user in the Article Manager will see when they login to the back end.[[Image:screenshot_acl_tutorial_20110112-15-de.png\|center\|frame]]		That's all you need to do. Members of this group can login to the back end and do everything in Article Manager but can't do anything else in the back end. For example, the screen below shows what a user in the Article Manager will see when they login to the back end.[[Image:screenshot_acl_tutorial_20110112-15-de.png\|center\|frame]]

Sieger66 at 19:06, 26 December 2019

2019-12-26T19:06:50Z

← Older revision		Revision as of 19:06, 26 December 2019
Line 337:		Line 337:
	# Create a new group called Article Administrator and make its parent group Public, as shown below.[[Image:screenshot_acl_tutorial_20110112-10-en.png\|center\|frame]] Because its parent group is Public, it won't have any permissions by default.		# Create a new group called Article Administrator and make its parent group Public, as shown below.[[Image:screenshot_acl_tutorial_20110112-10-en.png\|center\|frame]] Because its parent group is Public, it won't have any permissions by default.
	# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.		# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.
	# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-en.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-de.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)		# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-en.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-en.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)
	# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-de.png\|center\|frame]]All of the other desired permissions are inherited.		# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-de.png\|center\|frame]]All of the other desired permissions are inherited.

Sieger66 at 19:06, 26 December 2019

2019-12-26T19:06:41Z

← Older revision		Revision as of 19:06, 26 December 2019
Line 337:		Line 337:
	# Create a new group called Article Administrator and make its parent group Public, as shown below.[[Image:screenshot_acl_tutorial_20110112-10-en.png\|center\|frame]] Because its parent group is Public, it won't have any permissions by default.		# Create a new group called Article Administrator and make its parent group Public, as shown below.[[Image:screenshot_acl_tutorial_20110112-10-en.png\|center\|frame]] Because its parent group is Public, it won't have any permissions by default.
	# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.		# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.
	# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-de.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-de.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)		# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-en.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-de.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)
	# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-de.png\|center\|frame]]All of the other desired permissions are inherited.		# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-de.png\|center\|frame]]All of the other desired permissions are inherited.

← Older revision		Revision as of 19:06, 26 December 2019
Line 338:		Line 338:
	# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.		# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.
	# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-en.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-en.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)		# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-en.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-en.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)
	# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-de.png\|center\|frame]]All of the other desired permissions are inherited.		# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-en.png\|center\|frame]]All of the other desired permissions are inherited.

	That's all you need to do. Members of this group can login to the back end and do everything in Article Manager but can't do anything else in the back end. For example, the screen below shows what a user in the Article Manager will see when they login to the back end.[[Image:screenshot_acl_tutorial_20110112-15-de.png\|center\|frame]]		That's all you need to do. Members of this group can login to the back end and do everything in Article Manager but can't do anything else in the back end. For example, the screen below shows what a user in the Article Manager will see when they login to the back end.[[Image:screenshot_acl_tutorial_20110112-15-de.png\|center\|frame]]

← Older revision		Revision as of 19:06, 26 December 2019
Line 337:		Line 337:
	# Create a new group called Article Administrator and make its parent group Public, as shown below.[[Image:screenshot_acl_tutorial_20110112-10-en.png\|center\|frame]] Because its parent group is Public, it won't have any permissions by default.		# Create a new group called Article Administrator and make its parent group Public, as shown below.[[Image:screenshot_acl_tutorial_20110112-10-en.png\|center\|frame]] Because its parent group is Public, it won't have any permissions by default.
	# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.		# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.
	# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-en.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-de.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)		# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-en.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-en.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)
	# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-de.png\|center\|frame]]All of the other desired permissions are inherited.		# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-de.png\|center\|frame]]All of the other desired permissions are inherited.

← Older revision		Revision as of 19:06, 26 December 2019
Line 337:		Line 337:
	# Create a new group called Article Administrator and make its parent group Public, as shown below.[[Image:screenshot_acl_tutorial_20110112-10-en.png\|center\|frame]] Because its parent group is Public, it won't have any permissions by default.		# Create a new group called Article Administrator and make its parent group Public, as shown below.[[Image:screenshot_acl_tutorial_20110112-10-en.png\|center\|frame]] Because its parent group is Public, it won't have any permissions by default.
	# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.		# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11-en.png\|center\|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.
	# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-de.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-de.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)		# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12-en.png\|center\|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13-de.png\|center\|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)
	# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-de.png\|center\|frame]]All of the other desired permissions are inherited.		# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14-de.png\|center\|frame]]All of the other desired permissions are inherited.