How Access360 signs in
Every request an AI assistant sends 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. runs as one iGrafx account. The assistant proves which account by signing in with that account's iGrafx credentials or with an API key that belongs to it. People should sign in with their own iGrafx account. API keys are meant for backend services and unattended agents, and as a stopgap on platforms that still use the classic iGrafx Login.
Overview
The first time an assistant connects, it opens an iGrafx authorization page in your browser. The page offers two ways to sign in:
- Sign in with iGrafx — you sign in with your iGrafx account, the same way you sign in to 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..
- Connect with an API key instead — you paste an API key that an administrator generated for an account.
Once you've signed in, the assistant receives its own access to 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. for that account. It never sees your password, and the API key you paste isn't passed on to the assistant.
Some agents can't open a browser, such as an agent that runs unattended. They send an API key as a request header with every request instead. See Connect a coding agent to Access360.
Which sign-in fits your platform
Sign in with iGrafx works when your platform signs people in through the iGrafx IdentityiGrafx Identity The iGrafx identity and access management service that brokers authentication between customer identity providers and Process360 Live components. Solution. To check: open your platform's address in a private browser window. If you're forwarded to id.igrafxcloud.com, id.igrafxcloud.eu, or id.igrafxcloud.jp, your platform uses the iGrafx IdentityiGrafx Identity The iGrafx identity and access management service that brokers authentication between customer identity providers and Process360 Live components. Solution, including when you then continue to your organization's own single sign-on.
If your platform uses the classic iGrafx Login, the authorization page still shows Sign in with iGrafx, but the sign-in is rejected. Move your platform to the iGrafx IdentityiGrafx Identity The iGrafx identity and access management service that brokers authentication between customer identity providers and Process360 Live components. Solution, so people can sign in with their own accounts; contact Customer Support to start. Until then, people can connect with an API key that an administrator generates for their account. See Set up Access360.
Individual and shared accounts
You decide whose account each assistant uses, and you can combine both approaches:
| Individual accounts | A shared account | |
|---|---|---|
| Who signs in | Each person, with their own iGrafx account | One dedicated account, used through a single API key |
| Permissions | Each person's own | The same for everyone who uses it |
| Changes recorded under | The person who made them | The shared account |
| Typical use | People who maintain the process model and need their changes traceable | A wider group, or an agent, that looks things up and asks questions |
Every account needs a licensed seat, whether a person or an agent uses it.
- Keep changes on individual accounts. A shared account can change content if its permissions allow it, but every change is recorded under the shared account. You can't tell which person made it, which weakens governance and the audit trail. Have people who change content use their own accounts, and give a shared account view-only permissions when it's only for looking things up.
- Decide whether agents share an account or each get their own. Agents that share one account use one licensed seat, but they all get the same permissions. An agent with its own account gets only the permissions its task needs, so an agent that only looks things up can't change the process model. This uses one seat per agent.
How long a connection lasts
- After you sign in with your iGrafx account, the connection lasts up to 90 days. After that, the assistant asks you to sign in again. It also asks again sooner if the iGrafx IdentityiGrafx Identity The iGrafx identity and access management service that brokers authentication between customer identity providers and Process360 Live components. Solution stops accepting your sign-in.
- After connecting with an API key, the connection also lasts up to 90 days before you sign in again. The key itself never expires: it works until an administrator deletes it.
- When an agent sends the API key on every request, there's no sign-in to renew. Access ends when the key is deleted.
Ending access
An administrator can end someone's access 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. at any time:
- Delete the account's API key, which ends every connection made with it.
- Take the person out of the group whose role grants Access MCP, or remove the permission from their roles.
- Switch off MCP Connectivity, which stops every assistant at once.
A person can also disconnect the assistant on their side, in the assistant's own connector settings.
Related tasks & references
- Set up Access360
- Access360 access controls
- Setting up single sign-on
- Access the REST API, for generating an API key