Access360 access controls
This reference lists the controls that decide whether an AI assistant can reach Process DesignProcess Design The discipline of explicitly modeling business processes to document, analyze, and optimize them. In Process360 Live, process design is the authoring side that complements mining's data-driven view. through Access360Access360 The licensed add-on that connects AI assistants such as Claude, ChatGPT, and Microsoft Copilot Studio to Process Design through the Model Context Protocol (MCP). The assistant acts as the signed-in iGrafx account, with that account's permissions. and what it can do there, from the platform license down to a single item.
Controls
A request from an assistant has to pass every control that applies to it.
| Control | Where it's set | What it decides |
|---|---|---|
| Access360Access360 The licensed add-on that connects AI assistants such as Claude, ChatGPT, and Microsoft Copilot Studio to Process Design through the Model Context Protocol (MCP). The assistant acts as the signed-in iGrafx account, with that account's permissions. license | Your iGrafx license | Whether your platform can use Access360Access360 The licensed add-on that connects AI assistants such as Claude, ChatGPT, and Microsoft Copilot Studio to Process Design through the Model Context Protocol (MCP). The assistant acts as the signed-in iGrafx account, with that account's permissions. at all |
| MCP Connectivity | Admin → Server Settings → AI Settings | Whether Process DesignProcess Design The discipline of explicitly modeling business processes to document, analyze, and optimize them. In Process360 Live, process design is the authoring side that complements mining's data-driven view. accepts requests from assistants. Off by default |
| Repositories | Admin → Server Settings → AI Settings | Which repositories assistants can reach: All repositories, or only Selected repositories. Repositories added later stay out of reach under Selected repositories until you select them |
| Access MCP server permission | Admin → Security Roles | Who may connect an assistant. The built-in administrator roles have it from the start; everyone else needs a role that grants it. A Veto in any of a person's roles blocks them |
| Repository roles, item roles, and licenses | As for any user. See Security roles and permissions | What the assistant can see and change. It's never more than the account can do in Process DesignProcess Design The discipline of explicitly modeling business processes to document, analyze, and optimize them. In Process360 Live, process design is the authoring side that complements mining's data-driven view. |
| The assistant platform's own admin controls | The assistant platform, such as your Claude or ChatGPT organization settings | Whether people in your organization may add or use the connector at all |
API key access
These controls matter only for backend services and unattended agents, and for people who connect with an API key as a stopgap while their platform still uses the classic iGrafx Login.
| Control | Where it's set | What it decides |
|---|---|---|
| Allow access via API Key | Admin → Support → REST API | Whether anyone can connect with an API key. Doesn't affect Sign in with iGrafx |
| The account's API key | Admin → User Management, on the user | Whether that account can connect with a key. Deleting the key ends its connections |
Messages an assistant reports
When a control blocks a request, Process DesignProcess Design The discipline of explicitly modeling business processes to document, analyze, and optimize them. In Process360 Live, process design is the authoring side that complements mining's data-driven view. returns a message that the assistant usually passes on to you.
| Message | Control |
|---|---|
MCP connectivity is disabled for this installation. An administrator can enable it in Process Design under AI Settings. | MCP Connectivity is off |
You do not have permission to access this installation via MCP. An administrator can grant MCP access through your server role permissions in Process Design. | The account lacks Access MCP, or one of its roles vetoes it |
Repository '<name>' is not enabled for MCP access. An administrator can enable it in Process Design under AI Settings. | The repository isn't among the Selected repositories |
REST API via API key authentication Disabled | The assistant connected with an API key while Allow access via API Key is off |
A repository that assistants can't reach also doesn't appear when an assistant lists repositories, so the assistant may report that it can't find the repository rather than quote the message above.
When Sign in with iGrafx is rejected, as it is on a platform that uses the classic iGrafx Login, the authorization page shows a message that begins Process Design did not accept the sign-in. Until the platform moves to the iGrafx IdentityiGrafx Identity The iGrafx identity and access management service that brokers authentication between customer identity providers and Process360 Live components. Solution, connect with an API key. See How Access360 signs in.
Notes / constraints
- A change to MCP Connectivity, the repositories, or Access MCP applies from the assistant's next request. Nobody has to reconnect.