Projects
How projects, roles, and archiving work in ArxDeck.
Projects
A project is the main workspace boundary in ArxDeck. Tickets, workflows, agents, knowledge, chat, and most integrations are scoped to a project.
What lives in a project
Each project has:
- Members with a project role
- Tickets and saved ticket views
- Workflows (project-local or from installed content modules)
- Agents and workflow automations
- Labels, workflow-scoped custom fields, and knowledge items
- Settings for GitHub, webhooks, feedback, Publish, and more (admin-only)
Projects belong to an organization. See Organizations for org roles, shared credentials, and the active org switcher.
Settings hub
All project members can open Settings in the sidebar (/projects/[id]/settings). The hub groups links under:
| Group | Examples |
|---|---|
| Project | General (name, timezone), Members (invite by email or add existing org members) |
| Entities | Workflows, Agents, Skills, Labels, Ticket views, Knowledge types |
| Capabilities | Feedback, Scheduled tasks |
| Integrations | GitHub, Webhooks, Publish |
| Info | ArxDeck MCP Audit (project admins) |
Links respect role-based visibility — for example, Knowledge types appear for agent managers; Feedback and some Info entries require project admin.
Roles
Project roles control what you can do:
| Role | Typical permissions |
|---|---|
| Project admin | Manage members, workflows, agents, labels, integrations, and all ticket mutations |
| Member | Create and edit tickets, comments, chat, and knowledge; cannot change project settings |
| Viewer | Read tickets and project content; no mutations |
Platform superadmins can create projects, manage global catalogs (workflows, agents, content modules), and archive projects platform-wide.
Members
Project admins manage members at Project → Settings → Members:
- Invite member — email invitation for people outside the organization (or not yet in the org). Creates a pending invitation and sends email when mail is configured.
- Add organization member — searchable picker for accepted organization members. Grants project access immediately with no invitation or email. Organization guests can receive only Viewer; organization admins already have implicit project admin access and do not appear in the picker.
Project templates
Organization admins can create projects from project templates at /settings/org/projects/new. Templates preconfigure workflows, agents, module installs, and other defaults for new projects.
Custom fields
Custom fields are defined inline on each workflow in the workflow editor — there is no separate global or project field catalog. See Workflows.
Default workflow and views
Project admins can set a default workflow for new tickets and choose default ticket views among saved filters. Installing a content module does not automatically change your default view — admins opt in explicitly.
Configuration history
Changes to project settings, agents, workflows, and other versioned resources are recorded in History with diffs and restore. See Configuration revision history.
Archived projects
Superadmins can archive a project from platform settings. Archived projects are hidden from navigation and return "not found" for normal project routes until unarchived. Data is retained; nothing is deleted.