Preparing your workspace…
Preparing your workspace…
Support
Self-serve
Answers
Yes. Open /workspaces?view=map, then drag a repo card from one application parent card and drop it on another application card.
Open map viewTalk to a person
Sign in to file a request and track our replies in one place — you get an email when we respond.
For account issues, billing questions, or bug reports. We typically respond within one business day.
support@greatarrow.aiReport vulnerabilities or suspicious activity. Encrypted communication available on request.
security@greatarrow.aiFor urgent production incidents, check the status page first — it updates in real-time during active incidents.
Yes — owners and members with permission to update both workspaces can move cards on the map. In practice, that means the API must validate `workspace.update` on source and destination.
Not for map nesting. Workspace cards can only move under an application that belongs to the same workspace owner. For different owners, use ticket/card transfer between workspaces.
Yes, as long as rules pass: target is not GENERAL, source is not GENERAL, same-owner link, no cycles, and source has no forbidden parent/workspace constraints for that target.
Common reasons are: trying to move a GENERAL workspace, selecting a GENERAL target, dragging into itself, creating a cycle (A under B under A), or using a parent workspace you do not belong to with the same owner context.
A successful move shows an Undo action in the success toast. If that window closes, drag the card back to its original parent (or re-run the move in reverse).
Yes, from the card actions in the board/modal. That is a different flow from map nesting and is currently available for users with ADMIN, OWNER, or MEMBER on both source and target workspaces.
Go to workspacesTitle, status, dates, priority, checklist items, and core fields move with it. Labels/custom fields not available in the target and members/watchers that aren’t in target may be removed.
Yes. A successful transfer shows an Undo action in the success toast, which moves the card back in one step. You can also open Transfer again and move it back manually.
Set the kind or presentation template again from Settings. We do not provide a dedicated one-click undo control for these settings yet; choosing the previous value is the rollback path.
Yes, from Settings -> Workspace routing kind (the section below basic metadata). It’s a manager action and changes routing/rollup behavior.
You’ll be blocked when rules fail, such as trying to mark a workspace as REPO without a connected repo URL, switching to Home when one already exists, or nesting any workspace while changing to GENERAL.
Yes. Open workspace settings and update Presentation template type in its section. This changes label/template only and does not affect routing or roll-up behavior.
Sign in, then visit the Install page. Pick your AI brand and follow the guided flow — no terminal or config file needed.
Go to InstallCheck the Status page for any active incidents. If all systems are operational, try disconnecting and reconnecting the MCP integration from your AI client's settings.
Check statusGo to Account → Connections. Each active connection has a Revoke button that immediately invalidates the token. The AI client will lose access on its next request.
Manage connectionsYes. Each client gets its own OAuth token, but they all read and write to the same workspace memory. Changes made in Claude are immediately visible in ChatGPT and vice versa.
Each plan includes a monthly token allowance for both embeddings and chat. Usage is tracked in real-time on your Settings → Billing page. The plan price is the most you'll ever be charged in a month — calls pause when you reach your allowance, so you are never charged beyond your plan. To keep going, you can buy a one-time token pack, connect your own provider API keys (BYOK), or upgrade your plan.
View billingFree trials are card-free and automatically transition to the Free plan when the evaluation period ends — you will never be charged automatically. If you have an active paid plan, you can cancel anytime from Settings → Billing via the Stripe customer portal. Paid features remain active until the end of your billing cycle.
Manage billingUse the password reset flow. If you signed up with Google or GitHub OAuth, use that same provider on the sign-in page — no password is needed.
Reset passwordGo to Account settings (/account) and scroll to Delete account. Type your email address to confirm and click Delete account. This immediately cancels any active Stripe subscription, revokes all connected OAuth tokens, permanently removes all owned workspaces, memories, chat logs, and documents, deletes your login from our auth provider, and removes you from all email lists. This action is immediate and irreversible.
Account settingsYes. All memories and integration credentials are encrypted at rest with AES-256-GCM. Enterprise plans support bring-your-own-key (BYOK) encryption per workspace.