Managing Integrations

Settings > Integrations is where you set up and monitor every integration in your organization. Each configured integration is its own row in a single list: a Wiz integration that feeds the Risk Register and a Jira integration that creates tickets sit side by side, each with its own name, type, and settings.

Viewing the page requires integrations:read. Adding, changing, testing, and removing integrations requires integrations:manage. See Managing Roles.

The integrations list

Each row shows:

• The integration’s logo, your name for it, and the product and type badge underneath: RSK for risks, INC for incidents, TKT for tickets, and NTF for notifications.
• Tags, for integrations that import risks or incidents (see Tags).
• The Enabled switch, which turns the integration on or off.
• The AI scoring switch, for integrations that import risks or incidents. When it’s on, imported records are scored by AI on ingestion and rescored when their description changes.

Use the type pills above the list to show only risks, incidents, tickets, or notifications. Select the active pill again to show everything.

The switches save the moment you flip them, whether the row is open or collapsed. If an integration’s connection has a problem, a warning icon appears next to Enabled. It is amber when the provider has rejected or suspended the credentials, and muted when the connection is disconnected or still pending. Hover over the icon to see the reason. A problem shows up here in the list, so you don’t discover a broken connection only when records stop arriving.

Adding an integration

1. Select Add above the list.
2. Pick a product and a type from the grid. Search by product, name, or field if the list is long. A product that supports more than one type, such as Jira, can be added once for each.
3. Choose the connection the integration should use from the Connection list, or select Add a connection… to create one (see Connections).
4. Complete the settings the integration needs, give it a name, and save. You’re asked for a name before anything is stored.

An integration can’t be enabled until its connection is active and its secret has been entered. If it isn’t, the Enabled switch explains what’s missing. Once saved, an integration keeps its connection.

Each integration page under Available Integrations lists the connection details and permissions that product needs.

Editing an integration

Select a row to open it in place. Everything you can change appears on the card:

• Name. Click the title to rename it.
• Settings. The fields specific to that integration, such as a query, a channel, or a project.
• Connection. The integration’s saved connection is shown locked beside an Edit button, which opens the connection’s details.
• Tags. Described below.

As you edit, changed fields are outlined, undo and redo become available, and Save appears only when you have unsaved changes. The Enabled and AI scoring switches are not part of Save; they apply immediately.

Test checks the integration’s connection and settings against the provider on demand and shows the result in a panel you can dismiss. For an integration whose connection was suspended, a successful Test also resumes it. Delete sits beside Test and asks for confirmation before it removes the integration.

Connections

A connection holds the details an integration needs to reach a provider: its URL, API key, or other credentials. Connections are separate from the integrations that use them, so one connection can serve more than one integration.

Select Manage connections above the list to see them all. They are grouped by product, with search once the list grows. Each has a Connection Name, which is also how the connection appears in the integration’s Connection list. Secrets are never displayed after they are saved. They show as masked values and are replaced only when you enter a new one.

Saving a connection doesn’t contact the provider, so a connection the provider would reject can still be saved. Use Test to check it, either from the connection form or from an integration that uses it. The next sync also records any rejection as the connection’s health, which is what the warning icon in the list reflects.

A saved secret is only ever tried against the address it was saved with. If you change a connection’s URL, enter its secret again before you test it.

Tags

Integrations that import risks or incidents have a tags field. Open the row and choose from your organization’s existing tags, typing to search, or type a new name to create one. Every record the integration imports is created with those tags, so you can filter the Risk or Incident Register to everything that came from one integration. For example, tagging a Wiz integration “Wiz” or “Cloud” lets you see all of its findings with a single filter.

Tags are applied only as a record is first imported:

• Records already in your register are not tagged retroactively.
• Tags aren’t reapplied on later syncs, so a tag someone removes from an imported record stays removed.
• Changing an integration’s tags affects only the records it imports afterward.

Ticketing and notification integrations don’t import records, so they have no tags field. To learn more about tags, see Item Tags.

Integration users

Records created by an integration are opened by an integration user, a service account the platform creates for the connection. It is named for the product and the connection, for example “Wiz Production”, so a risk or incident shows which connection brought it in. Integration users appear in the Service Accounts table on Settings > Team, with a link back to the integration.

• Renaming a connection renames its integration user.
• Connections to the same product need names that are distinguishable once combined with the product name. A name that would read the same as another connection’s, such as “Prod” next to “Wiz Prod”, is refused.
• Integrations set up before this naming was introduced may still read “Wiz Integration”.

See Service Accounts for how integration users behave when an integration is removed or reconfigured.