Settings

Settings in Venue.sh is where you manage your personal account and, when you have the Admin role, your organization's configuration. Open it from the Settings cog in the upper-right corner of any app screen. The Account page opens by default.

The Users & Teams link next to the cog opens the same settings area on the Users page. See Users and Teams for managing people and teams.

Settings Pages

The left-side menu inside Settings lists the pages available to you. What you see depends on your role and on which features your organization has enabled.

Page	What you manage there
Account	Your profile, password, multi-factor authentication, personal API keys, and active devices.
Users	People in your organization, their roles, and invitations. See Users and Teams.
Teams	Teams and their membership. See Users and Teams.
Assistant	AI providers, provider API keys, and available models. See Assistant.
AI Settings	Repository indexing for search, and general AI usage for summaries and related features. See AI Settings.
Organization	Organization-level features, including Development Insights, and organization deletion.
SSO	Single sign-on for your organization. See SSO.
Legal & Compliance	Legal and compliance information for your organization.

Account

The Account page covers everything tied to you as an individual user rather than to your organization.

Profile - Update your personal information.
Password - Change the password you use to sign in.
Multi-factor authentication - Manage the second factor on your account.
API keys - Create a personal API key to authenticate MCP clients and API integrations. See API Keys below. This is separate from the provider API keys an Admin configures on the Assistant page.
Active devices - Review the sessions currently signed in to your account and end any you do not recognize.

API Keys

An API key lets you authenticate with Venue.sh outside the browser, using your own account permissions instead of a browser session. Use it with MCP clients that cannot complete an interactive OAuth sign-in, or with scripts and other integrations that call the Venue.sh API on your behalf.

You can have one active API key at a time. Creating a new key immediately revokes any existing one, so update your integrations with the new key right away.

To create an API key:

On the Account page, go to API keys and click Create API key.
Enter an optional name to help you remember what the key is for (e.g., "MCP client").
Choose how long the key should last: 30 days, 90 days, or 1 year.
Click Create key.

Copy the key when it is shown. Venue.sh displays it only once, at creation, and cannot show it to you again.

Using an API key

Send the key in the X-Venue-User-Token header on every request. Use the value exactly as it was shown when you created it. Do not put it in Authorization as a Bearer token.

The request runs as you, in the organization that was active when you created the key, with the same permissions as your account.

To confirm the key works, replace YOUR_API_KEY and, if needed, the dashboard URL:

curl \
  -H "X-Venue-User-Token: YOUR_API_KEY" \
  https://dashboard.venue.sh/api/users/me

Use the same header on any authenticated Venue.sh API call from a script or integration.

For MCP clients that cannot open a browser for OAuth, add the header to the server config. In Cursor:

{
  "venuesh": {
    "url": "https://dashboard.venue.sh/mcp",
    "headers": {
      "X-Venue-User-Token": "YOUR_API_KEY"
    }
  }
}

In Claude Code:

claude mcp add --transport http venuesh https://dashboard.venue.sh/mcp \
  --header "X-Venue-User-Token: YOUR_API_KEY"

See Venue MCP Endpoint for OAuth setup when your tool can complete a browser sign-in.

Each key shows its status on the Account page:

Active - The key is valid and has more than 7 days left before it expires (or never expires).
Expires in n days - The key expires within 7 days. Create a new key and update your integration before it does.
Expired - The key can no longer authenticate requests.

To stop a key from working immediately, click Revoke next to it and confirm. This is permanent - any integration using that key stops working right away.

note

An API key carries the same permissions as your account. Anyone with the key can act as you within your organization, so treat it like a password and revoke it if you suspect it has leaked.

AI Settings

The AI Settings page is where Admins control how repositories are indexed for search and how general AI usage is configured. Select it from the left-side menu inside Settings. You need Assistant settings Read permission to view it and Update permission to change it.

General AI Usage - Turn on general AI usage for your organization, including repository summaries and related suggestions. This switch stays off until Repository Ingestion is enabled. Under Advanced, you can reuse a model from an existing Assistant configuration.
Repository Ingestion - Index connected repositories so Venue.sh can search their contents and discover Skills from SKILL.md files. Choose Managed Ingestion (Venue.sh runs embeddings for you) or Bring Your Own Model (your Ollama base URL, model name, and optional API key). Turning ingestion off also turns General AI Usage off.

Click Save Configuration. Changes apply to future ingestion jobs and summary generation, not to jobs already in progress.

For import triggers, embedding options, and how summaries appear on catalog entities, see AI Settings.

Organization

The Organization page is where Admins manage organization-wide options.

Development Insights - Toggle engineering metrics on or off for the organization. See Development Insights.
Delete organization - Permanently remove the organization. Only users with the Admin role can do this.

note

Organization settings require the Admin role. If you cannot see a page described here, your role does not include access to it. Contact your Venue administrator or see RBAC.

Settings Pages​

Account​

API Keys​

Using an API key​

AI Settings​

Organization​

See Also​