Permissions Tab: Difference between revisions
No edit summary |
No edit summary |
||
| (17 intermediate revisions by the same user not shown) | |||
| Line 15: | Line 15: | ||
|This role is assigned to all members invited to the team. They do not have access to the Hub or other administrative features. | |This role is assigned to all members invited to the team. They do not have access to the Hub or other administrative features. | ||
|} | |} | ||
[[File:Roles.png|alt=Default Roles Permissions Checkboxes|center|thumb| | [[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 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. | |||
Any permission that is not selected is not granted to users assigned to the role. | |||
=== Checkbox States === | === Checkbox States === | ||
| Line 39: | Line 41: | ||
<div style="clear:both;"> | <div style="clear:both;"> | ||
In the image above the specific required for 'External Editor` include : | |||
Edit Itinerary to be able to add items to the itinerary like flight, | |||
=== 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 where they apply within the organisation.By default all role have organisation scope. | ||
{| class="wikitable" | |||
|+ | |||
!Organisation | |||
|By default all role have organisation scope.These permission apply to all itineraries and sections in the organisation | |||
|- | |||
!Itinerary | |||
|This refers to setting permission for a selected itinerary and supports only User and Custom Role. | |||
|- | |||
!Sections | |||
|This refers to setting permission for selected sections in an itinerary | |||
|- | |||
!Itinerary Tags | |||
|This refers to setting permission for itineraries with a specified itinerary tag | |||
|} | |||
</div> | |||
===== 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. | |||
[[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]] | |||
Latest revision as of 15:24, 15 July 2026
Roles
EventR includes four predefined roles.
| Owner | This role is assigned to the creator of the team/organisation and has full control.This role can be transferred to another member of the team.See Transfer Ownership .There can be only one owner at a time. |
|---|---|
| Admin | This role is equivalent to the Owner role and has full control.There can be multiple admin members |
| Guest | Members with this role do not have access to the Chat and Team tabs in the app. Only items that they are part of are displayed on the Home page, and only their name is listed. |
| User | This role is assigned to all members invited to the team. They do not have access to the Hub or other administrative features. |
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.
Any permission that is not selected is not granted to users assigned to the role.
Checkbox States
| Unchecked/Black | Permission Not Granted/Given |
|---|---|
| Checked/Green | Permission Granted |
| Disabled/Greyed | Permission not available or overridden |
| Locked | Permission denied |
In the image above the specific required for 'External Editor` include :
Edit Itinerary to be able to add items to the itinerary like flight,
Scope
Permissions are grouped into scopes that define where they apply within the organisation.By default all role have organisation scope.
| Organisation | By default all role have organisation scope.These permission apply to all itineraries and sections in the organisation |
|---|---|
| Itinerary | This refers to setting permission for a selected itinerary and supports only User and Custom Role. |
| Sections | This refers to setting permission for selected sections in an itinerary |
| Itinerary Tags | This refers to setting permission for itineraries with a specified itinerary tag |
Itinerary Scope
Section Scope
Itinerary Tag Scope
Itinerary tags can be attached on the event information page.
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.
