Permission scopes

Your AI client requests scopes and Achievator shows them during authorization. Read and write scopes are independent; a write scope does not grant read tools. Every required scope must be approved, and each operation still checks your normal workspace and resource permissions.

achievator.projects.read

Read projects

Permits

Search names and read returned project details in the connected workspace, subject to your project access.

Does not permit

Does not create, edit or delete projects, or access another workspace.

achievator.tasks.read

Read tasks

Permits

Search accessible workspace tasks and your own personal tasks, and read their fields, descriptions, checklists and links. Combined with productivity.read, enables weekly context and previews.

Does not permit

Does not create or edit tasks, read another user's personal tasks or grant productivity review access on its own.

achievator.tasks.write

Write tasks and weekly plans

Permits

Create and update tasks, append or rewrite descriptions, and add or update checklists. With tasks.read and productivity.read, enables saving approved Weekly Focus, Weekly Wins and task schedules.

Does not permit

Does not grant read tools, delete tasks or checklist items, manage users or change workspace permissions. Weekly planning cannot schedule someone else's tasks into your personal week.

achievator.productivity.read

Read productivity and time tracking

Permits

Read your own recorded time, planning, focus alignment, estimates and estimate calibration. With tasks.read, enables weekly-planning context and previews.

Does not permit

Does not start timers, create or edit time entries, save a weekly plan on its own or grant access to other users' private productivity data.

achievator.notes.read

Read notes

Permits

Search accessible workspace and personal notes and read current note Markdown, location and revision. Your normal list and resource permissions still apply.

Does not permit

Does not create or edit notes, or read other users' personal notes. Personal note search excludes notes attached to personal tasks.

achievator.notes.write

Write notes

Permits

Create notes and update accessible note titles, pinned state and content. Notes may be personal or attached to one supported existing parent, including a task.

Does not permit

Does not grant read tools, delete or move notes, change ownership or expand your normal edit permissions.

achievator.ideas.read

Read ideas

Permits

Search accessible ideas by title and read their current Markdown descriptions, locations and revisions.

Does not permit

Does not create or edit ideas, or read other users' personal ideas. Search does not scan idea descriptions.

achievator.ideas.write

Write ideas

Permits

Create personal or linked ideas and update their titles and rich-text descriptions under your existing permissions.

Does not permit

Does not grant read tools, delete or move ideas, change ownership, pin ideas or attach them directly to tasks.

achievator.documents.read

Read documents and pages

Permits

Search accessible documents, read document metadata and page trees, and read selected pages as Markdown with revisions.

Does not permit

Does not create or edit documents or pages, read another user's personal documents or search page bodies.

achievator.documents.write

Write documents and pages

Permits

Create a document and its first page, update document metadata, add pages or one level of subpages, and append or replace accessible page content.

Does not permit

Does not grant read tools, delete or move documents or pages, change ownership or create deeper page nesting.

OAuth 2.1 & PKCE

Achievator MCP uses OAuth 2.1 with PKCE (Proof Key for Code Exchange) — the current security standard for authorizing third-party app access without sharing passwords.

What this means for you: When you connect an AI client, you authenticate directly with Achievator. The AI client never sees your password. Instead, it receives a short-lived, scoped access token that can only perform the actions you approved.

PKCE prevents interception: The code exchange process includes a cryptographic proof so that even if the authorization code were intercepted in transit, it could not be used by anyone other than the AI client that initiated the flow.

Access tokens are short-lived: Tokens expire automatically. The AI client uses a refresh token to silently obtain new access tokens. If you revoke access, the refresh token is also invalidated — the AI cannot obtain new tokens.

Revoking access

You can revoke an AI client's access to Achievator at any time. Revocation is immediate and does not require contacting support.

  1. 1

    Go to Achievator Settings

    Navigate to Settings → Security → Connected Apps.
  2. 2

    Locate the AI connection

    Find the Claude, ChatGPT, or other MCP client entry.
  3. 3

    Click Disconnect and confirm

    Access and refresh tokens for this connection are immediately invalidated.
  4. 4

    Remove from AI client

    Also delete or disconnect the connector from within your AI client to prevent confusion.

Add screenshot: achievator-connected-apps.webp

Place the image in public/images/help/

Achievator Settings → Security → Connected Apps

Frequently asked questions