Authentication mapping at import

First and subsequent imports

Authentication visibility within our platform is typically limited to the workspace level. In most cases, users must map authentications when importing workflows and projects across workspaces. For the first import, users need to select or create a matching authentication based on its requirements. For subsequent imports, most recently used authentication will be highlighted as "last used" in the UI and preselected.

Selection of authentications (legacy method)

During an import, users will be presented with a list of authentications for the required service, categorized as follows:

• **Related Authentications: **These are authentications that were **either last used or created in the same workspace **for this particular import.
• **Other Authentications: **This category includes a list of authentications matching the required service, although there is no certainty that they match the required scope. It is the user's responsibility to verify that the authentication scope is appropriate.
• Last used: If this is not the first time you are importing the project the last used authentication will be clearly indicated and auto-selected

Selection of authentications (new method)

During an import, users will be presented with a list of authentications for the required service, categorized as follows:

• **Matching scopes: **These are authentications for the same service which are an exact match for scopes
• Different scopes: These are authentications for the same service where there is a scopes mismatch which may give problems and represents a risk to your production environment
• Last used: If this is not the first time you are importing the project the last used authentication will be clearly indicated and auto-selected If there is a mismatch of scopes for the chosen authentication a warning will be presented: For Embedded solutions it is particularly important that the scopes for your authentications match. The scopes of an authentication control the specific level of access that an authentication has, and as explained in our guidance on auth slots when you set the scopes in the source workflow of a solution, this sets the scopes for your End Users. Therefore if there are mismatched scopes your End Users are likely to experience issues with their Solution Instances. Please also see our guidance on Breaking changes and Change management (Embedded) for more information.

Creating new authentications

You can also choose to create an authentication on the fly. Note that you should take care to match scopes when creating a new auth. This can only be done through the UI.