← Back to site

Keep your system. Move the work here.

This page is for a company that already has its own system and does not want to give it up. Below: what lives where, how master keys work, and how to connect the two.

Ask your AI instead of reading

The link below is written for machines. Give it to Claude, ChatGPT or whatever your team uses — it will explain the integration in your own terms and write the requests for you.

chatick.com/integration.txt

Who owns what

Yours

Projects, clients, deadlines, budgets, reporting — your system. Chatick does not touch them.

Chatick

Tasks and checklists, time tracking, chat, files, documents, notes — Chatick.

Master keys

A company admin creates a key in company settings. It is shown once: only its fingerprint is stored, and nobody can recover it later. Revoking is immediate — the check runs on every request, not on expiry. Every call is logged.

A key carries scopes: users:write, projects:write, read:all. A read-only key cannot create anything — that is the point.

How to connect

  1. The admin issues a key in company settings and hands it to your developer.
  2. Your system pushes projects. Sending the same one twice updates it instead of duplicating.
  3. Your system pushes people. Up to 500 per call; one bad record does not sink the rest.
  4. Your reporting reads tasks, hours and summaries back whenever it needs them.

Moving between the systems

Ask our API for a link and a person lands straight in the project — they already signed in on your side. The link lives five minutes and works once. In the other direction, set your project URL template once and a button appears in the project header.

Webhooks

Instead of polling us, receive an event when a task is created, reassigned or changes status. Every request is signed; verify the signature so nobody else can send you invented events.

How people sign in

You never manage their passwords — Chatick has none. Google, a code by email, or the one-time link. All three lead to the same account. We never call your system to authenticate: if it goes down, people already working keep working.