Authentication and permissions

How you sign in

The connector uses OAuth 2.0. When you connect it in your app:

  1. Your app registers with the connector and sends you to the connector's sign-in address in your browser.
  2. Apps the connector can't verify (apps that sign in through an address on your own computer, such as Claude Code and Codex, and any other app) first see a connector page that names the app, marks the name as unverified, and shows where the sign-in will return to. You choose Allow or Deny. Claude's and ChatGPT's own hosted apps skip this page.
  3. PATHwd's sign-in page opens at pathwd.app. You sign in with your PATHwd email and password.
  4. PATHwd asks: "Allow PATHwd to use your account?" and explains that it will be able to do in PATHwd what you can do. You choose Allow or Deny.
  5. You are sent back to your app, which is now connected.

Your password is entered only on PATHwd's page. It never passes through the chat, your AI app or the connector.

The connector supports Dynamic Client Registration, PKCE (S256), refresh-token rotation with reuse detection, and token revocation. Its OAuth metadata is at https://mcp.pathwd.app/.well-known/oauth-authorization-server and https://mcp.pathwd.app/.well-known/oauth-protected-resource.

How long a sign-in lasts

  • Your app holds an access token that lasts 1 hour and a refresh token it uses to get new ones. Each refresh replaces the refresh token; a refresh token presented twice ends the whole connection.
  • The PATHwd sign-in behind the connection lasts 30 days. After that, your app asks you to sign in again.
  • An Allow on the connector's own page (step 2 above) is remembered in that browser, for that app, for 30 days.

The connector acts as you

Every command runs in your PATHwd account, as you, with exactly the access you have in the PATHwd web app:

  • Roles and business object permissions: you can view, edit, archive, create folders or create reports only where your roles allow it.
  • Tags: records outside your tags are not visible.
  • Fields, field groups and relationships: only what the record viewer shows you. Fields hidden from you don't appear at all.
  • Folders, reports and calendars: only those shared with you, with the access they are shared with.
  • Tasks, notes and messages: the same rules as in the web app (for example, only a note's author can edit or delete it).

When the web app wouldn't let you do something, the connector refuses it with a message such as "Jane Doe can't archive Job 26-0073 — they don't have Archive permission on Jobs, as in the web app." Nothing changes, and no other tool gets around it. The raw PATHwd API is not available through the connector (see Safety and confirmations), so every request goes through these checks.

Changes you make through the connector are recorded in PATHwd's history under your name, marked as made by an AI agent through the PATH CLI.

Accounts

If you belong to more than one PATHwd account, the connector can work in any of them, one at a time. The assistant lists your accounts and picks one when you say which. The choice is saved for the connection, so other chats in the same app use the same account until you switch. Accounts where you are deactivated can't be used.

What admins can do

Account Admins have the same extra abilities through the connector as in the web app, and no more:

  • Everything an Admin can do in the web app: every business object, folder, report and calendar; archiving and deleting.
  • Act as another member (the web app's Impersonate): an Admin can ask the assistant to run a command as another active member of the account, to see exactly what that member sees. Changes made this way are recorded as that member's, as in the web app. Only account Admins can do this; anyone else is refused with "… can't use --as-user: acting as another user is the web's Impersonate, which only account Admins have."
  • Designer permission additionally allows starting a pathway on a record that the pathway's visibility rules would otherwise hide it on (super-user mode), as in the web app. Changing the account's setup (business objects, fields, workflow, pathway design) is not available through this connector.

Admins who manage users and roles do so in the PATHwd web app. Every rule they set there applies to the connector at once.

Disconnecting and revoking access

To disconnect, remove or disconnect PATHwd in your app's connector settings:

  • Claude.ai, Claude Desktop, Cowork: Settings → Connectors, then disconnect or remove PATHwd.
  • Claude Code: /mcp, select pathwd and clear its authentication, or claude mcp remove pathwd.
  • ChatGPT: Settings → Apps & Connectors, then disconnect PATHwd.
  • Codex: codex mcp logout pathwd, or codex mcp remove pathwd.

When your app tells the connector it is disconnecting (OAuth token revocation), the connector at once:

  • ends the PATHwd sign-in behind the connection,
  • refuses that connection's tokens from then on, and
  • deletes the connection's private workspace (saved state and files).

If an app removes the connector without telling it, the app no longer holds the tokens, and the PATHwd sign-in behind them expires on its own within 30 days. Asking the connector to sign out from inside a chat does nothing; the message says to disconnect in the app instead.

PATHwd support can also pause the connector for a user or a whole account; contact support.

Thank you! Your message was sent. We'll be in touch soon.
Something went wrong. Please refresh the page and try again, or reach out directly by email.

Privacy Contact

If you have any questions, concerns, or requests related to our privacy policy, please contact us.

  • privacy@pathwd.com