Using JRNI
Appointments
Calendar overview
Creating appointment bookings
Locating bookings and customers
Blocking out time on the calendar
Rescheduling and canceling bookings
Adding attendees to existing and upcoming bookings
Changing the staff member or resource on an upcoming booking
Creating pre and post appointment questions
Using Check In for appointments
Creating and managing bookings via Call Center
Parent and Child level overview
Locations overview
Resolving conflicting shift patterns
Staff
Creating staff members
Editing and removing staff members
Creating availability for multi-location staff
Creating and managing staff availability
Services
Resources
Analytics
Analytics overview
Using the Basic Dashboard
Using the HQ Dashboard
Using the Appointment Dashboard
Using the Event Dashboard
Using the Conversion Dashboard
Using the Capacity Dashboard
Exploring the library of Dashboards and Reports
Sending, scheduling, and downloading Reports/Dashboards
Creating and modifying a Dashboard
Creating your own Reports
Setting up KPI targets and alerts
Filtering Dashboard and Report data
Using Table Calculations
Drilling down into your data
Virtual Queuing
Overview of JRNI Virtual Queuing
Setting up a virtual queue
Overview of the Concierge page
Setting up and managing a display board
Managing live queues via the Concierge page
How customers can join a live queue
Booking journeys
How to translate your content
Connectors & API
Calendar
Video
CRM
Salesforce
Guide to Salesforce Integration with JRNI
Set up the data sync
Map customers, appointments and events
Link JRNI staff to Salesforce users
Standard and Custom object mapping
Use Studio inside Salesforce
Manage user permissions and profiles
Set up a booking journey in Salesforce
Add BookingBug updates to Chatter
Integrating with Yext for JRNI Appointments
Account Settings & Administration
Table of Contents
- All Categories
- Connectors & API
- Calendar
- Exchange
- Configure access type
Configure access type
Updated
by Tara
You'll need to configure your access type based on the type of permissions you require across your organisation.
Impersonation access
Impersonation works on a one-to-many basis. You’ll need to set up a dedicated service account on our behalf in Active Directory, and then give that account impersonation rights over all accounts it will need to access.
For example, if you have 5 branches and twenty five customer assistants whose calendars we need access to – our service account would need to be given Impersonation rights over those accounts within your Exchange server. We then create a staff member for each of them in the JRNI platform and link the two accounts using the email address to complete the integration.
Impersonation is administered by a system admin and cannot be changed by an individual mailbox owner. Access rights are actually set against the impersonator account (service account) and the rights granted are broad, covering the mailbox and calendar – although we only use access to the calendar.
Delegate access
The alternative to Exchange Impersonation is Delegate access. This is for each mailbox account to provide delegate access to the service account. Access rights are set on a one-to-one basis, and are administered by the mailbox owner, meaning rights can be granted or removed at any time by them.
One of the major advantages of using delegate access is that access rights are more granular, and you can pick and choose which folders or areas of the account we have access to.
