Permissions Tab: Difference between revisions

Judym (talk | contribs)
No edit summary
Kaylanp (talk | contribs)
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This page gives an explanation of the Permissions tab, found in the admin section.
== '''Roles''' ==
== '''Roles''' ==
EventR includes four predefined roles.
EventR includes four predefined roles.
Line 46: Line 48:


=== Scope ===
=== Scope ===
Permissions are grouped into scopes that define where they apply within the organisation.By default all role have organisation scope.
Permissions are grouped into scopes that define how far across the organisation they apply.By default all role have organisation scope.
{| class="wikitable"
{| class="wikitable"
|+
|+
Line 65: Line 67:


===== Itinerary 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]]
[[File:No delete itinerary permission.png|thumb|668x668px|Members with External Editor role can not delete the selected itinerary. On the app the delete itinerary button is disabled. While in [[EventR Enterprise Coordinator Hub Guide|ECH]] it is completely hidden.|none]]


==== Section Scope ====
==== 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.40.56.png|thumb|674x674px|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]]
[[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|687x687px|Image displaying the Event Information, Flights, and Accommodation tabs hidden ,on the ECH (Left) and on the App (Right), when they are locked in the section scope.|none]]


==== Itinerary Tags Scope ====
==== Itinerary Tags Scope ====
Itinerary tags can be attached on the event information page.
Itinerary tags are attached on the event information page.
[[File:Itinerary tags.png|none|thumb|907x907px|Itinerary tags]]
[[File:Itinerary tags.png|none|thumb|681x681px|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.
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.
Line 79: Line 81:
'''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.
'''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:Locked itinerary tag.png|left|thumb|873x873px|Selected Itinerary with the lock will not be displayed on the app or ech]]
[[File:Itinerary tags scope.png|thumb|874x874px|Image displaying permission granted via the itinerary tag scope on the hub and on the app.Excluded locked itinerary tags|center]]
[[File:Itinerary tags scope.png|thumb|800x800px|Image displaying permission granted via the itinerary tag scope on the ECH and on the app. The "Testing Test" itinerary is not visible due to permissions options. |center]]See  [[How to restrict visibility of sections to different user roles|External Editor]] example


==== Permissions Table ====
==== Permissions Table ====
Line 125: Line 127:
|This gives a team member the permission to view itinerary private entries for other team members on the Team and Team member pages.Owners and Admin have this permission enabled by default without being part of the entry. This permission can be added to a role on the Permissions Tab in ECH
|This gives a team member the permission to view itinerary private entries for other team members on the Team and Team member pages.Owners and Admin have this permission enabled by default without being part of the entry. This permission can be added to a role on the Permissions Tab in ECH
|}
|}
See  [[How to restrict visibility of sections to different user roles|External Editor]] example