Skip to main content

Views and Visibility

AI-Corporate adapts the application to your role, your environment, and your personal settings. As a result, you may not see a button, model, tool, or integration that someone else does see.

That is usually not an error. AI-Corporate only shows items that are currently available, allowed, and relevant for your account.

Why doesn’t everyone see the same thing?​

The interface is built from multiple layers:

  1. Your role: employee, admin, board admin, or super admin.
  2. The environment: organization, branch, or tenant settings.
  3. Restrictions and access: for example, whether employees are allowed to use certain features.
  4. Available models and providers: which AI models are enabled by the environment.
  5. Tool settings: which tools are visible, automatically available, on, or off.
  6. Integrations and MCP access: whether integrations are allowed and whether you are logged in with the correct provider.
  7. Your personal preferences: for example the Starter or Default view, default provider, and personal tool exceptions.
  8. The current chat context: some buttons disappear or are disabled during an ongoing response, in an assistant, in document mode, or with a specific integration.

So a missing button does not automatically mean you have no rights. Sometimes the feature is turned off in your environment. Sometimes you are using the Starter view. Sometimes the feature only belongs to another model or another provider.

Starter and default view​

Users with an employee or admin account can choose in Preferences how many options they want to see in the app. In the app, these modes are called:

  • Starter: calm view with fewer options.
  • Default: all options and settings are visible.

Default​

In Default you see the full interface within what your role and environment allow. For example, you can:

  • choose the default AI provider in Preferences;
  • set general instructions and extra instructions;
  • use the model switcher in the chat settings and in responses;
  • use the direct input modes for chat, text to image, text to audio, and documents if available;
  • open the extra options for chat;
  • switch on the home screen between sections such as links, files, images, and statistics;
  • start tools and integrations from the home screen;
  • set personal tool exceptions;
  • manage drive integrations if you are logged in with the correct provider.

Starter​

In Starter, the regular chat remains available, but AI-Corporate hides a number of advanced options. This makes the interface calmer.

In this view, the following are hidden, among others:

  • the default AI provider in Preferences;
  • general instructions, extra instructions, and personal response style;
  • the model switcher in the chat side panel and in responses;
  • the direct input mode buttons for image, audio, and documents;
  • the chat extra-options button;
  • the dashboard switcher for links, files, images, and statistics;
  • the tools and integrations block on the home screen;
  • the button to create a new assistant from the home screen;
  • personal tool exceptions;
  • drive integrations.

Not everything disappears. History and available assistants may still be visible. Some chat-specific settings or tools may also still appear in an existing chat context, depending on the selected chat, assistant, or workflow.

In Starter, the buttons to stop a response, copy it, read it aloud, regenerate it, and view sources remain available. Only model selection and export to Word, PowerPoint, or PDF are hidden.

Why don’t I see the model switcher?​

The most common reason is that Starter is enabled.

The model switcher is hidden in Starter:

  • in the chat side panel;
  • in previous responses;
  • in parts of the chat window where you would normally switch models.

Do you want to choose models or try a response again with a different model? Then set the view to Default via Preferences.

Roles and role view​

AI-Corporate uses roles to determine which parts of the application are loaded. A role is not the same as a full job description. The final view also depends on permissions, environment, organization or branch scope, and personal settings.

Employee​

An employee account uses the regular work environment: chatting, using available assistants, viewing history, managing files, and setting personal preferences.

Whether an employee sees extra features, such as MCP integrations, voice chat, or creating documents, depends on the environment settings and any individual access.

Admin​

An admin account has access to the management environment within its own organization or branch scope. Which admin panels are visible is still filtered by permissions and scope.

An admin can also view the app as an employee. In that role view, admin-specific parts disappear from the regular user interface, so the admin can better see what employees experience.

Board admin​

A board admin has a broader administrative role than a regular admin. This role may see settings at environment or organization level that are not always available to regular admins, such as broader environment settings, permissions, or central AI settings.

A board admin can also look along in role view as admin or employee. That means the same user can see different interfaces depending on the active role view.

Models and providers​

The available language, image, and speech models come from the model configuration of the environment. An organization can decide which providers and models are available.

As a result, the following can happen:

  • OpenAI, Claude, Google, or European AI are not all visible;
  • a model mentioned in a news item or example is not in your environment;
  • image models or speech models differ from language models;
  • an assistant works with a fixed model;
  • a tool is not available for the selected model.

The built-in Google and Microsoft integrations are provider-independent. They can be used with OpenAI, Claude, Gemini, and Mistral, as far as the chosen model supports tool use.

Tools: automatic, on, off, and not visible​

Tools can be configured in different ways.

Automatic​

The tool is available, but the AI decides for itself whether the tool is needed. This is the normal setting for many tools.

On​

The tool is explicitly on for you or for the chat. AI-Corporate then tries to make the tool available more directly.

Off​

The tool is visible as an option, but not available for you or for this chat.

Not visible​

This is the strongest restriction. If an admin sets a tool to Not visible, the tool disappears from the chat window and from your personal preferences. You cannot turn this tool on yourself.

Personal tool settings are therefore only exceptions to what the environment has made visible. They cannot bring back a hidden tool.

Provider-specific tools​

Not every tool works with every AI provider.

Examples:

  • OpenAI has its own native tools, such as web search and code interpreter.
  • Claude has its own tools, such as web search, fetching web pages, and running code.
  • Google has its own native tools, such as Google Search, URL context, Maps, and code execution.
  • Some general tools work provider-independently.

So when you switch model provider, the list of tools can change. That is expected behavior. AI-Corporate adjusts the tool settings to the provider associated with the selected model.

