Docs
Sign in

AutoBoarding browser extension

Use the UnitX AutoBoarding Chrome extension to start and control migrations, and what it deliberately cannot do.

The UnitX AutoBoarding extension for Chrome is a shortcut for migrations. From its popup you can start a migration from Trello, Jira Cloud, ClickUp or Asana, see what discovery found, and start, pause, resume or cancel migrations — without opening UnitX. Everything it does is also possible in UnitX itself, and approving a migration always happens there.

What it does — and does not do#

It canIt cannot
Sign you in through UnitX’s own consent pageAsk for, see or store your password
Start a migration and run discoveryApprove a migration — it is not given that permission
List your migrations and their progressConnect a source tool (that needs credentials, entered in UnitX)
Start an approved migration, pause, resume and cancelRead Trello, Jira, ClickUp or Asana pages in your browser
Show what a connector cannot bring acrossRead other tabs or your browsing history

When you install it, Chrome shows the only permissions it requests: sign-in (identity), storing its sign-in token (storage) and access to your UnitX address. It has no access to any other site.

Before you start#

  • Your organization has to provide the extension: it is built for your UnitX address and registered in UnitX as an application. Ask your administrator where to install it from.
  • The source tool must already be connected under Integrations.
  • You need the migration permissions below in your UnitX organization.

Permissions

migration.viewmigration.connectmigration.managemigration.cancel
These are the permissions the extension asks to use on your behalf. What you can actually do through it is limited to the ones your role also holds. It never asks for migration.approve.

Sign in#

  1. Open the extension

    Select the UnitX AutoBoarding icon in Chrome’s toolbar.
  2. Choose Sign in with UnitX

    A UnitX page opens in a real browser window. Sign in there as usual if you are not already signed in.
  3. Approve the extension

    The consent page lists what the extension will be able to do. Choose Allow. The popup now shows your migrations.

Note

Your sign-in lasts about an hour. When it expires, the extension asks you to sign in with UnitX again.

Start a migration from the extension#

  1. Choose Migrate from another tool

    In the popup.
  2. Pick the Source platform and Connection

    Sources that are not enabled for your organization cannot be chosen. If you have no connection yet, the popup says No connected source platform yet and offers Connect a platform, which opens UnitX.
  3. Choose Find what’s there

    The extension creates the migration and runs discovery. This only reads; nothing is written to your organization.
  4. Review and approve in UnitX

    The popup shows Ready to review with the readiness percentage, counts of what was found and what won’t come across. Choose Review and approve in UnitX to open the migration’s page, where approval happens.

Watch and control migrations#

The popup lists your migrations with their source and status. Depending on the status, each offers:

Start
For a migration that is ready and has been approved in UnitX.
Pause
For a running migration.
Resume
For a paused migration.
Cancel
For any migration that has not finished.
What won’t come across
The connector’s list of features it cannot migrate, with reasons.
Details in UnitX
Opens the full migration page in UnitX.

Migrations keep running if you close the popup or the browser — they run in UnitX, not in the extension. Open in UnitX at the top of the popup opens UnitX in a tab.

For administrators: providing the extension#

Register it as an application#

The extension signs in as an OAuth application. Because a published extension can be unpacked and read, it holds no client secret: it is registered as a public client and uses PKCE instead. Register it through the UnitX API as a public client, with the redirect URL Chrome assigns to your extension, and give the resulting client ID to whoever builds the extension package for your UnitX address. See OAuth applications.

You can revoke the extension for everyone at any time from Governance → Applications.

“This extension has no client id configured”

The package was built without being registered as an application in UnitX. Ask your administrator for a correctly built package.

A source platform is greyed out.

It is not enabled for your organization yet. See which tools you can migrate from.

Why can’t I approve from the extension?

Approval authorizes writing data into your organization, so it happens in UnitX. The extension is never given the approval permission, so no version of it can approve.

Still stuck? Search the docs with ⌘K, open Help inside UnitX, or contact support.