Expectations
All customers with a login integration are expected to update end-user communications, including any Cadmium login pages, with accurate login and customer support instructions. The client should make it clear on their website/app what credentials the user should log in with (i.e. email and registration ID) and who to contact for login and access/registration support. If no contact information is present, and an end-user reaches out to Cadmium technical support, the user will be directed to reach out to the client contact on file.
Why is this expected?
- Cadmium technical support is meant for technical questions about the platform. Clients are expected to assign someone from their team/registration company to field end-user questions about registration, access, and login credentials.
- Cadmium technical support will not know the users' login credentials and will not be able to assist with login questions.
- Cadmium technical support cannot change access within the Eventscribe Website and Mobile App, as this originates within the third-party application. End-users need to contact registration if they want to update their registration package.
The expectation is that end-users reach out to the designated client support contact. Integration issues should be reported by the client to integrationservices@gocadmium.com after confirming the user should be able to log in and that there is in fact an issue. Please provide the user's login credentials:
- Single Sign-on (SSO): Username and password (request end-user temporarily reset password to test123)
- Query-to-Authenticate: Registration email and registration ID
Best Practices
Best practices regarding end-user communication are determined by your integration type, Single Sign-on (SSO) or Query-to-Authenticate.
NOTE
If you do not know what type of integration you have, your Integration Project Manager can confirm your integration type. Basic definitions are below.
- Single Sign-on (SSO): Users are redirected to a 3rd-party site (i.e. membership system) to enter their login credentials (i.e. username/password) and are then redirected back to Cadmium's site.
- Query-to-Authenticate: Users enter their login credentials (i.e. email/registration ID) on Cadmium's login page and Cadmium queries against the 3rd-party system's API to validate access.
All Integrations
As a general best practice, use consistent language for the terms you select for username and access key throughout your registration confirmation email, instructional emails, and within the Eventscribe Website or Mobile App.
Below are suggestions for additional text for the technical support popup. Customize this content to fit the specific needs of your event.
Settings Path: Eventscribe Website >>> Settings >>> Technical Support >>> Extra Details
- Extra Details Title = blank
- Extra Details Text = Please review the <a href="URL">FAQ page</a> for general questions. Log into this site with [enter login credential terminology here]. If you don't know this information, reference your registration confirmation email or contact [email and phone].<br><br>For technical support for this site, log in to submit a support ticket. Technical support is available 9am—9pm Eastern, Monday – Friday.
Single Sign-On
The user will be redirected to your third-party site's login page. All login instructions and customer support contact information should be listed there in addition to Cadmium's technical support pop-up as noted above.
Query-to-Authenticate
Below are suggestions for updated field values and text for your login screen. Customize this content to fit the specific needs of your event.
Website
Settings Path: Eventscribe Website >>> Settings >>> Users >>> Login Screen
- Label: 'Username' = "Email Address"
- Label: 'Access Key' = "Registration ID"
- Login Tag Line = "Please enter your registration credentials."
- Login Alert = "Registration ID not found."
- Custom HTML At Bottom Of Login Box = "'Forgot Registration ID' will only work if you've logged in previously. If you don't know your login credentials, reference your registration confirmation email or contact [email and phone]."
- User Can Create Account = No
- All users must originate in the third-party system, which is the source of truth for registrant data.

Mobile App
If you have a website, update your mobile app settings to mimic your website settings.
Settings Path: Eventscribe Mobile App >>> Settings >>> Accounts
Entry Page
- 'Introduction Text' = "Welcome to the [event name] mobile app! Please log in with your registration credentials."
- To ensure proper login integration, make sure the following settings are configured:
- App Settings > Accounts > Entry Page > "Skip Entry Page?" must be set to "Do not skip entry login screen."
- App Settings > Accounts > Login Process > Login Style must be set to "Login Only."
IMPORTANT NOTE
Changing either of these settings will bypass the login integration.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article