Skip to documentation
Documentation
Documentation
OverviewInstallationQuickstartYour first dayYou were sent a linkWorking with a customerConfigurationTroubleshootingFAQGlossary

Usage

Terminal interfaceCLIStatuslineDashboardAnalytics

Collaborate

DocumentsLessonsSession sharingPicking up tomorrow and handing work overFrom your phoneSession linksSession messagingAsksAsks privacy fact sheetFeedbackEmail from crewkitBlueprintsAgent identitiesMCP server

Configure

AgentsSkillsSkill and agent security scanningRulesCommandsInheritancePlaybooksExperimentsHooksCapture modesSensitive sessionsData residencyTeamSettings mapIntegrations

Workspaces

WorkspacesSet up a workspaceFix a ticket end to endShip a feature with approvalHand off work and set agent settings

API Reference

API OverviewAuthenticationSessions APIResources APIOrganizations APIProjects APIPlaybooks APIExperiments API
Need a hand?Find an answer in troubleshooting.
Loading docs…
CREWKIT / DOCUMENTATION

Working with a customer

For a team building in its customer's repository, every route a customer with no crewkit account has today, what each one stores, which providers see it, how long it is kept and who on your team reads it.

A customer here is a person outside your organization, with no crewkit account. crewkit gives such a person three routes today: an Ask link, a share link and a feedback panel. This page says what each one sends, stores and keeps, so you can pick one before your first session and answer the customer's privacy officer.

What the customer sees on each route is on You were sent a link. What your own sessions collect is set by your organization's capture mode.


The routes

RouteWhat the customer sees and sendsWhere it is stored, and which providers see itKept forWho sets it up, and who on your team reads it
Ask linkYour questions. They send answers, a reason for each, and the name they give.crewkit's API and database on DigitalOcean; Vercel serves the static page and never sees an answer. No Ask code calls Anthropic or Voyage AI. Answers a person confirms reach your sessions, which are analyzed and indexed under your session settings. See Where it goes.Your Asks retention after the Ask closes: 180 days by default, 30 to 365. A hashed network address, 30 days.An Admin or Owner publishes; a Manager too, when the organization allows it. Every member can read the Responses.
Share link to one conversationOne conversation, at the level you chose: a summary, the transcript, or the transcript with its token counts and git context. They send nothing. crewkit counts each opening, and does not record who opened it.The conversation is already stored in crewkit, under your capture mode; under minimal a link shows the summary only.Until it expires or is revoked; a CLI link expires in 7 days by default. The conversation itself follows your session retention, 365 days by default.The conversation's owner, or a Manager and up, creates a link for members; only an Admin or Owner creates a public link, which is the only kind a customer can open.
Feedback panel in an app the customer testsA notice, then a message with their name and email, and the page they were on; a screenshot only when your team turns screenshots on for that key and they choose to add one.crewkit's database. Name and email are stored encrypted. A confirmed report becomes a project document your agents can search, which never holds the name, email or screenshot; project search sends queries to Voyage AI.Pending, 30 days. Confirmed, your feedback retention: 180 days by default, 30 to 365.An Admin or Owner turns Feedback on; a Developer and up creates the key. Developers and up, and members at Feedback triage, read reports in the Inbox.

You were sent a link

For someone with no crewkit account who opened a crewkit link, what the page is, what you can do there, who reads what you send, and how to erase it.

Configuration

Configure crewkit with environment variables, config files, and CI/CD settings.

On this page

The routesWhat has no routeWhich route for which job

What has no route

A plan or weekly status for the customer: no route exists today. Your project's plan and dashboard are read by members of your organization only, and no crewkit email sends a project's progress to anyone outside it. To show progress, send a share link to a conversation, or write the status yourself.


Which route for which job

  • You need a decision from the customer: an Ask.
  • You want to show them work: a share link, public, at the summary level unless they need the transcript.
  • You want bug reports from the app they test: the feedback panel.