Date: Fri, 29 Mar 2024 00:56:40 -0700 (PDT) Message-ID: <1724344627.735.1711699000620@docs-lju.6connect.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_734_1472628726.1711699000259" ------=_Part_734_1472628726.1711699000259 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Before you begin creating Workflows in your new ACP instance, there are = a few items to consider:
After installing/gaining access to your new ACP instance, once of the fi= rst steps that should be taken is to add appropriate users to ACP.
ACP gives all users equal status ("admin" level) in the system, so consi= der carefully who should have access to ACP, and add only the necessary use= rs.
For information on how to add and manage users, see User Management.
ACP provides out-of-the-box connectors supporting six services. Review w= hat services you may have access to, and ensure that you have correct insta= nce name/url/credential information for each service.
In addition to the provided connectors, ACP allows for custom generic co= nnectors to be created. See Connec= tors for more information.
Supported Connector Services:
As ACP utilizes available APIs from the supported services, ensure that = users that will be creating or editing ACP Workflows have access to, and fa= miliarity with, the associated connector API systems and reference document= ation. For complicated Workflows, it may help to pre-plan which steps, endp= oints, and conditions are needed for a Workflow prior to creating it in ACP= .
AWS Docu= mentation: https://d= ocs.aws.amazon.com/index.html
To learn how to work with ACP, check out our Quick-start Tutorials:
For detailed information on working in ACP, see the ACP User Guide: