> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vidocsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Settings

> Manage members, API keys, audit logs, SCM usernames, integrations, scans, and billing.

Most settings are in the user menu at the bottom of the sidebar. The menu shows only the items that your role and your deployment allow. For the role of each action, refer to [Navigation and roles](/web-app/navigation-and-roles#roles).

## Members

**User menu > Members** shows all users of the organization with their role and their projects. You need the Admin role.

<Tabs>
  <Tab title="Vidoc Cloud">
    **Invite members**

    1. Open the menu (**⋮**) next to **Manage project access**, then select **Invite members**.
    2. Step 1: type an email address and select a role for each person. The default role is **Read Only**. Then click **Manage project access**.
    3. Step 2: select the projects that the new members can access. Then click **Invite**.

    The invitee signs in with the invited email address and clicks **Accept**. Until then, the invitation shows under **Pending Invitations**. Click **Revoke** to cancel it.

    **Remove members**

    1. Select the checkboxes of the members.
    2. Open the menu (**⋮**), then select **Remove member**.
    3. Click **Remove access**.

    **Delete the organization**

    In **Organization danger zone**, click **Delete organization**, then confirm. Vidoc deletes the organization, all projects, and all repositories, and cancels the running scans.
  </Tab>

  <Tab title="Self-hosted">
    Users join the organization when they sign in through your company SSO for the first time. They get the **Developer** role. The operators of your installation set the first admin. The web app has no invitations.

    To remove a user, remove the user in your identity provider.
  </Tab>
</Tabs>

On both deployments, an admin can:

* **Change a role:** select a new role in the **Role** column. You cannot change your own role.
* **Change project access:** select the checkboxes of the members, click **Manage project access**, select the projects, then click **Apply**. Admins have access to all projects.

## API keys

**Project switcher > API keys** manages the keys for the [CLI](/cli/installation) and the [REST API](/api/authentication).

1. Click **Create new key**.
2. Type a **Name**, for example `CI pipeline`.
3. Select the **Expiry**: 1 day, 1 week, 1 month, 6 months, or 1 year.
4. Click **Create**.
5. Copy the token. Keep it in a secret store.

A key belongs to one project. A key has the permissions of the user who created it. For example, a key of a Read Only user cannot change findings.

You need the Developer role or higher to create a key. To delete a key, you need the Admin or Security Engineer role.

For key expiry, rotation, and errors, refer to [API keys](/settings/api-keys).

## Audit logs

**User menu > Audit logs** shows security-relevant events in the organization. You need the Admin role.

Filter by search text, actor, affected user, project, date range, action, outcome, and source. Click an event to see its details.

## SCM usernames

**User menu > SCM usernames** links your username on each source code platform to your Vidoc account. The dialog shows only the platforms that have an active integration in your organization.

| Platform              | Value to type                     |
| --------------------- | --------------------------------- |
| GitHub                | Your GitHub handle, without `@`   |
| GitLab                | Your GitLab username, without `@` |
| Bitbucket Cloud       | Your Bitbucket nickname           |
| Bitbucket Data Center | Your Bitbucket username           |

1. Type your username in the row of the platform.
2. Click **Save**.

To remove the link, clear the field, then click **Save**.

Vidoc uses this link when you reply to a Vidoc comment in a PR, and when you mention the Vidoc bot in a GitHub PR. Without the link, Vidoc tries these methods:

* On GitHub, Vidoc uses the GitHub account that you signed in with (**Continue with GitHub**) when you connected GitHub.
* On GitHub and GitLab, Vidoc matches the email that your platform profile shows with your Vidoc account email. If your profile shows no email, this method does not work.

If no method finds your Vidoc account, Vidoc does not record your feedback. Refer to [Feedback in pull requests](/pull-requests/feedback).

## Integrations

**User menu > Integrations** (or **Settings** in the sidebar) shows one card for each source code platform. You need the Admin role. For the setup of each platform, refer to:

* [GitHub](/integrations/github)
* [GitLab](/integrations/gitlab)
* [Bitbucket](/integrations/bitbucket)

On Vidoc Cloud, the page also has a card for [Slack](/web-app/slack).

## Scans panel

<Note>
  **Self-hosted only.** Vidoc Cloud does not show the Scans panel.
</Note>

**User menu > Scans** shows all scans of the installation. You need the Admin role.

* Filter by project, repository, status, and type.
* The worker health card shows if the scan workers are ready.
* Click a scan to see its execution history.
* **Stop** stops a running scan.

To get help from Vidoc support with one scan, open the scan, then click **Download support bundle** or **Copy support bundle**. You get a JSON file. The browser makes the file from the data on the scan page. It contains no source code and no file contents. It contains scan metadata (IDs, project, repository, branch, commit, status, times), workflow data, and error messages. Vidoc removes values that look like secrets from the error messages. An error message can contain file paths. Examine the file before you send it.

## Billing

<Note>
  **Vidoc Cloud only.** Self-hosted installations do not show Billing.
</Note>

**User menu > Billing** shows the plan of the organization. You need the Admin role.

* **Subscription Status**: the billing type (Stripe or Enterprise), the status, and the date until which the subscription is active.
* **Manage Subscription** (Pro plan): opens the Stripe customer portal, where you manage the subscription and the payment details.
* **Usage This Month**: the number of scans in the current billing period, the monthly scan limit, and the next renewal date. An admin can change the limit.
* **Subscribe to Pro**: shows when the organization has no plan. Without a plan, Vidoc does not scan.

Your account manager manages Enterprise plans. For plans and pricing, refer to [vidocsecurity.com](https://www.vidocsecurity.com).