For the complete documentation index, see llms.txt. This page is also available as Markdown.

MaiGPT Role Usage Permissions

Configure the MaiGPT models, tools, skills, connectors, and built-in features available to different roles.

Organization administrators can restrict the models, tools, skills, connectors, and built-in features available in MaiGPT by role. When a member has multiple roles, the system combines the permissions granted by each role. The member can use an item as long as at least one role allows it.

Owners are not subject to role usage scope restrictions. The settings below apply to both default and custom roles.

Use Case

An IT manager wants the customer service role to use only company-approved models. They open the role's MaiGPT usage permissions, clear "All" under "Available Models," and select the approved models. The card immediately shows "Partial" and the number selected, and a success message appears. Tools, skills, and connectors retain their own "All" settings; changing the model scope does not restrict them.

Configure a Role's MaiGPT Usage Scope

1

1. Open Role Permissions

Go to Organization Settings → Organization Overview, then select Edit Role Permissions in the "Management" section.

2

2. Select a Role

Find a default or custom role in the role list, select Edit on the right, then open the Assign MaiGPT Usage Permissions tab.

3

3. Set the Available Scope

Under "Available Scope," configure Available Models, Tools, Skills, and Connectors separately. Each card has its own "All" checkbox. Click a category name to expand or collapse its list of items.

Category setting
What members can use

"All" selected

Every available item in the category; the list is grayed out

"All" cleared, some items selected

Only selected items; the card shows "Partial" and the number selected

"All" cleared, no items selected

This role grants no access to the category; the card shows "None"

To restrict a category, clear its "All" checkbox, then select the permitted items from the list that opens automatically. Selecting "All" again clears individual selections. If you clear "All" later, you must select the items again.

Four available-scope cards, each with its own All checkbox
Configure Available Models, Tools, Skills, and Connectors separately
The card shows None when All is cleared and no available models are selected
When no model is selected, this role grants access to no models
After one available model is selected, the card shows Partial 1/48
The card shows Partial and the number selected; the total changes with the models available to the organization
4

4. Configure Built-in Features

Under "Features," enable or disable the following capabilities:

  • Code Interpreter: Runs code and generates charts, spreadsheets, or documents.

  • Knowledge Base RAG: Uses the organization's knowledge bases to answer questions and cite sources.

  • Deep Research: Breaks down questions and searches the web in multiple rounds. It uses its own web search and is unaffected by whether the official search tool is enabled.

  • Browser Tool: Operates a browser, opens pages, interacts with webpage elements, and captures screenshots.

Changes are saved automatically, so you do not need to click "Save." You can leave the page after the update success message appears. If saving fails, the page identifies the item that was not updated and restores it to its last successfully saved state.

Four feature toggles on the Assign MaiGPT Usage Permissions page
Manage MaiGPT built-in features in role settings

What Members See

After the role settings take effect, MaiGPT displays only the models, tools, skills, and feature entry points available to the member. If knowledge base retrieval or Code Interpreter was previously available but has been disabled for the role, the right panel explains that the feature is not yet available to the role.

If a connector has been enabled by the organization but is not yet available to the member's role, the member will not see the authorization button and can submit an access request instead. If the member previously completed authorization, they can still disconnect it to remove credentials they no longer use.

Last updated

Was this helpful?