Permissions Tab: Difference between revisions

(9 intermediate revisions by the same user not shown)

Line 17:

== '''Custom Roles''' ==

=== '''Custom Roles''' ===

Custom roles can be created to meet your specific requirements. For example, the '''External Editor''' role shown above allows members to add items to an itinerary, access the EventR Coordinator Hub (ECH) and the '''AI Inbox''' page, and interact with '''To-do''' checkboxes. However, members with this role do not have access to the '''Team''' page in the app.

Line 60:

Line 59:

|-

!Itinerary Tags

|~~Permission denied~~

|This refers to setting permission for itineraries with a specified itinerary tag

|}

</div>

[[File:No delete itinerary permission.png|thumb|845x845px|left|Members with External Editor role have can not delete the selected itinerary.On the app the delete itinerary button is disabled while in ECH it is completely hidden.]]

~~[[File:Screenshot 2026-07-15 at 15.40.56.png|left|thumb|881x881px|Image displaying section scope.This means member with this role have no access to selected sections]]~~

[[File:Screenshot 2026-07-15 at 15.35.51.png|alt=Image displaying the Event Information, Flights, and Accommodation tabs hidden on the ECH when they are locked in the section scope.|left|thumb|891x891px|Image displaying the Event Information, Flights, and Accommodation tabs hidden on the ECH when they are locked in the section scope.]]

===== Itinerary Scope =====

[[File:No delete itinerary permission.png|thumb|845x845px|Members with External Editor role have can not delete the selected itinerary.On the app the delete itinerary button is disabled while in ECH it is completely hidden.|none]]

==== Section Scope ====

[[File:Screenshot 2026-07-15 at 15.40.56.png|thumb|881x881px|Image displaying section scope.This means member with this role have no access to selected sections|none]]

[[File:Screenshot 2026-07-15 at 15.35.51.png|alt=Image displaying the Event Information, Flights, and Accommodation tabs hidden on the ECH when they are locked in the section scope for a certain role|thumb|891x891px|Image displaying the Event Information, Flights, and Accommodation tabs hidden on the ECH when they are locked in the section scope.|none]]

==== 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.

~~Firstly, select a 'scope' over which you wish for these permissions to apply~~. ~~'Organisation'~~ will ~~apply them at an organisation level, '~~Itinerary~~' will prompt you to select an itinerary that these permissions apply to, 'Section' prompts you to select a section of an itinerary (such as Flights, Accommodation etc~~.~~) and 'Itinerary Tag' prompts you to select one of your~~ itinerary tag ~~groups. The permissions can be allocated to each of 4 roles..~~.

[[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 17: / Line 17: @@
 [[File:Roles with customs.png|alt=Default Roles Permissions Checkboxes|center|thumb|617x617px|Default Roles Permissions Checkboxes with a sample custom role 'External Editor']]
-== '''Custom Roles''' ==
+=== '''Custom Roles''' ===
 Custom roles can be created to meet your specific requirements. For example, the '''External Editor''' role shown above allows members to add items to an itinerary, access the EventR Coordinator Hub (ECH) and the '''AI Inbox''' page, and interact with '''To-do''' checkboxes. However, members with this role do not have access to the '''Team''' page in the app.
@@ Line 60: / Line 59: @@
 |-
 !Itinerary Tags
-|Permission denied
+|This refers to setting permission for itineraries with a specified itinerary tag
 |}
 </div>
-[[File:No delete itinerary permission.png|thumb|845x845px|left|Members with External Editor role have can not delete the selected itinerary.On the app the delete itinerary button is disabled while in ECH it is completely hidden.]]
-[[File:Screenshot 2026-07-15 at 15.40.56.png|left|thumb|881x881px|Image displaying section scope.This means member with this role have no access to selected sections]]
-[[File:Screenshot 2026-07-15 at 15.35.51.png|alt=Image displaying the Event Information, Flights, and Accommodation tabs hidden on the ECH when they are locked in the section scope.|left|thumb|891x891px|Image displaying the Event Information, Flights, and Accommodation tabs hidden on the ECH when they are locked in the section scope.]]
+===== Itinerary Scope =====
+[[File:No delete itinerary permission.png|thumb|845x845px|Members with External Editor role have can not delete the selected itinerary.On the app the delete itinerary button is disabled while in ECH it is completely hidden.|none]]
+==== Section Scope ====
+[[File:Screenshot 2026-07-15 at 15.40.56.png|thumb|881x881px|Image displaying section scope.This means member with this role have no access to selected sections|none]]
+[[File:Screenshot 2026-07-15 at 15.35.51.png|alt=Image displaying the Event Information, Flights, and Accommodation tabs hidden on the ECH when they are locked in the section scope for a certain role|thumb|891x891px|Image displaying the Event Information, Flights, and Accommodation tabs hidden on the ECH when they are locked in the section scope.|none]]
+==== 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.
-Firstly, select a 'scope' over which you wish for these permissions to apply. 'Organisation' will apply them at an organisation level, 'Itinerary' will prompt you to select an itinerary that these permissions apply to, 'Section' prompts you to select a section of an itinerary (such as Flights, Accommodation etc.) and 'Itinerary Tag' prompts you to select one of your itinerary tag groups. The permissions can be allocated to each of 4 roles...
+[[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]]