{"versionId":"343668d3-cc32-4c4d-0410-08dea64beb61","articleId":"35ce27c0-8ad6-4ba3-5730-08de8b941e33","title":"Access Profiles | Admin Guide","tags":["System admin","User management","All articles"],"content":"<html><head></head><body><p>Access Profiles let system administrators control who can access specific features in Theta Assist. You can use them to restrict&nbsp;<strong>models</strong>,&nbsp;<strong>built-in tools</strong>,&nbsp;<strong>connectors</strong>, and&nbsp;<strong>MCP servers</strong>&nbsp;to specific users or groups.</p>\n<p>This helps you manage access to higher-cost or specialised capabilities without creating new user roles.</p>\n<div class=\"mce-toc\">\n<h2>Quick links</h2>\n<ul>\n<li><a href=\"#1-what-access-profiles-are\">What access profiles are</a></li>\n<li><a href=\"#2-what-they-control--and-what-they-dont\">What access profiles control</a>\n<ul>\n<li><a href=\"#mcetoc_1jnoakfvm35g\">Important: models behave differently from tools and servers</a></li>\n<li><a href=\"#mcetoc_1jnoakfvm35h\">Key distinction</a></li>\n</ul>\n</li>\n<li><a href=\"#mcetoc_1jkml5teg53\">Manage access profiles</a>\n<ul>\n<li><a href=\"#mcetoc_1jnoakfvm35i\">Create a profile</a></li>\n<li><a href=\"#adding-members\">Add members</a></li>\n<li><a href=\"#removing-members\">Remove members</a></li>\n<li><a href=\"#deleting-a-profile\">Delete a profile</a></li>\n</ul>\n</li>\n<li><a href=\"#mcetoc_1jkml5teg54\">Apply an access profile</a>\n<ul>\n<li><a href=\"#mcetoc_1jnoakfvm35j\">Apply to a model</a></li>\n<li><a href=\"#built-in-tools\">Apply to a built-in tool</a></li>\n<li><a href=\"#connectors\">Apply to a connector</a></li>\n<li><a href=\"#mcp-servers-theta-assist-servers\">Apply to an MCP server</a></li>\n</ul>\n</li>\n<li><a href=\"#mcetoc_1jkml5teg55\">How access is evaluated</a>\n<ul>\n<li><a href=\"#mcetoc_1jnoakfvm35k\">For models</a></li>\n<li><a href=\"#mcetoc_1jnoakfvm35l\">For tools, connectors, and MCP servers</a></li>\n<li><a href=\"#caching\">Caching</a></li>\n</ul>\n</li>\n<li><a href=\"#6-common-scenarios\">Common scenarios</a>\n<ul>\n<li><a href=\"#mcetoc_1jnoakfvm35m\">Restrict premium models to approved users</a></li>\n<li><a href=\"#mcetoc_1jktkd2v73s\">Restrict an MCP server to a specific team</a></li>\n<li><a href=\"#mcetoc_1jktkd2v73t\">Make a tool available to everyone</a></li>\n<li><a href=\"#mcetoc_1jktkd2v73u\">Use one profile across multiple tools</a></li>\n</ul>\n</li>\n<li><a href=\"#7-troubleshooting\">Troubleshooting</a>\n<ul>\n<li><a href=\"#mcetoc_1jnoakfvm35n\">A user cannot see a model they should be able to use</a></li>\n<li><a href=\"#mcetoc_1jnoakfvm35o\">A user can see a model they should not be able to use</a></li>\n<li><a href=\"#mcetoc_1jnoakfvm35p\">A user cannot add a tool, connector, or MCP server they should have access to</a></li>\n<li><a href=\"#mcetoc_1jnoakfvm35q\">A user can use a tool but is not in the tool’s Access Profile</a></li>\n<li><a href=\"#mcetoc_1jnoakfvm35r\">A user cannot switch a thread to a specific model</a></li>\n<li><a href=\"#mcetoc_1jnoakfvm35s\">Deleting a profile unexpectedly opened access</a></li>\n</ul>\n</li>\n</ul>\n</div>\n<h2 id=\"1-what-access-profiles-are\" dir=\"auto\" data-line=\"19\">What access profiles are</h2>\n<p>An&nbsp;<strong>Access Profile</strong>&nbsp;is a named list of users and/or groups.</p>\n<p>You assign an Access Profile to a feature to control who can access it. Access Profiles do not grant system permissions on their own. Their meaning comes from where you apply them.</p>\n<p>For example, you might:</p>\n<ul>\n<li>restrict a premium model to a small group of approved users</li>\n<li>allow only the finance team to add a Business Central MCP server</li>\n<li>limit a built-in tool to users who have completed training</li>\n</ul>\n<h2 id=\"2-what-they-control--and-what-they-dont\" dir=\"auto\" data-line=\"29\">What access profiles control</h2>\n<p>Access Profiles can be applied to:</p>\n<ul>\n<li>Models</li>\n<li>Built-in tools</li>\n<li>Connectors</li>\n<li>MCP servers</li>\n</ul>\n<h3 id=\"mcetoc_1jnoakfvm35g\">Important: models behave differently from tools and servers</h3>\n<p>Access Profiles do not behave the same way for every feature type.</p>\n<div>\n<table style=\"width: 723.658081px; border-collapse: collapse; border-width: 2px;\" border=\"1\">\n<thead>\n<tr>\n<th style=\"text-align: left; border-width: 2px;\">Feature type</th>\n<th style=\"text-align: left; border-width: 2px;\">What the Access Profile controls</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"border-width: 2px;\">Models</td>\n<td style=\"border-width: 2px;\">Who can&nbsp;<strong>see, select, and use</strong>&nbsp;the model</td>\n</tr>\n<tr>\n<td style=\"border-width: 2px;\">Built-in tools</td>\n<td style=\"border-width: 2px;\">Who can&nbsp;<strong>configure</strong>&nbsp;the tool on an assistant</td>\n</tr>\n<tr>\n<td style=\"border-width: 2px;\">Connectors</td>\n<td style=\"border-width: 2px;\">Who can&nbsp;<strong>configure</strong>&nbsp;the connector on an assistant</td>\n</tr>\n<tr>\n<td style=\"border-width: 2px;\">MCP servers</td>\n<td style=\"border-width: 2px;\">Who can&nbsp;<strong>configure</strong>&nbsp;the MCP server on an assistant</td>\n</tr>\n</tbody>\n</table>\n<h3 id=\"mcetoc_1jnoakfvm35h\">Key distinction</h3>\n<p>For&nbsp;<strong>tools, connectors, and MCP servers</strong>, Access Profiles gate&nbsp;<strong>configuration</strong>. Once an authorised user has added one of these to an assistant, other users with access to that assistant may still be able to use it.</p>\n<p>For&nbsp;<strong>models</strong>, Access Profiles gate both&nbsp;<strong>visibility</strong>&nbsp;and&nbsp;<strong>use</strong>. If a user is not allowed to use a restricted model:</p>\n<ul>\n<li>they will not see it in model pickers</li>\n<li>they cannot assign it to an assistant</li>\n<li>they cannot switch a thread to it</li>\n<li>model-based background features will not select it on their behalf</li>\n</ul>\n</div>\n<h2 id=\"mcetoc_1jkml5teg53\" dir=\"auto\" data-line=\"40\">Manage access profiles</h2>\n<h2 id=\"3-managing-access-profiles\" dir=\"auto\" data-line=\"40\"></h2>\n<p>Access Profiles are managed under&nbsp;<strong>Admin &gt; Management &gt; Access Profiles</strong>.</p>\n<h3 id=\"mcetoc_1jnoakfvm35i\">Create a profile</h3>\n<ol>\n<li>Go to&nbsp;<strong>Admin &gt; Management &gt; Access Profiles</strong>.</li>\n<li>Select&nbsp;<strong>Create profile</strong>.</li>\n<li>Enter a unique&nbsp;<strong>Name</strong>.</li>\n<li>Optionally enter a&nbsp;<strong>Description</strong>.</li>\n<li>Select&nbsp;<strong>Create</strong>.</li>\n</ol>\n<div><img src=\"https://storage.faqbot.nz/prod/0d5220bc9ad14992d05108dccd460f35/files/pasted_image_article_access-profiles-admin-guide_bc74a9cb-d419-4655-a095-3d71e811069b.png\" width=\"800\" height=\"289\"></div>\n<h3 id=\"adding-members\" dir=\"auto\" data-line=\"51\">Add members</h3>\n<p dir=\"auto\" data-line=\"53\">Open the profile to add members. Members can be:</p>\n<table dir=\"auto\" style=\"border-collapse: collapse; border-spacing: 2px;\" border=\"1\" data-line=\"55\">\n<thead dir=\"auto\" data-line=\"55\">\n<tr dir=\"auto\" data-line=\"55\">\n<th>Member type</th>\n<th style=\"text-align: left;\">Description</th>\n</tr>\n</thead>\n<tbody dir=\"auto\" data-line=\"57\">\n<tr dir=\"auto\" data-line=\"57\">\n<td><strong>User</strong></td>\n<td>A specific individual user</td>\n</tr>\n<tr dir=\"auto\" data-line=\"58\">\n<td><strong>Group</strong></td>\n<td>All current and future members of a Theta Assist group, including Azure AD-synced groups</td>\n</tr>\n<tr dir=\"auto\" data-line=\"59\">\n<td><strong>Everyone</strong></td>\n<td>All authenticated users</td>\n</tr>\n</tbody>\n</table>\n<p>To add a member:</p>\n<ol>\n<li>Open the profile.</li>\n<li>Select&nbsp;<strong>Add member</strong>.</li>\n<li>Choose the member type.</li>\n<li>Select the user or group.</li>\n<li>Confirm the change.</li>\n</ol>\n<p dir=\"auto\" data-line=\"61\"><strong>\uD83D\uDCA1 Tip:</strong>&nbsp;Using&nbsp;<strong>Group</strong>&nbsp;membership (especially Azure AD-synced groups) is preferred over adding users individually — group membership changes automatically propagate without needing to update the Access Profile.</p>\n<h3 id=\"removing-members\" dir=\"auto\" data-line=\"65\">Remove members</h3>\n<ol>\n<li>Open the profile.</li>\n<li>Find the user or group in the member list.</li>\n<li>Remove the member.</li>\n</ol>\n<p>Changes usually apply quickly, but cached access may take a few minutes to refresh.</p>\n<h3 id=\"deleting-a-profile\" dir=\"auto\" data-line=\"69\">Delete a profile</h3>\n<p>Deleting an Access Profile does not delete the features using it. It removes the restriction from those features.</p>\n<p>If a deleted profile was assigned to a model, tool, connector, or MCP server, that item becomes unrestricted unless another restriction is applied.</p>\n<h2 id=\"mcetoc_1jkml5teg54\" dir=\"auto\" data-line=\"75\">Apply an access profile</h2>\n<p>You can apply an Access Profile in several places.</p>\n<h3 id=\"mcetoc_1jnoakfvm35j\">Apply to a model</h3>\n<p>Use this when you want to restrict who can see and use a model.</p>\n<ol>\n<li>Go to&nbsp;<strong>Admin &gt; Configuration &gt; Models</strong>.</li>\n<li>Open the model you want to manage.</li>\n<li>Select an&nbsp;<strong>Access Profile</strong>.</li>\n<li>Save your changes.</li>\n</ol>\n<p>If no Access Profile is assigned, the model is available to all eligible users.</p>\n<p><strong>Note:</strong>&nbsp;System admins can still see restricted models.</p>\n<h2 id=\"4-applying-an-access-profile-to-a-tool-or-server\" dir=\"auto\" data-line=\"75\"></h2>\n<h3 id=\"built-in-tools\" dir=\"auto\" data-line=\"79\">Apply to a built-in tool</h3>\n<ol>\n<li>Go to&nbsp;<strong>Admin &gt; Built-in Tools</strong>.</li>\n<li>Open the tool settings.</li>\n<li>Select an&nbsp;<strong>Access Profile</strong>.</li>\n<li>Save your changes.</li>\n</ol>\n<p dir=\"auto\" data-line=\"86\">Tools with no Access Profile assigned are visible to all users when configuring their assistant.</p>\n<h3 id=\"connectors\" dir=\"auto\" data-line=\"88\">Apply to a connector</h3>\n<ol dir=\"auto\" data-line=\"90\">\n<li dir=\"auto\" data-line=\"90\">Go to <strong>Admin &gt; Connectors</strong>.</li>\n<li dir=\"auto\" data-line=\"91\">Open the connector settings.</li>\n<li dir=\"auto\" data-line=\"92\">Select an Access Profile</li>\n<li dir=\"auto\" data-line=\"92\">Save your changes.</li>\n</ol>\n<h3 id=\"mcp-servers-theta-assist-servers\" dir=\"auto\" data-line=\"95\">Apply to an MCP server</h3>\n<ol dir=\"auto\" data-line=\"97\">\n<li dir=\"auto\" data-line=\"97\">Go to <strong>Admin &gt; MCP Servers</strong>.</li>\n<li dir=\"auto\" data-line=\"98\">Open the server configuration.</li>\n<li dir=\"auto\" data-line=\"99\">Select an Access Profile.</li>\n<li>Save your changes.</li>\n</ol>\n<p dir=\"auto\" data-line=\"102\">This applies to both globally-scoped and assistant-scoped MCP servers.</p>\n<h2 id=\"mcetoc_1jkml5teg55\" dir=\"auto\" data-line=\"106\">How access is evaluated</h2>\n<h2 id=\"5-how-access-is-evaluated\" dir=\"auto\" data-line=\"106\"></h2>\n<p>When a user opens a configuration screen, Theta Assist checks their Access Profile membership, including both direct membership and group membership.</p>\n<h3 id=\"mcetoc_1jnoakfvm35k\">For models</h3>\n<p>If a model:</p>\n<ul>\n<li>has&nbsp;<strong>no Access Profile</strong>, it is available to all eligible users</li>\n<li>has an&nbsp;<strong>Access Profile</strong>, it is available only to members of that profile and system admins</li>\n</ul>\n<p>If a user is not allowed to use a restricted model:</p>\n<ul>\n<li>the model is hidden from model lists</li>\n<li>assigning it to an assistant is blocked</li>\n<li>switching a thread to it is blocked</li>\n<li>background features that choose models automatically will skip it and use another valid option if available</li>\n</ul>\n<p>Restricted models also cannot be set as the&nbsp;<strong>system default model</strong>.</p>\n<h3 id=\"mcetoc_1jnoakfvm35l\">For tools, connectors, and MCP servers</h3>\n<p>If an item:</p>\n<ul>\n<li>has&nbsp;<strong>no Access Profile</strong>, it is available to all eligible users</li>\n<li>has an&nbsp;<strong>Access Profile</strong>, only members of that profile can add or configure it</li>\n</ul>\n<p>Items a user cannot configure are usually hidden.&nbsp;</p>\n<h3 id=\"caching\" dir=\"auto\" data-line=\"117\">Caching</h3>\n<p>Access Profile membership is cached for a short time.</p>\n<p>After adding or removing someone from a profile:</p>\n<ul>\n<li>wait up to&nbsp;<strong>5 minutes</strong></li>\n<li>ask the user to refresh the page and try again</li>\n</ul>\n<h2 id=\"6-common-scenarios\" dir=\"auto\" data-line=\"123\">Common scenarios</h2>\n<h3 id=\"mcetoc_1jnoakfvm35m\">Restrict premium models to approved users</h3>\n<p>Use an Access Profile when you want only a nominated group to use a higher-cost model.</p>\n<p>Example:</p>\n<ol>\n<li>Create an Access Profile such as&nbsp;<strong>Premium model users</strong>.</li>\n<li>Add the approved users or groups.</li>\n<li>Open&nbsp;<strong>Admin &gt; Configuration &gt; Models</strong>.</li>\n<li>Assign that profile to the premium model.</li>\n<li>Save.</li>\n</ol>\n<p>Only those users, plus system admins, will see and be able to use that model.</p>\n<h3 id=\"mcetoc_1jktkd2v73s\">Restrict an MCP server to a specific team</h3>\n<ol>\n<li>Create an access profile, for example&nbsp;<strong>Sales Team</strong>.</li>\n<li>Add the relevant Azure AD group or individual users to the profile.</li>\n<li>Open the MCP server settings.</li>\n<li>Assign the&nbsp;<strong>Sales Team</strong>&nbsp;profile.</li>\n</ol>\n<p>Only members of that profile will be able to add the server to their assistants.</p>\n<h3 id=\"mcetoc_1jktkd2v73t\">Make a tool available to everyone</h3>\n<p>Leave the&nbsp;<strong>Access Profile</strong>&nbsp;field blank, or remove the profile that is currently assigned.</p>\n<p>The tool will be visible to all users and available for them to add to their assistants.</p>\n<h3 id=\"mcetoc_1jktkd2v73u\">Use one profile across multiple tools</h3>\n<p>You can use the same Access Profile across:</p>\n<ul>\n<li>models</li>\n<li>tools</li>\n<li>connectors</li>\n<li>MCP servers</li>\n</ul>\n<p>This is useful when one team should have access to a set of related capabilities.</p>\n<p>&nbsp;</p>\n<h2 id=\"7-troubleshooting\" dir=\"auto\" data-line=\"147\">Troubleshooting</h2>\n<h3 id=\"mcetoc_1jnoakfvm35n\">A user cannot see a model they should be able to use</h3>\n<p>Check the following:</p>\n<ul>\n<li>the model has the correct Access Profile assigned</li>\n<li>the user, or one of their groups, is in that profile</li>\n<li>the user has refreshed the page</li>\n<li>enough time has passed for cached access to refresh</li>\n</ul>\n<p>If the user still cannot see it, ask a system admin to confirm the model restriction.</p>\n<h3 id=\"mcetoc_1jnoakfvm35o\">A user can see a model they should not be able to use</h3>\n<p>Check whether:</p>\n<ul>\n<li>the wrong Access Profile is assigned to the model</li>\n<li>the user is a member of the profile through a group</li>\n<li>the user is a system admin</li>\n</ul>\n<h3 id=\"mcetoc_1jnoakfvm35p\">A user cannot add a tool, connector, or MCP server they should have access to</h3>\n<p>Check the following:</p>\n<ul>\n<li>the item has the correct Access Profile assigned</li>\n<li>the user, or one of their groups, is in that profile</li>\n<li>the item is enabled</li>\n<li>cached access has refreshed</li>\n</ul>\n<h3 id=\"mcetoc_1jnoakfvm35q\">A user can use a tool but is not in the tool’s Access Profile</h3>\n<p>This may be expected.</p>\n<p>For tools, connectors, and MCP servers, Access Profiles control who can&nbsp;<strong>configure</strong>&nbsp;the item. They do not necessarily stop other users from using an assistant that already has the item configured.</p>\n<h3 id=\"mcetoc_1jnoakfvm35r\">A user cannot switch a thread to a specific model</h3>\n<p>The model may be restricted by an Access Profile.</p>\n<p>Ask a SysAdmin to check:</p>\n<ul>\n<li>whether the model is restricted</li>\n<li>whether the user is a member of the assigned profile</li>\n</ul>\n<h3 id=\"mcetoc_1jnoakfvm35s\">Deleting a profile unexpectedly opened access</h3>\n<p>Deleting an Access Profile removes the restriction from any models, tools, connectors, or MCP servers that used it.</p>\n<p>If this was not intended:</p>\n<ul>\n<li>recreate the profile, or create a replacement</li>\n<li>reassign it to the affected items</li>\n</ul></body></html>","description":"Use Access Profiles to control who can access models, tools, connectors, and MCP servers in Theta Assist.","isMarkdown":false,"publishedOnUtc":"2026-05-04T01:47:46.9386755","modifiedOnUtc":"2026-03-27T00:02:21.0033047"}