Connect AI agents

Connect an external AI agent to the selected iTasks workspace on your behalf. It uses your current permissions, not the owner's: only projects, data and actions available to you are accessible.

Before you connect

The selected workspace needs an active PRO subscription. Access is automatic for the owner. Other members, including administrators, need a separate grant from the owner or an administrator.

Connect your agent

1. Select the workspace you need.
2. Open your profile using your avatar and choose “Connect AI agents”. This screen shows only the current workspace.
3. Choose “Copy instructions” and send the entire text to your AI agent. It includes the connection addresses, user, workspace and rules.
4. If your client needs manual server setup, use the MCP URL below the instructions with Streamable HTTP transport. No additional Bearer token is required.
5. Ask the agent to call get_current_context first and verify the user and workspace without changing data. Then give it a specific task.

Use a client that supports remote MCP or REST/OpenAPI. Pasting instructions does not guarantee automatic setup in every client: you may need to add the server manually or approve access. REST, OpenAPI and discovery addresses are already included in the complete instructions.

Grant access to a member

The owner or an administrator opens “Administration → Members”, selects a user and enables “Access via MCP/API” in their settings. Enabling access requires PRO. The owner is marked “Automatic for the owner”. This grant does not change the user's role or project access. Administrators can also grant themselves access, but cannot disable the owner's automatic access.

Once access is granted, the member opens their own profile and copies their own instructions. The manager sees the permission state, not another user's personal link. Do not share the owner's keys with members.

Members and roles

Update keys or revoke access

Use the same personal link in all your AI clients for this workspace. Copying or reopening it does not change it. Confirming “Update access keys” immediately invalidates the old link in every client. Copy the new instructions and update each connection; other members' links are unaffected.

To revoke a member's access, disable “Access via MCP/API” in their settings. The server immediately rejects further requests. An open screen may still display the old link until reopened; this does not make the link valid. Removing a member or blocking their account also ends their access.

Permissions, limits and security

• Permission to connect is not an instruction to change data. The agent should act on your requests; private projects, other users' protected files and forbidden actions remain inaccessible.
• Tasks, comments, time tracking and HelpDesk follow your permissions. “My tasks” means tasks assigned to you. Changes are made on your behalf.
• Request limits are shared by the workspace and all connections. They are not model AI token usage. On HTTP 429, the client must follow Retry-After.
• When PRO expires, connections pause. Renewal restores an existing grant and link unless access has been revoked.
• The link and instructions contain secrets. Share them only with a trusted AI client, never in team chats, screenshots, logs or repositories. Secret fields are hidden in these illustrations.

Related guides

Members and roles · Profile and language · Subscription and limits