Settings - Preferences
Here, you can configure settings that apply specifically at the customer level.
Brand kits — logos, colors and fonts — have their own menu, Settings > Branding. Learn more: Settings - Branding
Team global settings
The Team global settings card shows the five customer-wide team options: who can see resources without a team, what users without a team can access, and whether users in teams can create items directly in the root folders. You can change them here or with the cog icon in the top right corner of the Teams tab.
Learn more: Customer level - Global team settings
Force two-factor authentication
When enabled, all users under this customer will be required to set up two-factor authentication (2FA) before they can access the system.
- Users who have not yet configured 2FA will be prompted to complete the setup on their next login.
- This setting overrides any user-level 2FA preferences — individual users cannot opt out when this is enabled.
Learn more: Setting up two-factor authentication
AI assistant access (MCP)
Introduced in version 2.1, Wallboard supports the Model Context Protocol (MCP), which lets external AI assistants (such as ChatGPT) connect to your Wallboard account and act on your behalf. Access is controlled at two levels: the customer (organization) level for the whole account, and the individual user level for each person.
Customer-level access
At the customer level, the AI agent access (MCP) card in Settings > Preferences controls:
- Allow MCP access - whether AI assistants are allowed to connect through MCP for this customer at all.
- Allowed actions - the default access new users receive when their account is created (changes do not affect existing users).
If MCP access is turned off at the customer level, no user under the customer can connect an AI assistant, regardless of their individual settings.
Per-user access
In the user's create and edit window, the AI agent access (MCP) section controls whether that user may connect an AI assistant (Allow MCP access) and which Allowed actions it may perform:
-
Read — the assistant can read data (devices, content, datasources, and so on).
-
Create/Update — the assistant can create new items and modify existing ones (one option covers both).
-
Delete — the assistant can delete items. Off by default — it must be enabled deliberately.
-
Administrator users start with MCP access disabled and must enable it explicitly.
-
After you change a user's MCP permissions, the change can take up to 5 minutes to take effect.
Learn more: Connect an AI assistant (MCP)
AI API keys
The AI API Keys section lets you configure your own third-party AI provider credentials at the customer level. These keys are used by AI-powered datasource features such as the Web Scraper and AI Datasource types.
You can provide a key for either supported provider:
- xAI API Key
- Google Gemini API Key
By default, AI-powered datasources use shared Wallboard platform keys, which are rate-limited. Provide your own key and all AI requests use it instead, with no platform-imposed limits — usage is then billed directly by the provider. Leave both fields empty to keep using the shared keys.
The section shows the customer's current monthly and hourly AI token usage. Once at least one of your own API keys is set, you can also set an Hourly Token Limit and a Monthly Token Limit to cap the customer's usage; until then both fields stay disabled. Use Clear key to remove a stored key.
Learn more:
User Interface Profiles - Customer-Level Permissions
With these settings, you can restrict UI elements customer wide (e.g., hide items that are otherwise shown in a preset).
- However, user-level permissions can override these restrictions.
- You can assign User interface profile settings to your customer from Preferences > Other settings > User interface profiles
Learn more: User Interface Profile settings
Vistar Media
- Vistar Media network id: Your unique network identifier from Vistar
- Vistar Media api key: Your authentication key from Vistar
Learn more: Vistar Media