The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to troubleshoot the instance where a user cannot import an automation pack.
The information in this document is based on Tidal Enterprise Orchestrator (TEO) 2.1 or later.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Normally, a user can import an automation pack by going to Administration > Automation Packs, and right-clicking and selecting Import.
A common issue with importing is for the Import option to be greyed out or disabled.
Complete these steps in order to resolve this problem:
Close down the TEO Master UI, and stop TEO.
Make sure the user is a local administrator and a TEO administrator.
Add the permission they are missing to their profile.
Restart TEO, and Reopen the Master UI.
The user should now be able to import automation packs.