A session would not sync if the session locations are missing in core.

Attendee email address is mandate field for attendees to sync from core.

Guests do not sync from Core to CC

Integration between CC and CrowdCompass supports integration for organizations

Integration between CC and CrowdCompass supports integration for tags and tracks

Integration between CC and CrowdCompass supports integration for attendees

Email address for attendees is mandate for them to sync to cc

Bio of attendees is mandate for them to sync to cc

Session start and end time is mandate for a session to sync to CC

Speaker headshots should be less than 5 mb for speakers to sync to CC

Speaker social media urls should be in http or https format for speakers to sync

A session directly created in crowdcompass will not be impacted by integration

Integration is one way from core to crowdcompass

Optional session do not sync to CC

All session do sync to CC unless integration is stopped for individual session

Speaker order on a session detail page will be random for a session syncing from core

There is nothing like subsessions in core

Session group in core is feature which allows attendee to pick only one session in the bundle

Admission items do not sync to CC but any session in personal agenda of attednee in core will show in my schedule of the attendee in CC

If session enrolment is on then any session in the past or closed session cant be added by the attendee in Cc to his schedule

If session enrolment is on then any session with a fee cant be added by the attendee in Cc to his schedule

If session enrolment is on then any included sessions can't be removed by the attendee in Cc from his schedule

If session enrolment is on then any included sessions in his admission item can't be removed by the attendee in Cc from his schedule

If session enrolment is on then any attendee created in CC and not coming from core can't add sessions to their schedule

If the registration modification is closed in the reg path or the modification until date is past attendee can neither add or remove any session from their schedule in CC

Only attendees created in core can add session to their schedule in CC if enrolment is on

Session with fee can only be added via registration website to the attendee schedule and not via the app by the attendee

Waitlisting is not supported via session enrolment in app

If an attendee is created in Cc he remains unaffected by integration

Personal agenda of attendee will sync back to core only when session enrolment is on

If a session X is created in Cc but them the same session syncs from core as well it will create a duplicate session in CC

When attendee modifies their profile in the app that information does not sync back to Core

Any field not syncing over from core for a session can be added and modified in CC without any overwriting eg parent unique I'd

Any field not syncing over from core for a session or speaker can be added and modified in CC without any overwriting eg tags and tracks

Session locations do not sync from core to CC

Speaker and Attendee headshots do not sync from core to Cc

There is a field mapping to prevent speaker headshots from syncing

There is a field mapping to prevent attendee headshots from syncing

Integration can be stopped for individual speakers and attendees

If am attendee has a guest then the guest will sync as a normal attendee in Cc so far as he has email address added

There is a field mapping for show on attendee list

There is no field mapping for attendee bio

Integration between CC and CrowdCompass supports integration for new session feedback survey only

Admission item controls what sessions will be included if the attendee picks the item and what choices will he have

What admission items are available to an attendee is controlled by his reg path

A session in the past or closed can't be added by the attendee to his schedule if enrolment is on

If attendee list display field mapping is unmapped then attednees will show on attendee list in the app

Reg type controls the reg path of the attendee

Reg paths are found under registration settings

An attendee can have only one reg type,reg path and admission item

An included session can't be made optional and vice versa

Any session added or removed to/from personal schedule in the app by the attendee will sync back to core only if session enrolment is on

A session part of a session group can't be removed in case its has invitee must select a session setting on

An attendee created in Crowdcompass will not be able to add session from core to his schedule in case s.e is on

If an attendee substitutes then his name will be removed from CC and his substitute's name will be added to attendee list in CC

If session enrolment is off attendee personal agenda will not sync to app

If session enrolment is off then attendee can add or remove any session from their schedule in the app but this info will not sync back to core

If session enrolment is off then attendee can add or remove any session from their schedule in the app but this info will not sync back to core

If a session has a zero dollar fee it still cant be added or removed by the attendee in the app if enrolment is on

The status of the attendee will be confirmed in CC for any attendee who syncs from core

Guests will not sync from core to CC if their email is not added

If session enrolment is off then session would not sync to crowdcompass

If integration is turned off after some time any sessions that have synced to CC will be deleted

Sessions pdf do not sync from Core to CC

If session is part of a session group attendee will not be able to remove that session from his schedule

If session integration is stopped what will happen

Which of the following will sync over to crowd-compass from Core

If session enrollment is off

Session description will not sync to CC from Core if field mapping is off for "session description"

Integration between CC and CrowdCompass supports integration for data tags

Travel data of an attendee will only show to him when he logs in with the core profile

What features will show to an attendee only when he logs in with the right profile

What features will show to an attendee only when he logs in with the right profile

The API token of an attendee can be extracted from admin management section in event-center

If a session is not syncing from core to cc it will also not show in the personal agenda of the attendee

There is no field mapping for attendee profile image

The setting that prevents overlapping sessions to be added to schedule is in the admission item

The setting that prevents overlapping sessions to be added to schedule is in the reg type

The setting that prevents overlapping sessions to be added to schedule is in the reg path

The field mapping that applies in an event depends on the configuration used during integrating the events

A speaker in core can't be associated to any session in CC

Speaker PDF do not sync from Core to CC

There is no field mapping on sessions for