Company administrators have complete control in ALITEO over whether and under what conditions AI assistants and MCP clients may access company data. This configuration is entirely independent of user settings and serves to protect company know-how.
Settings Location
The configuration is available to users with the company administrator role in the left panel:
- Open Company Settings.
- In the left menu, select the Integrations section.
- Click on the MCP Connector tab (Connecting AI tools to the company via the MCP protocol and their permissions).
Enabling Providers and the MCP Client
Administrators can selectively enable individual channels for the entire company:
- ChatGPT – toggle for the direct official ALITEO connector in the OpenAI interface (undergoing certification).
- Claude – toggle for the direct official ALITEO connector in the Anthropic interface (undergoing certification).
- MCP Client – master toggle (Enabled / Disabled). When enabled, users can connect to this company's data from any standard MCP client (e.g., Claude Desktop, Cursor, Antigravity) using the provided Client ID and Server Address. Disabling this toggle globally blocks access to company data for generic MCP clients.
Global Maximum Permissions for AI Tools
In the Permissions section, administrators define a security ceiling for the entire company. This ceiling determines the highest permission level an AI assistant can obtain:
- Read – the agent may read tasks, projects, and timesheets. Write and update operations are strictly blocked for all assistants in the company.
- Read and Write – the agent may create and edit tasks and timesheets; projects are read-only.
- Full Management – the agent has access to the full range of operations, including administrative actions corresponding to the user's role.
Permission Narrowing Rule: The company administrator sets the maximum possible permissions. The consent granted by a user to their assistant when establishing a specific session can only narrow these permissions, never expand them beyond the boundaries set by the administrator.
Permission Exceptions for Specific Users
If you need to configure different rules for specific company members compared to the global settings, use the Permission Exceptions section:
- Click the + Add button to select a specific user from the list of company members.
- For the selected user, choose an individual access level (e.g., restricting permissions to Read only, while the rest of the company is allowed Read and Write).
- Revoking access: The administrator can set an exception that completely blocks MCP access to company data for a given user, while other members can continue using the connector.
- An exception can be removed at any time by clicking the trash icon.
Company Audit and Session List
At the bottom of the screen is the Session List accordion. Here, administrators have an overview of all AI assistants of company members who currently or previously accessed data for this company:
- User – name and email of the company member whose assistant created the session.
- Last Activity – timestamp of the agent's most recent communication.
- Status – visual indicator (Connected, Disconnected, Expired).
- Permissions – currently applied permissions for the session.
- Disconnect Button – administrators have the right to disconnect any session immediately. This instantly revokes that assistant's access to this company's data without affecting the user's access in other companies.
Rate Limits and Quota Sharing with the REST API
The MCP protocol and the standard REST API share the same technical infrastructure and licensing rules in ALITEO. Each MCP tool call draws from the shared quota allocated to the company:
- Shared Company Limit – total number of allowed calls per 60 seconds (e.g., 1,300 requests/minute depending on the Premium or Enterprise plan). This limit is shared across all users, webhooks, REST API integrations, and AI agents within the company. Every domain tool call (tasks, projects, timesheets, meetings) consumes this quota.
- Exception for getRateLimits Tool – querying current rate limits (
getRateLimits) is not counted against the company quota and does not consume company limit capacity. This allows safe inspection of status before launching larger operations.
- General User Limit – for system tools not tied to a specific company (
listCompanies, getConnectionInfo, getRateLimits), a global limit of 60 calls per minute per user and tool applies.
- Time Window and Reset – limit counters reset automatically at the start of each minute in UTC time.
- Rate Limit Exceeded – when quota is exhausted, the server returns the error code
rate_limit_exceeded with the parameter retryAfterSeconds defining the number of seconds until the next window opens. Neither the client nor the assistant should make aggressive retry loops, but must respect the recommended delay.
- getConnectionInfo – inspects technical and diagnostic information about the connection and status of the ALITEO API gateway.
- listOperations – provides an overview of permitted operations and functions in the currently established session.