FAQ
Access, capabilities, limitations, and how to get help with ArxDeck.
FAQ
Answers to common product questions. The landing page FAQ covers shorter marketing summaries; this page goes deeper without repeating that copy verbatim.
Access and signup
Can I sign up without an invite?
Not yet. ArxDeck is invite-only for now. Contact contact@arxdeck.ai or your organization's admin for access. Self-serve signup is planned later this year — there is no public signup form on the marketing site today.
I have an invite — what if I already have an account?
Open the invite link, sign in when prompted, and accept the invite with the same email address. Membership is granted only with a valid token, authenticated session, and matching email.
Who can invite me?
Depends on scope: organization admins, project admins, or platform superadmins can send invitations for their respective scopes. They cannot duplicate invites for emails already in the target org or project.
Who is ArxDeck for?
ArxDeck leads with solo builders, side projects, and people experimenting with AI workflows who want a ready-made ticket board without stitching tools together. Teams are a secondary fit — ArxDeck supports multi-member projects, organizations, and shared credentials when you need them.
ArxDeck Helper
What can Helper configure?
Workflows, agents, scheduled tasks, skills, custom fields, and content module manifests (global manifests require platform admin approval). Helper uses proposals — nothing applies without your approval.
What can Helper not configure?
GitHub, inbound webhooks, feedback ingest, Publish deployments, and organization API keys remain manual in v1. Helper can still explain concepts and link you to the right settings pages.
Integrations documented here
v1 public docs include setup-oriented pages for:
- ArxDeck MCP
- GitHub
- Managed deployments (Publish)
- Content modules
- Inbound webhooks
- Feedback ingest API
Cursor Cloud, Claude Managed, OpenRouter, and the local Windows agent are supported in the product but do not have dedicated setup guides in this documentation set yet. See Agents overview.
Additional automation topics:
Capabilities and limitations
Can agents change anything without approval?
Ticket field updates and comments from active runs follow agent permissions and MCP allowlists. Configuration changes and many knowledge writes require proposal approval. Helper cannot bypass the inbox.
Does ArxDeck replace my git host or CI?
No. ArxDeck orchestrates work on tickets and connects to GitHub for repos, PRs, and optional CI-before-merge. Your code stays in GitHub; Publish deploys supported app types to managed hosting when enabled.
What is not in v1?
Examples of honest limitations:
- No versioned public documentation site
- No generated OpenAPI dump for every API — feedback ingest full reference is in-app
- No dedicated docs setup pages per cloud agent provider in this doc set
- Content module labels as global catalog resources are deferred
- External MCP tool calls are not audited inside ArxDeck
Invite-only access for now and current integration depth are intentional — see What is ArxDeck? for positioning.
Support
For access requests and product questions: contact@arxdeck.ai.
For bugs affecting your deployment, use your organization's support channel or platform feedback if enabled.