Automation Co-Pilot for Business Users FAQ
- Updated: 2024/01/22
Automation Co-Pilot for Business Users FAQ
Answers to frequently asked questions (FAQs) for embedded instances of Automation Co-Pilot.
Disable third-party storage partitioning
Automation Co-Pilot users should disable third-party storage partitioning
from browsers (such as Google Chrome or Microsoft Edge) to enable communication to
the embedded iFrame. Partitioning can cause users to experience
the following situations.
- A user logs in successfully and a window displays for Automation Co-Pilot. The Log In window does not close and the Automation Co-Pilot window displays a spinner.
As of M113, third-party storage partitioning is enabled by default for some users.
However, you can disable storage partitioning by setting a feature flag.
- If this policy is set to Allow Partitioning or unset, third-party storage partitioning might be enabled.
- If this policy is set to Block Partitioning, you cannot enable third-party storage partitioning. This policy can cause disruption with the communication of data between the iFrame and Automation Co-Pilot.
To disable third-party storage partitioning:
- Navigate to the appropriate browser partitioning location:
- For Google Chrome, navigate to:
chrome://flags/#third-party-storage-partitioning
. For more details, see Storage partitioning. - For Microsoft Edge, navigate to:
edge://flags/#third-party-storage-partitioning
. For more details, see Microsoft Edge Developer documentation.
- For Google Chrome, navigate to:
- Select Disabled from the drop-down.
Allow pop-ups from Automation Co-Pilot
If the end users is not seeing the Log In window, it could be that the browser is blocking pop-up windows. The end user should add Automation Co-Pilot as a pop-up exception.
To manage pop-ups in Google Chrome:
- From Chrome, navigate to a page where pop-ups are blocked.
- In the address bar, click Pop-up blocked.
- Click the link for the pop-up you want to see.
- To always see pop-ups for the site, select .