Skip to main content

Organization Settings

The settings page is visible only to users with the Organization manager or Organization Owner role and can be accessed by clicking the Settings menu item in the sidebar.

Workspaces​

Managing workspaces​

In workspace management, workspaces can be created, updated and deleted. To select the workspace to update or delete, click the workspace in the left column on the page. The workspace details will then be displayed.

Adding a workspace​

To add a workspace, click the Add workspace button. A new workspace (Workspace 1) will appear. It can now be configured like any existing workspace.

Configuring a workspace​

The workspace configuration allows for the following parameters to be configured:

  • Workspace name: Click the workspace name in the main configuration window to make it editable. Choose a new, unique workspace name and press the checkmark to save the new name
  • Workspace projects: Check the boxes for all projects that should be in this workspace. If personal projects need to be added, these can be made visible with the Show personal projects toggle.
tip

A project can be assigned to multiple workspaces!

info

A note about project visibility: when a user has access to at least one project in a workspace, the workspace overview cards for all projects in that workspace will be displayed on the workspace overview. The user will not be able to view test execution details for the projects the user is not assigned to, nor will the user be able to select those projects from the project selector.

This can be leveraged to create a high-level dashboard for users that do not require full project access.

Deleting a workspace​

To delete a workspace, select it in the left column and press the Delete workspace button on the bottom right. After confirmation, the workspace will be deleted.
When a workspace is deleted, it will no longer be displayed in the project selection drop down. Users will then have to access the projects through another workspace, or the All projects option in the project selection drop-down.

Projects​

The Projects tab displays all configured projects in the application and provides a shortcut to the project's members project management page.

Adding a project​

To add a new project, click the Add project button, provide a project name and press Create.

info

Projects can be created, but not removed. To render a project invisible to users and disallow collection of results for the project, unassign all members from it.

Managing project members​

Using the Edit members button for each project, the user navigates to the project settings page for the selected project.

Users​

The Users tab provides a list of users in the organization and allows to configure or remove existing users.
The user overview shows:

  • User details: The name and email address of the user.
  • Projects: The projects the user has access to.
  • Actions: The role assigned to the user and available user actions.

To add a new user to your organization, send the user an invite on the Invitations tab. As soon as the user accepts it, the user is added to the organization.

Removing users​

To remove a user, click the user's Remove button. After confirming the warning, the user will be removed from the organization.

Assigning/Revoking administrative rights​

To assign Administrative rights to a user, choose the appropriate role in the user's row. After confirming the action, the user's role will be updated to the selected value.

info

At least 1 user with the organization owner role should always remain present, to prevent lock-out. This is enforced by the application.

Invitations​

Sending an invitation​

To invite a new user to the organization:

  • Click Add Invitation
  • Enter the email address of the user you want to invite.
  • Select the projects the new member should have access to.
  • Click Send Invitation.

After the invitation has been sent, it is displayed on the Invitations tab and in the user's Pending Invitations overview. A confirmation message is displayed when the invitation was sent successfully.

Managing pending invitations​

The Invitations tab shows all pending invitations for the organization.
For each pending invitation, Orangebeard shows the invited email address and the projects included in the invitation.

Click Revoke to cancel a pending invitation.

Settings​

On the System Settings tab, system-wide configuration parameters can be adjusted and stored.

  • Today Offset: Specify the start time for the today filters. Defaults to midnight 00:00. Choosing another value here will filter from the given time instead of midnight.
  • Skip Weekend: if enabled, the today filter will skip weekend days in its cutoff. I.e. when test run nightly, but only on weekdays, the today filters will include friday night's tests on monday.

AI Model​

The AI Model tab allows the organization-wide AI assistant configuration to be managed. The configuration applies to all assistant sessions in the organization.

LLM Configuration​

Configuring the LLM provider

This video is hosted on YouTube. Playing it may transfer data to YouTube and set cookies. Click 'Accept' below to accept and enable all YouTube videos on this site.

The LLM Configuration tab displays the current token usage and budget status, and allows the default AI provider settings to be configured.

The following information is displayed:

  • Tokens used today: The number of tokens used by the assistant today.
  • Daily budget: The maximum number of tokens that can be used by the assistant per day. When no budget is configured, the value is displayed as Not set.
  • Budget status: Shows whether the current usage is within the configured budget.

Configuring the provider​

To configure the AI model, select a provider from the Provider dropdown.

The available providers are:

  • Orangebeard
  • Anthropic
  • Azure-openai
  • Gemini
  • Mistral
  • Openai

When Orangebeard is selected, the system default assistant configuration is used. The default configuration uses Gemini 3.1 Flash Lite on VertexAI, hosted in the EU.

For custom providers, the following parameters can be configured:

  • Model: The model name that should be used by the selected provider.
  • API Key: The API key used to connect to the selected provider. Leave this field blank to keep the existing encrypted key unchanged.
  • Max Output Tokens: Limits the output to the specified amount of tokens. Defaults to 4096.
  • Temperature: The model temperature. Defaults to 1.
  • Daily Token Budget: Limits the total number of tokens that can be used by the assistant per day. Leave this field blank to allow unlimited usage.

After changing the configuration, click Save LLM Config to store the settings.

info

Configured API keys are encrypted when stored. When updating other LLM settings, the API key field can be left blank to keep the existing key.

Custom Assistant Instructions​

The Custom Assistant Instructions field can be used to add organization-specific context for the assistant.

Examples of useful instructions are:

  • How work items, defects, or test cases are organized in your project
  • Team conventions for titles, attributes, or severity levels
  • Paths or links to relevant code repositories or documentation
  • Domain-specific terminology the assistant should understand

These instructions are appended to the default system prompt and apply to all assistant sessions in the organization.

Using the configured assistant​

After the LLM configuration is saved, the assistant uses the configured provider and model when AI Support is opened.

MCP Servers​

The MCP Servers tab allows Model Context Protocol servers to be registered for the organization. MCP servers make external tools available to the assistant, such as repository, issue or pull request tools.

Registered MCP servers apply to the organization and can be used by the assistant when handling requests.

Configuring MCP Servers

This video is hosted on YouTube. Playing it may transfer data to YouTube and set cookies. Click 'Accept' below to accept and enable all YouTube videos on this site.

Registering an MCP server​

To register a new MCP server, open the MCP Servers tab and click + Register new server.

The following fields can be configured:

  • Server Name: The name used to identify the MCP server in Orangebeard.
  • Server URL: The URL of the MCP server.
  • Custom Headers: Optional headers that are sent to the MCP server, provided as a JSON object.

Example custom headers:

{
  "Authorization": "Bearer YOUR_TOKEN"
}

Click Register MCP Server to add the server.

info

Custom headers are encrypted when stored. After encryption, they will no longer be displayed in the UI.

info

If the MCP server requires OAuth, a new browser tab opens to finish the authorization.

Editing an MCP server​

Select an existing server from the list to edit its configuration.

The following settings can be updated:

  • Server Name
  • Server URL
  • Custom Headers

Click Save Changes to store the updated configuration.

The authorization status is shown in the top-right corner of the server details. When a server has not been authorized yet, it is displayed as Not authorized.

Deleting an MCP server​

To remove an MCP server, select the server from the list and click Delete Server.

Available Tools​

The Available Tools tab shows the tools that are available to the assistant.

Tools are grouped by MCP server. For example, a GitHub MCP server can expose tools for repositories, issues, pull requests, branches, commits, releases and code search.

Orangebeard also provides its own tools, such as tools for retrieving test runs, test results, attachments and historical analyses. These tools are always available to the assistant and will be called on behalf of the user chatting with the assistant.

Ask Orangebeard