This article explains an upcoming change to how administrators sign in to your Conferences i/o app. Today, everyone who administers your app uses the same Administrator Password. We are moving to individual administrator accounts, where each person signs in with their own email address and password.
Note: This change has not been released yet. This article is advance notice so that you can plan. We will roll out this feature in September 2026 and allow both methods of authentication to occur for a period of time in order to ensure there is no disruption to your access.
Administrators who sign in through SSO
Working with individual accounts
Adding and removing administrators
Other changes at the same time
What is changing
Right now, anyone who knows your app's Administrator Password can sign in as an administrator. The password is shared by your whole team and is not tied to a person, so your app cannot tell one administrator from another. For how sign-in works today, see Sign-in to the Admin panel.
After this change, every administrator has their own account, tied to their email address. People sign in as themselves, and you can give or remove one person's access without changing a password for everyone else.
Individual accounts will be required on every site, and every administrator will need one. An account is not created automatically the first time someone tries to sign in. Someone has to be added as an administrator before they can get in.
Note: Only the Administrator Password is being retired. Your Moderator Password, App Password, and Q&A Facilitator Password are not affected by this change.
How the rollout works
The change happens in stages so that nobody loses access partway through.
Today. Administrators sign in with the shared Administrator Password. Nothing has changed yet.
Soon: Both methods accepted. Your app accepts the shared Administrator Password and individual accounts at the same time. Your team keeps working the way it does today while each administrator gets set up, and the sign-in page shows both options.
Later: Individual accounts only. The shared Administrator Password stops granting administrator access. From that point on, every administrator signs in with their own account.
Note: There is no setting for you to turn on. We move each app through these stages and will tell you when your app is starting and when it is finishing.
What you need to do
Existing apps
If your app already exists, you keep signing in with your current Administrator Password while both methods are accepted. During that stage, sign in the way you do today and add each of your administrators by email address. Each person receives an invitation and sets up their own sign-in.
Work through your full list of administrators during that window. Anyone who does not have their own account when your app moves to individual accounts only will be turned away at sign-in until an existing administrator adds them.
New apps
New apps are created with one administrator. You provide a single administrator email address when the app is set up. That person receives an invitation, and once their account is active they add the rest of your team the same way.
Administrators who sign in through SSO
If your app uses single sign-on, your administrators keep signing in through your organization's identity provider. Nothing about that changes while both methods are accepted.
Once your app moves to individual accounts only, a single sign-on login grants administrator access only if that person already has an administrator account on the app. We will set up accounts in advance for single sign-on administrators who have signed in recently, and anyone we miss can be added by an existing administrator. This may not capture all administrators depending on what data is coming through your SSO assertion.
Working with individual accounts
Setting up your account
When someone adds you as an administrator, you receive an email invitation with a link to set your password. After that, go to your app's admin sign-in page, choose to sign in with your admin account, and enter your email address and password.
Administrator access is granted one app at a time. If you administer more than one Conferences i/o app, you are added to each one separately and receive an invitation for each.
Adding and removing administrators
Administrators manage their own team from an Admins page in the Admin panel, without contacting support. The page lists everyone who has administrator access to the app, along with their email address and whether they have been invited, are active, or have been deactivated. Someone you have just invited shows as invited until they finish setting their password.
From that page you can invite a new administrator by email address, edit an administrator's details, edit your own, and deactivate someone. Deactivating takes effect immediately and does not erase the record of what that person did, so you can restore their access later without losing that history.
There is one level of administrator access. Everyone you add gets the same access you have, so add people you intend to give full administrative control of the app.
Note: LCVista Support and, where a partner manages your app, your partner's administrators also appear in this list so that you can see everyone with access. Those entries are managed by us and cannot be edited from your app.
Passwords and resets
Each administrator sets and manages their own password. If you forget yours, use the forgot password link on the sign-in page. Another administrator on your app can also reset it for you from the Admins page, which sends you an email to set a new one.
After a password is reset, the old password stops working and any session signed in with it is ended.
Accounts we create in advance
To reduce the setup work for your team, we will create accounts ahead of time for administrators we can identify as having signed in recently. This is a best effort and will not cover everyone. Our older sign-in records have gaps, and anyone who signed in with only the shared password left no record of who they were, so some people who should have an account will not get one this way.
Plan on checking the list yourself. When your app is ready, open the Admins page, confirm that everyone on your team is there, and add anyone who is missing.
Other changes at the same time
Once your app accepts individual accounts, actions that permanently delete data are confirmed by typing a short confirmation word instead of re-entering the Administrator Password, because administrators no longer share one password.
On single session apps, the Moderator Password also grants administrator access today. Once your app moves to individual accounts only, it still signs someone in as a moderator but no longer as an administrator. Anyone who has been using it to administer the app will need their own administrator account.
What to do now
There is nothing to set up yet. We will contact you with dates and instructions when your app is ready to start.
In the meantime, it helps to write down who currently has administrator access to your app and which email address each person should use. You will need that list when it is time to add everyone, and it is a good opportunity to leave off people who no longer need access.
Getting help
If you have questions about this change or about who has administrator access to your app, contact Customer Support.
Note: If you are turned away at sign-in and told to contact your site administrator, it means your app does not have an administrator account for you yet. Ask another administrator on your app to add you.