For Google-native tools, there is an additional detail: they cannot always be combined with general function tools. If Google-native tools are active, AI-Corporate can disable other tools in that round to make the model call work technically.

Integrations and MCP tools​

Under Tools on the home screen, different kinds of integrations may appear:

  • built-in AI-Corporate tools;
  • personal MCP servers;
  • organization-wide MCP servers;
  • built-in integrations such as Google Calendar, Google Drive, Gmail, Microsoft Teams, Outlook, and SharePoint.

Whether you see them depends on several conditions.

MCP access​

The environment determines whether employees may use MCP integrations. In addition, an admin can set an individual exception per employee:

  • allowed;
  • not allowed;
  • default, meaning follow the environment setting.

If MCP access is off, you will not see a button to add an MCP server, and organization or personal MCP integrations disappear from your view.

Logged-in provider​

Some connectors are only visible if you are logged in with the correct provider.

Examples:

  • Google Calendar, Google Drive, and Gmail require separate Google consent.
  • Outlook, Microsoft Teams, and SharePoint require separate Microsoft consent.

Your regular AI-Corporate login may use email and password. The connector opens a separate OAuth sign-in and then stores the consent server-side.

For some integrations, you need to give additional consent. A regular login is then not enough, because the connector needs extra permissions, for example to read calendars or search files. AI-Corporate asks for that consent when you start the integration.

Desktop and local MCP​

Local MCP servers and local file access belong to the desktop app. If you use the web version, you will not see desktop-specific features.

Chat context: why is something temporarily gone or disabled?​

Some parts are only temporarily hidden or disabled.

That can happen when:

  • a response is being generated at that moment;
  • you are in a controlled assistant;
  • you are working with a fixed prompt type, such as document mode;
  • a previous chat has saved its own tool setting;
  • a message is being regenerated;
  • the selected local model does not support tool use;
  • a tool is not supported for the selected model;
  • you are on mobile and the layout is more compact.

In that case, wait until the response is ready, open a new chat, or check whether you are in an assistant, document mode, or integration chat.

Admin settings that affect visibility​

Admins can influence visibility in different places.

Restrictions​

In restrictions, an environment can set whether employees have access to features such as:

  • MCP integrations;
  • voice chat;
  • creating documents;
  • usage limits.

In addition, admins can set exceptions for individual employees.

Models​

In model settings, the environment determines which language, image, and speech models are available. If a provider or model is not included there, it will not appear in the model switcher.

Tools​

In tool settings, you can set per provider whether tools are automatically available, on, off, or not visible. Not visible is especially important: users cannot restore such a tool themselves.

Integrations​

Built-in Google and Microsoft integrations and organization-wide MCP servers are managed separately. They only appear if they are enabled for the environment and the user meets the access conditions.

FAQ: Help! I can’t see something​

I don’t see the model switcher​

Check whether you are using the Starter view. Go to Preferences and set the view to Default. If you do not see that setting, your role or environment may determine which view you get.

I don’t see Assistants in the menu​

In Starter, Assistants is hidden from the main menu. Available assistants may still be visible on the home screen. Set the view to Default if you want to open the separate assistants page from the menu.

I don’t see Tools or Integrations on the home screen​

In Starter, the tools and integrations block on the home screen is hidden. Set the view to Default. Then check whether your environment allows MCP access and tools.

I don’t see a certain tool​

The tool is probably set to Not visible in the environment, is not available for the chosen provider, or does not fit your current chat context. You cannot restore hidden tools yourself via preferences.

I see a tool, but it does not work in this chat​

The tool may be disabled for this chat, may not match the selected model, or may be temporarily unavailable during generation. Try starting a new chat and check your tool settings.

I don’t see Google Calendar, Gmail, or Google Drive​

These integrations must be enabled by the environment. Open Preferences → Tools, turn on the desired Google integration, and complete the separate Google consent flow.

I don’t see Outlook, Teams, or SharePoint​

These integrations must be enabled by the environment. Open Preferences → Tools, turn on the desired Microsoft integration, and complete the separate Microsoft consent flow.

I can’t add an MCP server​

MCP access may be turned off in the environment for your role. In addition, an admin may have set an individual exception for your account to not allowed. Without MCP access, the Add tools button does not appear in Preferences → Tools.

My colleague sees more models than I do​

First check whether you both use the Default view. After that, the difference may be caused by a different role, organization, branch, active chat context, personal preference, or environment.

I don’t see a model that is mentioned in an article or training​

The documentation may mention examples of models that are not enabled in every environment. The admin determines which models are available in your environment.

A model is gray or cannot be selected​

Check whether the model is available through the environment and fits your view. An active integration does not gray out other models; it is available with any suitable model that supports tool use.

I don’t see General instructions or Extra instructions​

These settings belong to the extended preferences. Set your view to Default. In Starter, these advanced preferences are hidden.

I don’t see Drive integrations​

Drive integrations are only available in Default. In addition, you must be able to log in with the correct provider or grant consent again.

I don’t see local AI or local MCP​

Local AI, local file access, and local MCP servers belong to the desktop app. These parts do not appear in the web version.

I don’t see something on mobile​

On small screens, AI-Corporate uses a more compact layout. Open the side menu via the hamburger icon or try the same page on a larger screen.

What should I tell support or my admin?​

Give as much detail as possible about:

  • which button, tool, integration, or model you are missing;
  • where you expected to see it;
  • whether you are an employee, admin, or board admin;
  • whether you are using Starter or Default;
  • which login provider you are signed in with, for example Google, Microsoft, or email/password;
  • whether you are working in a regular chat, assistant, document mode, or integration chat.

With that information, an admin can usually quickly check whether it is a personal preference, role, environment setting, or technical limitation.

On this page