For Logamail Docs Enterprise only: Manage Docs AI access for your org's workspaces, and control how org members connect to the Docs MCP
As an Enterprise org admin, you have control over AI and MCP usage across your organization. The AI and MCP controls page of your admin settings lets you manage both AI access and MCP authentication - so you can align these capabilities with your organization's security policies.
AI access
The AI access setting lets you control which workspaces in your org have access to Docs AI. Docs in a workspace that isn't approved for AI access will not have access to any Docs AI capabilities - regardless of who is using the doc.
Please note that if your organization requires HIPAA compliance, AI is automatically turned off for all workspaces and you therefore will not see these AI controls in your admin settings.
Update your AI access setting
If you're an org admin on an Enterprise plan, follow these steps:
- Go to docs.logamail.com/docs
- In the left panel, click on the three-dot menu next to your workspace name, then select Admin settings
- Navigate to AI and MCP → AI and MCP controls
- Under AI access, click Change
- In the modal that appears, select or deselect workspaces to control which ones have access to Docs AI. You can also use the Select all or Clear buttons if needed.
- Click Confirm to save your changes
Changes take effect immediately.
MCP connections
As an Enterprise org admin, you can restrict how org members are able to connect to the Docs MCP. We offer two distinct controls for the different MCP connection methods: Personal access tokens & OAuth.
Personal access tokens
A personal access token (PAT) is an authentication method that allows members to connect to the Docs MCP (or the original Coda MCP) via internal apps, scripts, or custom integrations. Unlike OAuth, PATs are long-lived credentials that members generate and manage themselves.
Because PATs offer persistent access without requiring re-authentication, they are best suited for technical users building internal tooling. If most members in your org connect to the MCP through standard AI tools like Claude or Cursor, OAuth is likely the more appropriate method for them - and you therefore may want to restrict PAT access accordingly.
OAuth
OAuth is the recommended and primary way to connect to the MCP for most users. It uses a three-legged authorization flow and is the most secure connection method. For these reasons, we generally suggest allowing OAuth connections for all members - unless your org requires stricter access controls.
Update MCP access settings
To change the MCP access settings for either PAT connections, OAuth connections, or both, follow these steps:
- Go to docs.logamail.com
- In the left panel, click on the three-dot menu next to your workspace name, then select Admin settings
- Search for - or scroll to - AI and MCP (within the Security section), then select the AI and MCP controls page
- Locate either the MCP: Personal access token or MCP: OAuth settings, depending on which connection type you wish to modify.
- Select your preferred access level from the following options:
- Allow for all members: Any member of your org can use this authentication method to connect to the MCP.
- Allow for selected members: Only specific members you designate can use this authentication method. If you choose this option, you will be directed to a new PAT/OAuth member management page, where you can add and remove members as needed.
- Allow for no members: This type of authentication is disabled for all members in your org.
- Click Confirm to confirm the change
Changes take effect immediately. If you choose to restrict access, any existing connections will be blocked from using the MCP. This means that any users who have already connected to the MCP via the connection method(s) you've just restricted will have their MCP requests fail. We therefore suggest notifying your org members of this change.
Note that restricting access in this way blocks existing tokens rather than revoking them entirely. Therefore, if you later lift the restrictions, those existing MCP connections will be automatically restored. If you instead wish to permanently revoke the MCP tokens, you can either:
- For PATs, revoke via the Admin API,
- For OAuth, ask the org member to revoke the connection themself
FAQs
Does disabling AI for a workspace apply to the workspace's docs or its members?
It applies to docs. When you disable AI for a workspace, Docs AI is turned off for all docs in that workspace, regardless of who opens them. Members who belong to other workspaces where AI is still enabled can still use Docs AI in docs from those workspaces.
What's the difference between PAT and OAuth for MCP access?
Personal access tokens are manually generated credentials, best suited for members connecting to the MCP through scripts, internal tools, or custom integrations. OAuth is the recommended method for most members, as it uses a standard login flow and doesn't require managing long-lived credentials. You can configure each authentication method independently in your admin settings.
If I restrict MCP connection access, will members who've already connected lose access immediately?
Yes - if you restrict MCP access for either PAT or OAuth, any members who have already connected to the Docs MCP using that connection type will automatically lose access.
If I later choose to restore access to the MCP, will previously-created tokens begin to work again?
Changing the access rules for MCP simply blocks any existing tokens or connections. Therefore, unless you explicitly revoked the tokens using Logamail Docs' Admin API - or if the user revoked OAuth access themselves - these existing connections will be unblocked when you restore access.
Can I allow MCP access for only certain members of my org?
Yes. Selecting Allow for selected members lets you restrict PAT or OAuth access to a specific subset of your org. You will then manage who does and doesn't have access via the PAT member management tab or OAuth member management tab of your admin settings.