A card where an organization admin could register the organization's own Google application, with a step-by-step guide. It is built but hidden for every customer today. Do not promise it.
DashboardIn developmentOrganizations use Haruno's own Google app. The card is switched off for everyone.
In development in this feature. It is not available to customers yet. Do not promise it.
In development: customers do not see this card
Organizations use Haruno's own Google application for Gmail, Calendar and Drive. The card below is built and tested, and it is switched off for everyone. Do not tell a customer they can register their own Google application on the dashboard.
What it would do
If it were switched on, an organization admin would find an Organization Google app card inside the closed section Your own sign-in apps (optional) on the Organization page. See Organization Yayoi app for that section.
The card lets an admin give Haruno a Google application of the organization's own. Members would use it whenever they connect a new Google service. Admins would:
Follow a guide with four steps, opened one at a time: create a project in Google's console, turn on the services (Drive, Gmail, Calendar), set up the consent screen, who may use it and the permissions, and create a "Desktop app" client.
Import the file Google gives them, Choose JSON file, or type the client ID and secret by hand.
Press Save Google app.
After saving, the card is marked App saved and shows the current client ID. It also says whether Google recognised the credentials: "Desktop credentials recognized" or "Verification inconclusive". That check does not prove the consent screen, the permissions or the test users are right.
Rules the card follows
Existing Google connections do not change. If the app is changed, people have to sign out, restart Haruno and sign in to Google services again.
Replace Google app and Remove Google app both exist. Removing asks first. Existing connections keep working, but new organization Google connections may not be possible.
Two admins saving at once get "Someone changed this setting. The latest version has been loaded; review it and try again."
Members never see the card.
What exists today
The dashboard service still honours a Google application that an organization saved earlier, even though the card is hidden.