An embedded document editor can behave differently from the same service opened directly. The outer portal and the embedded service may use different domains. Before deleting browser data, determine whether the failed step is specifically the connection between them.

Compare the two entry points

Open the service through its usual trusted address and confirm the intended account can view a harmless document. Return to the portal and repeat the embedded action. Record the outer portal address, embedded service name and exact failure. Do not include document contents or a password in the note.

If direct access fails too, investigate that account or service first. If direct access works, inspect Chrome’s third-party-cookie indication on the portal. Google explains that embedded services can need access to information saved under their own site.

Where a verified business workflow requires it, use the address-bar control to allow third-party cookies temporarily for the current site. Reload and repeat the same embedded task. Avoid changing several privacy controls during this comparison; otherwise an improvement will be hard to attribute.

Keep the exception understandable

Google currently describes a regular-window temporary allowance as lasting 90 days unless switched off sooner. An Incognito allowance lasts for that Incognito session. Record the mode and date, rather than assuming an exception has identical lifetime everywhere.

Success means the intended account opens the expected embedded content and the task completes. It does not mean every future sign-in problem has been solved. If there is no improvement, reverse the test and report the two-entry comparison to the portal administrator.

For a continuing exception, review the actual site entry under Chrome’s third-party-cookie settings. A wildcard can cover more subdomains than one address. Use only the scope the service requires, and remove stale exceptions after the workflow changes. Keep any administrator-enforced policy in place while support investigates.

Sources: Chrome documentation.