Connections in Fusion

Question 1

Can access rights be limited in Fusion directly, or do they need to be limited on the application’s side when a connection is made?

Answer 1

The application-side.

Question 2

What 5 things can be done in the Connections area?

Answer 2

See which permissions were given to Fusion for each connection
Rename Connections
Reauthorize existing connections
Deleted existing connections
Verify that the connection to the service was established successfully

Question 3

How does Fusion notify users before the access rights to a connection expire?

Answer 3

Through an email sent shortly before the access rights expire.

Question 4

Is there a single set of requirements for connections between Fusion and applications?

Answer 4

No. The requirements vary based on the API of the app or web services.

Question 5

What two ways can be used to connect to an app or web service that doesn’t have a specific module created in Fusion for it?

Answer 5

Through either the HTTP or Webhook modules.

Question 6

What 2 types of connection metadata should be set when creating a new connection?

Answer 6

Environment and Authentication

Question 7

What is the Environment type used for when making a connection?

Answer 7

Helps distinguish if the connection is a production or non-production system

Question 8

What is the Authentication type used for when making a connection?

Answer 8

To distinguish if the connection is to a service or personal account.
Some options are User and server-to-server.