From August 11, you will only log in via your own Coachview address:
customername.coachview.com.
Logging in via secure.coachview.net will no longer be possible.
Are you already using your own Coachview address? Then no action is needed and the rest of this article is not relevant for you.
You may currently still log in via secure.coachview.net, but this will stop on August 11. From that date onwards, you will always log in via your own Coachview environment: customername.coachview.com.
You will also see a renewed login screen that better matches your own environment. You can customize it using the colours of your organisation via this guide.
Are you still using a bookmark, favorite or shortcut to secure.coachview.net? Please update it to your own Coachview address.
/guide-media/01KW908ACEXA98WCZTXGSFZWTS
Frequently asked questions
What exactly is changing?
The general login page secure.coachview.net will be discontinued. From now on, you will log in directly via your own environment: customername.coachview.com.
Do I need to take any action?
Only if you use a bookmark, favorite, or shortcut to secure.coachview.net. Please update it to your own Coachview address.
What is my login URL?
Your login URL has the format customername.coachview.com. Not sure which one to use? You can find it in the banner after logging in.
Can I still log in via secure.coachview.net after August 11?
No, this will no longer be possible. Please always use your own login address.
Do we need to update anything for the API?
No, nothing changes for the API.
Why is this change being made?
By letting everyone log in through their own Coachview environment, it becomes possible to use the same email address across multiple training providers. This makes things much easier going forward.
Will my login details change?
No, your username and password remain the same. Only the login URL changes.
Will anything change for SSO or integrations?
In principle, no. Existing integrations and Single Sign-On will continue to work. We do recommend checking any internal documentation or shortcuts and updating them where needed.