# Hide Vault Connection Fields

Some connectors ask consumers for more than your application needs. NetSuite, for example, has optional fields such as Default Subsidiary, Integration user time zone (optional) and Attachments folder ID. If your application doesn't use them, you can hide them so consumers only see the fields that matter to you.

You choose which fields are visible per connector, in the [Apideck dashboard](https://platform.apideck.com/). The setting applies to your application only. Other applications that use the same connector are unaffected.

## Hide fields in the dashboard

1. Open the [Apideck dashboard](https://platform.apideck.com/) and go to **Configuration**.
2. Select the Unified API (for example **Accounting**), then the connector (for example **NetSuite**).
3. Find the **Fields visible in Vault** section. Checked fields are visible to consumers. The section only appears when the connector has at least one optional field that can be hidden.
4. Untick the fields you want to hide.
5. Click **Save settings**.

![The Fields visible in Vault section of a connector's configuration](/guides/hide-vault-form-fields/fields-visible-in-vault.png)

Each field shows the same help text your consumers see in Vault, so you can check what a field is for before you hide it. To show a hidden field again, tick it and save.

## Which fields can be hidden

Only optional fields can be hidden.

- Required fields, and fields required for authorization, are always shown checked and disabled with a "Required" label. This guarantees consumers can always complete the connection.
- Fields the connector already hides on its own are not listed.

To check which fields of a connector can be hidden, call [`GET /connector/connectors/{id}`](/apis/connector/reference#operation/connectorsOne). For each setting it returns `required`, `required_for_authorization`, `hidden` and `description`. There, `hidden` means the connector itself hides the field for every application; your own choices aren't reflected in it.

## What consumers see

Hidden fields are no longer shown on the connection form in Vault. The Vault API still returns them in the connection's `form_fields`, with `hidden: true`.

## Things to know

- **Hiding is display-only.** A value already saved on a connection keeps applying after you hide the field.
- **You can still set hidden settings through the Vault API.** Send them with `settings` in [`PATCH /vault/connections/{unified_api}/{service_id}`](/apis/vault/reference#operation/connectionsUpdate). This lets you configure a hidden field for one consumer yourself.
- **It is not a Vault session setting.** The session setting [`hide_resource_settings`](/guides/vault-react#customizing-the-session) hides the resource configuration in Vault for a single session. Hiding connection fields applies to your whole application, for one connector.

## Example: token-based authentication on NetSuite

An application that only uses NetSuite token-based authentication needs Account ID, Access token ID, Access token secret, Consumer key and Consumer secret. It can hide Default Subsidiary, Integration user time zone (optional), Attachments folder ID and the Bank Feed RESTlet Script ID and Deploy ID, so consumers only fill in the credentials.

## Optional does not always mean unused

Only hide fields you're sure none of your consumers need. Take NetSuite:

- **Consumer key and Consumer secret** are optional only when the account uses the Apideck Integration Connectivity bundle. If you hide them, consumers who connect with their own integration record can't complete the connection.
- **SuiteTax enabled** tells Apideck whether the NetSuite account uses SuiteTax. If you hide it, consumers can no longer set it in Vault. A value already saved keeps applying, but a consumer whose account uses SuiteTax and who hasn't set it yet stays on legacy tax, so tax data is read and written incorrectly.

## Related guides

- [Vault JS](/guides/vault) and [Vault React](/guides/vault-react) to embed Vault in your application
- [Vault Connection States](/guides/connection-states) to understand the connection lifecycle