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, 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.
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 workspace-wide.
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.
Archived projects
Superadmins can archive a project from workspace settings. Archived projects are hidden from navigation and return "not found" for normal project routes until unarchived. Data is retained; nothing is deleted.