Getting started
How to request access, sign in, and orient yourself after your first login.
Getting started
This guide walks through onboarding by ArxDeck permission level — not job titles. Everyone starts with the same basics; project admins and organization admins have additional setup paths.
ArxDeck Helper is available in every project. At any step you can ask Helper how to do something in plain language, or ask Helper to propose configuration changes you review and approve in Proposals. See ArxDeck Helper.
Before you have an account
ArxDeck is invite-only for now. Self-serve signup is planned later this year. To get access today:
- Contact the ArxDeck team at contact@arxdeck.ai and describe your use case, or ask your organization's ArxDeck admin to send you an invite.
- Watch for an invitation email with a link to accept the invite. Your admin may also share the link directly if email delivery is unavailable on their deployment.
- Create an account (email/password or Google, if enabled for your deployment) or sign in at workspace.arxdeck.ai if you already have credentials.
There is no public signup form on the marketing site. An invitation is required.
Everyone — first steps
Once authenticated, follow this path:
- Open the dashboard — you see projects you belong to in the active organization (or an empty-state welcome if none are assigned yet).
- Open a project — select a project from the sidebar. If your invite was project-scoped, that project appears automatically. Organization-wide invites may require an admin to add you to specific projects.
- Browse tickets — open Tickets to filter, sort, and open ticket detail pages.
- Create or view tickets — members and admins with create permission can add tickets; viewers can read existing work.
- Use project chat — start a conversation from the chat launcher in the top bar. Pick an agent, optionally pin knowledge, and ask questions about the project.
- Explore knowledge — browse durable project memory under Data → Knowledge.
Your project role (admin, member, or viewer) determines whether you can change settings, edit tickets, or only read. See Projects for role details.
Stuck on any step? Open New helper chat from the chat launcher and ask Helper what to do next — for example, "How do I create a ticket?" or "Where do I find project chat?"
Project admins — configure the project
If you are a project admin, continue with setup through the Settings hub (/projects/[id]/settings). The hub groups links under Project, Entities, Capabilities, Integrations, and Info.
Typical admin path:
- Settings → General — confirm project name and timezone (calendar schedules use project timezone).
- Settings → Workflows — install or create workflows, set a default workflow, add automations and task templates.
- Settings → Agents — configure agents for chat, automations, and ticket runs. See provider setup guides: Cursor Cloud, Claude Managed, OpenRouter.
- Settings → GitHub — connect a repository for repo-backed agents and docs browse.
- Settings → Members — invite collaborators to the project.
- Optional: Settings → Webhooks, Feedback, Publish, Skills, Labels, Ticket views, and Knowledge types as your workflow requires.
Prefer guided setup? Click Help me set this up on any admin detail page, or ask Helper in chat to propose workflows, agents, scheduled tasks, skills, GitHub settings, webhooks, feedback config, or Publish configuration. Approve proposals in Project → Proposals.
Review Configuration revision history to understand how approved changes are tracked with diffs and restore.
Organization admins — members, credentials, and projects
If you are an organization admin, you also manage tenant-wide resources at Organization in the sidebar (/settings/org). The hub lists compact rows:
| Row | Purpose |
|---|---|
| Members | Invite and manage organization members |
| Projects | Create, archive, and manage projects (including from project templates) |
| API keys | Provider credentials shared across projects (CURSOR_API_KEY, ANTHROPIC_API_KEY, OPENROUTER_API_KEY, etc.) |
| MCP servers | External MCP endpoints agents can call |
| Voice | Organization speech-to-text provider and idle protection |
| Deployments | Publish limits and budgets |
Typical org-admin path:
- Organization → Members — invite team members to the organization.
- Organization → API keys — configure provider credentials before agents can run.
- Organization → Projects — create projects (or use Create project on the dashboard empty state). New projects can start from templates at
/settings/org/projects/new. - Add members to projects via Settings → Members on each project (org admins have implicit project admin on all active projects).
Optional next steps
When you are ready to go deeper:
- Workflow automations — define what happens when a ticket enters a status
- Task templates & runs — multi-step automated jobs on tickets
- Scheduled tasks — recurring agent jobs without a ticket
- Integrations overview — MCP, GitHub, Publish, webhooks, and feedback ingest
Related
- What is ArxDeck? — product overview and access model
- Projects — roles and project structure
- Organizations — org vs project boundaries
- ArxDeck Helper — guided setup via proposals
- FAQ — access, limitations, and support