ECH Admin Screen: Difference between revisions
New and improved definition for the padlock. Think this is as clear as I can get it |
|||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
The Admin screen is where you control various settings for your organisation. | The Admin screen is where you control various settings for your organisation. | ||
=== Organisation Tab === | === Organisation Tab === | ||
[[File:ECH Admin Screen.png|thumb|ECH | [[File:ECH Admin Screen.png|thumb|ECH organisation screen (admin tab)|center|513x513px]] | ||
Basic information about your organisation, including subscription summary. | |||
<div style="clear:both;"> | <div style="clear:both;"> | ||
=== Settings Tab === | === Settings Tab === | ||
{| class="wikitable" | |||
|+ | |||
!Setting | |||
!Definition | |||
|- | |||
|'''In app editing enabled for admins only''' | |||
|Prevents other roles from carrying out in app editing | |||
|- | |||
|'''Disable in app editing for everyone (including admins)''' | |||
|Leaves in app editing responsibility with owner | |||
|- | |||
|'''Disable user invites in app''' | |||
|Prevents generation of user invite links in app | |||
|- | |||
|'''Disable chat in app''' | |||
|Disables app chat | |||
|- | |||
|'''Disable location sharing in app''' | |||
|Disables app location sharing | |||
|- | |||
|'''Enable Booking Service in the coordinator hub''' | |||
|Enables Hotel Booking service to be accessed in ECH | |||
|- | |||
|'''Expense Tracking mode''' | |||
|Personal means expenses are managed solely within the app, while Approval enables full approval workflow integration within the ECH. | |||
|- | |||
|'''Enable Booking AI in the coordinator hub''' | |||
|Enables Booking AI in ECH | |||
|- | |||
|'''Number of days events can be added before event starts''' | |||
|Set day window | |||
|- | |||
|'''Number of days events can be added after event ends''' | |||
|Set day window | |||
|- | |||
|'''Name format for team members in the EventR Coordinator Hub''' | |||
|Choose from a list of first name, second name, and initial combinations | |||
|- | |||
|'''Name format for team members in the EventR App''' | |||
|Choose from a list of first name, second name, and initial combinations | |||
|- | |||
|'''Name format for team members in the team PDF''' | |||
|Choose from a list of first name, second name, and initial combinations | |||
|- | |||
|'''Enable additional information profile options for EventR team and EventR Coordinator Hub users''' | |||
|When enabled, users can add more details to their profile page and choose to share them with Parekh. If this setting is active, profile information for users added via the HUB will be automatically shared with the team until they opt out. | |||
|- | |||
|'''Enable additional information sections to be required''' | |||
|Once sections have been enabled, you can require users to provide and share additional information sections with the team | |||
|- | |||
|'''Toggle severity of additional user information''' | |||
|Once sections have been required, you can set alert levels.By default a required section is set to 'Dot marker' | |||
|} | |||
<div style="clear:both;"> | |||
=== Permissions Tab === | === Permissions Tab === | ||
[[File: | 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... | |||
{| class="wikitable" | |||
|+ | |||
!User | |||
|Users can have each of their permissions toggled individually. | |||
|- | |||
!Guest | |||
|Guests have EventR Team access, but <u>no</u> activated permissions. | |||
|- | |||
!Admin | |||
|Owners can allocate users to become admins, who can then have their individual permissions adjusted to reflect the level of control they require, should they need more control than standard users. | |||
|- | |||
!Owner | |||
|The team owner will remain owner <u>forever,</u> and will always have 'full control' selected, i.e. all permissions activated across all scopes. | |||
|} | |||
The checkboxes can either be green (permission activated), greyed out (unable to toggle that permission), black (permission not activated) or locked (denies a permission that may be implied by the permissions in other scopes). [[File:Four Available Checkbox Colours.png|center|thumb|Clockwise from top left: Black, Green, Grey, Locked.]] | |||
<div style="clear:both;"> | <div style="clear:both;"> | ||
=== Theme Tab === | === Theme Tab === | ||
[[File:ECH Admin Theme Tab.png|thumb|ECH theme screen (admin tab)|center|507x507px]]Create custom app theme for team members.<div style="clear:both;"> | |||
<div style="clear:both;"> | |||
=== Section Setup Tab === | === Section Setup Tab === | ||
[[File:ECH Admin Sections Tab.png|thumb|ECH | [[File:ECH Admin Sections Tab.png|thumb|ECH sections screen (admin tab)|center|514x514px]] | ||
Deactivate and active sections of your itinerary to alter their visibility to your team members. | |||
<div style="clear:both;"> | <div style="clear:both;"> | ||