Overview

Interno pulls your security data in from the tools you already run. Each tool in the catalogue is a connector, and each set of login details you save against a connector is a credential. One connector can hold several credentials — for example one per region, tenant or business unit — and each of them scans independently.

This guide covers finding a connector, saving a credential, running a scan, and changing a credential later.

Prerequisites

• The Integrations view permission (defence:integration:view)
• The credentials create permission (defence:integration:credentials:create) to add or change anything
• The API details for the tool you want to connect — what these are depends entirely on the tool, and the form tells you which fields it needs

Finding a Connector

Navigation: Sidebar → Admin → Integrations

1. Click Admin in the sidebar, then Integrations.
2. The catalogue appears as a grid of connector cards. Each card shows the tool's logo, its name, the category it belongs to, and chips for the kinds of data it brings in. Hover a card for the tool's full description.
3. To narrow the list, use the Category filter (it opens a searchable list of categories and defaults to All) or type the tool's name into the search box.
4. The catalogue is paged; use the pager at the bottom right when the list runs over one page.

If a connector has already scanned, a status icon sits next to its name on the card. Hover it for Last Scan — when the scan ended and whether it was Processing, Completed or Failed.

Adding a Credential

1. Click the connector's card. A panel slides in from the right showing Tool Credentials — every credential already saved for that tool.
2. Click Add *[tool]* Credentials at the top right of the panel.
3. Fill in the form:

1. Click Save Changes.

> Warning: Pick the Name carefully. It is fixed for the life of the integration — the only way to change it is to delete the credential and create a new one. While you are typing, the form tells you either *Only letters, digits, and . \_ - are allowed (no spaces).* or *This name can't be changed once added.*

What You Can Do With a Saved Credential

Each saved credential appears as a card in the Tool Credentials list showing its name, its non-secret field values, and whether it is active. Secrets are never shown back to you.

The card carries two icons and an actions menu:

• A green tick or a red cross showing whether the credential is active or deactivated.
• A Scan Information icon (once the credential has scanned at least once). Click it for the scan history — each scan's Started at, Ended at and Status, plus the error detail for anything that failed.
• The three-dot Actions menu.

The Actions menu holds:

Editing a Credential

Choose Edit from a credential's actions menu. The full form reopens with everything Interno can safely show you already filled in.

Two things behave differently in edit mode:

• Name is disabled. Hovering it shows *This name can't be changed once the integration is added.*
• Secret fields come up blank and are marked *(leave blank to keep current)*. They are not required. Leave a secret empty and the stored one is kept; type a new value and only that secret is replaced. You never have to re-enter every credential just to change one field.

Click Update to save. If you have not actually changed anything, Interno tells you *No changes to update* and closes the form.

Troubleshooting

My integration name was rejected → The Name may only contain letters, digits, and . _ -, with no spaces, and must be 100 characters or fewer. Use something like aws-prod or azure_tenant1 rather than My AWS Account.

I want to rename an existing integration → You can't. The name is permanent and the save is rejected with *Credential name cannot be changed after creation.* Delete the credential and add a new one under the name you want.

I opened Edit and all the passwords are empty → That is intentional. Secrets are never sent back to your browser. Leave them blank to keep what is stored, or type a new value to replace it.

Saving fails with "Integration limit reached" → Your plan caps how many integrations can be active at once, and the message names your current count and your limit. Deactivate an integration you no longer need, or contact us to raise the limit. The same check applies when you re-activate a deactivated integration.

The connector's card shows a Failed scan → Open the credential's Scan Information icon and read the error detail for the failed run. Expired tokens, changed permissions on the tool's side and unreachable base URLs are the usual causes. Fix the underlying access, then use Start Scan to try again.

Start Scan is greyed out → A scan for that credential is already running. Wait for it to finish.

The Integrations page says I'm not authorised → You are missing defence:integration:view. If instead the page loads but the credentials list is blocked, you are missing defence:integration:credentials:view.

There is no Add Credentials button → Adding needs defence:integration:credentials:create. Ask your administrator.

The catalogue says "No Tools Available" → Your search term or Category filter matched nothing. Clear them and try again.

Need more help? Contact support@zeron.one