Rolle für Experiences einrichten

To configure a user’s access to Experiences, create allow and deny rules on the Experiences tab of the user’s role. Allow rules grant access to Experience types, and deny rules further restrict that access.

NOTE: A user can perform only the actions explicitly defined by the allow rules.

NOTE: For a user to be able to bind content in Experiences, ensure the relevant content and/or media permissions are defined in their custom role.

To add Experiences permissions to a role:

1. Melden Sie sich bei der Contentful Web-App an.

2. Click Settings and select Roles & permissions.

3. Either create a new custom role or edit an existing one. The role editor page is displayed.

4. Gehen Sie zur Registerkarte Experiences.

5. In the Allowed area, click New allow rule to define the allowed Experience type and the actions the user can perform with it.
   

   NOTE: A user can perform only actions explicitly allowed by allow rules in their user role.

6. Select the Experience type according to the following options:

   • Experiences - Select this option to apply the allow rule to all experiences.

   • Experiences created by user - Select this option to apply the allow rule only to the experiences created by the user.

   • Selected experiences - Select this option to select a specific experience(s) the allow rule applies to.

   • Patterns - Select this option to apply the allow rule to all patterns.

   • Patterns created by user - Select this option to apply the allow rule only to the patterns created by the user.

   • Selected patterns - Select this option to select a specific pattern(s) the allow rule applies to.

   • Components - Select this option to apply the allow rule to all components.

   • Selected components - Select this option to select a specific component(s) the allow rule applies to.

7. Under Actions, select an action the user role can perform with the selected experience type from the drop-down menu.
   

   NOTE: You can select All actions for full access to the selected Experience type, or select a specific action for more granular permissions.

   NOTE: For Components and Selected components, only Read action can be selected. 

8. Click +With tags and select one or multiple tags to apply the permission only to the experience types with the selected tag(s).

9. In the Denied area, click New deny rule to define the denied Experience types and actions.
   

   Important: Deny rules override allow rules. They restrict the permissions granted to the user by allow rules.

10. Repeat steps 6-8, selecting the experience type, action, and tag options for the deny rule.

11. Click Save changes to apply your changes.

Experiences permissions can be set up using the Content Management API. Through the API, you can granularly add individual permissions to a role, each permission corresponding to an action.

Änderungen an einer Rolle über die API überschreiben die Einrichtung dieser Rolle über die Web-App-Benutzeroberfläche. Durch die Aktualisierung der Experiences-Berechtigungen über die Web-App werden die über die API festgelegten Berechtigungen überschrieben.

Read permissions may not be enforced correctly when fetching all Studio entries via API without entity-specific filtering fields.componentSettings[exists]=true|false.

To avoid receiving unexpected results caused by this limitation, always fetch Experiences and Patterns separately, and use entity-specific filters to ensure permissions are respected.