Update 27th March 12:14PM CET
Some users have reported loss of access to Appscript.
Root cause: Appscripts recently created may not have been whitelisted
Resolution: Raise a incident ticket with the app ID.
Click on error details
Copy and paste text in the client ID shown pop up to the incident ticket. (in red)
Error 400: admin_policy_enforced
Request details: access_type=offline login_hint=charles.fromage-ext@syensqo.com hl=en response_type=none gsession redirect_uri=https://script.google.com/oauthcallback state=12345661395298156544 client_id=408709770952-5o37rm454pr8poa5pvukcmf9e747ics6.apps.googleusercontent.com prompt=consent enable_serial_consent=true scope=https://www.googleapis.com/auth/spreadsheets flowName=GeneralOAuthFlow
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Appscript embedded in Google documents that belongs to a Syensqo user should work as per normal post migration if the Appscript only requires [Google Sign-in] information.
If your Appscript requires more than [Google Sign-in] scope, it may be blocked due to security reasons. Please raise an incident ticket to have your Appscript unblocked. (Subjected to security guidelines)
Notes:
For new users who are executing the Appscript, they will be presented with a warning page. Users have to
1) Click "advanced" and select "go to script (unsafe)"
2) Reauthorise "OAuth"
Important:
We recommend users to make a copy of the Google document/Appscript to trigger a new creation of Google Cloud Platform (GCP) script container in Syensqo's GCP tenant. This will ensure the Appscript to be fully functional throughout the transition period
If this step is not done, the Appscript may be broken in the future when Solvay does a clean up in their GCP tenant.
There is also other way to find what your script ID is:
Step 1: Open Apps Script Editor
- Open your Google Sheets file.
- Click on Extensions → Apps Script.
Step 2: Access the Project Settings
- In the Apps Script editor, click on the Project Settings (⚙️) on the left sidebar.
- Scroll down to the Script ID section—this is useful but not the Client ID.
Step 3: Get the OAuth2 Client ID
If your script is linked to a GCP project, you can find the Client ID:
- In the Apps Script editor, go to Project Settings.
- Under Google Cloud Platform (GCP) Project, click Manage Project.
- In the GCP Console, go to APIs & Services → Credentials.
- Look under OAuth 2.0 Client IDs.
- Copy the Client ID (xxxxxxxxxxxxxxxxxxxxxxxxx.apps.googleusercontent.com).
The best way to get IT support is to use the new
Service One Platform.