Permissions Tab: Difference between revisions

(2 intermediate revisions by the same user not shown)

Line 73:

==== Itinerary Tag Scope ====

Itinerary tags can be attached on the event information page.

[[File:Itinerary tags.png|none|thumb|907x907px|Itinerary tags]]

On the '''Permissions''' page, under the '''Itinerary Tag''' scope, select the itinerary tags and configure the permissions for the specified role. Check the box to grant access, set a lock to deny access, or leave it unchecked to inherit the default permission which is access granted.This means that any member assigned to a role with this configuration will have access to '''all checked, unchecked, and untagged itineraries.''' However, they will not have access to any itineraries that are locked.

'''Best practice:''' Tag all itineraries and explicitly configure each tag by either checking it to grant access or locking it to deny access. This ensures permissions are applied consistently and produces the expected access results.

[[File:Locked itinerary tag.png|left|thumb|927x927px|Selected Itinerary with the lock will not be displayed on the app or ech]]

[[File:Itinerary tags scope.png|left|thumb|874x874px|Image displaying permission granted via the itinerary tag scope on the hub and on the app.Excluded locked itinerary tags]]

@@ Line 73: / Line 73: @@
 ==== Itinerary Tag Scope ====
 Itinerary tags can be attached on the event information page.
+[[File:Itinerary tags.png|none|thumb|907x907px|Itinerary tags]]
 On the '''Permissions''' page, under the '''Itinerary Tag''' scope, select the itinerary tags and configure the permissions for the specified role. Check the box to grant access, set a lock to deny access, or leave it unchecked to inherit the default permission which is access granted.This means that any member assigned to a role with this configuration will have access to '''all checked, unchecked, and untagged itineraries.''' However, they will not have access to any itineraries that are locked.
 '''Best practice:''' Tag all itineraries and explicitly configure each tag by either checking it to grant access or locking it to deny access. This ensures permissions are applied consistently and produces the expected access results.
+[[File:Locked itinerary tag.png|left|thumb|927x927px|Selected Itinerary with the lock will not be displayed on the app or ech]]
 [[File:Itinerary tags scope.png|left|thumb|874x874px|Image displaying permission granted via the itinerary tag scope on the hub and on the app.Excluded locked itinerary tags]]