Q1. What is the problem that you are trying to solve?
Additionally, a homepage is required to create a project in Google Cloud and mark it as external in the consent page settings to allow users external to your @organization.com to use your platform with Google SSO.
Q2 - Who is impacted?
All companies that use their Passbolt to share their product passwords with their customers will have some information when they first land on the Passbolt server instead of ending up directly on the login page. They will also be able to use Google SSO to log in with their own @organization.com email instead of having to create an internal one.
Would also benefit any user who separates their passwords into different accounts by workspace (for example personal, work, university…) with Chrome profiles or different computers, for example.
Q3 - Why is it important and/or urgent?
It is important because customers will be able to learn about Passbolt before using it and will make Passbolt easier to use and friendly.
In addition, it could save costs since many platforms calculate the subscription of their services to be paid based on the number of users in the organization, so if you do not have to create internal emails you will have to pay less.
On the Google consent page, when set to external if the verification process is not approved, a warning is displayed that causes insecurity for users because they believe they could be exposed.
Q4 - What is your proposed solution? (optional)
Here you have the previous post where you can read about the proposal and find Google’s requirements for the homepage, which must be met.
Q5. Community support
People can vote for this idea to show traction:
- Must have: this is critical for me to have this
- Should have: this is important for me to have this
- Could have: this could be nice to have
- Won’t have: we should not schedule this (explain why)