Support

Yes. Open /workspaces?view=map, then drag a repo card from one application parent card and drop it on another application card.

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.

Title, 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.

Check 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.

Go 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.

Yes. 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. You can opt into pay-as-you-go overage or set a hard spend ceiling.

Use 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.

Go to Account and scroll to the danger zone. Account deletion removes all workspaces, memories, integration credentials, and audit logs within 24 hours. This action is irreversible.

Yes. All memories and integration credentials are encrypted at rest with AES-256-GCM. Enterprise plans support bring-your-own-key (BYOK) encryption per workspace.