Team & Settings
Manage users and team members, configure project roles, system roles, phase types, and all system settings in ArchiJAM.
Team & Settings
Team (/team)
The Team page shows a card grid of every user in the system.
Each card displays:
- Avatar (initials with the user's chosen background color, or a photo if uploaded)
- Full name and job title
- Email address
- System role badge
- Presence dot (colored circle based on current presence status)
Search Real-time filter across name, email, and job title.
Role filter Dropdown to show only users with a specific system role.
Editing a user (admin) Admins see an Edit button on every card. Clicking opens a slide-over form with all user fields:
- First and last name, email, job title
- Cell and work phone
- Start date, birth date
- Office location
- System role and admin flag
- Manager (used for time approval routing)
Editing your own card (non-admin)
Non-admin users see an Edit button on their own card only, which links to /profile.
System Settings (/settings)
System Settings is accessible to admin users only. It is organized into tabs.
Tab: Company
- Firm Name — displayed in the sidebar and app header
- Office Locations — a list of offices with name, address, timezone, and abbreviation. Used for user assignment and the
{LOC}project number token. - Currency — default USD; select from a list
- Language — English (North American) is the only available language currently
Tab: Users
A table of all users with avatar, name, email, system role badge, and admin flag.
Adding a user Click Add User. Fill in email, first name, last name, password, job title, system role, and admin flag. Returns a 409 error if the email already exists.
Editing a user Click the edit control on any row to open the user slide-over. Admins can change any field including system role, admin flag, and email. A reset password action emails the user a link to set a new password.
Tab: Project Roles
Project roles define the functional positions on a project (e.g. Project Manager, Architect, Structural Engineer). They are assigned to team members per project.
Each role has:
- Name and color
- Permission tags (e.g. can edit dates, can add tasks)
- Single-user flag — when enabled, only one person can hold this role on a given project
- Billable rate
Adding a role Click Add Role. Fill in name, color, permissions, and single-user flag.
Deleting a role Blocked if the role is currently assigned to any team member on any project.
Tab: App Roles
App roles control which modules and actions each user can access. They are separate from project roles — project roles are per-project; app roles govern app-wide access.
Permission matrix
| Module | Available actions |
|---|---|
| Projects | view, create, edit, delete |
| Tasks | view, create, edit, delete |
| Pipeline / Opportunities | view, create, edit, delete |
| Contacts & Companies | view, create, edit, delete |
| Time Tracking | view, create, submit, approve |
| Team | view |
| Reports / Dashboard | view |
projects.createis permanently blocked for Limited Users and Guests regardless of app role.
Default app roles (cannot be deleted):
- Full Access — all permissions enabled
- Limited Access — view + edit for most modules; no delete
- Read Only — view only across all modules
Permission evaluation order (per API call):
isAdmin = true→ full access- Tier hard block (guest non-view, limited_user project create) → 403
- Assigned app role permissions → allow/deny
- No app role → fall back to tier defaults
Tab: Phase Types
The global list of phase types used when adding phases to projects. Columns: abbreviation, name, color swatch.
Controls: inline name/abbreviation editing, color picker, up/down reorder, remove, and Add Phase Type button. Changes save via PUT /api/settings. Existing project phases are not retroactively modified.
Tab: Project Numbers
Configure how project numbers are generated.
Pattern tokens
| Token | Output |
|---|---|
{YYYY} | 4-digit year (e.g. 2026) |
{YY} | 2-digit year (e.g. 26) |
{###} | Auto-incrementing counter, zero-padded to 3 digits |
{LOC} | Office location abbreviation |
Click the token buttons to insert them into the pattern field at the cursor position. A live preview shows the next three project numbers that would be generated.
Counter Reset — Annually, Quarterly, Monthly, or Never.
Current Counter — editable integer; advance or reset manually.
Tab: Working Days & Holidays
Working days Checkboxes for Mon–Sun. Default is Mon–Fri. Affects all milestone date calculations.
Holidays A list of dates with a label and optional recurring toggle. Add or remove entries. Changes take effect on the next milestone calculation.
Tab: Time & Leave
Controls the time tracking behavior:
- Week start day (e.g. Monday or Sunday)
- Standard workday hours (used to flag over-logged days)
- Time entry intervals
- Submission and approval workflow — enable/disable, set regularity (daily, weekly, bi-weekly, monthly), and configure approval routing
- Non-billable categories (PTO, Sick, VTO, Administrative, etc.)
Tab: API Clients
Create and manage OAuth2 client credentials for external automation tools (e.g. n8n).
Adding a client
Enter a name and optional description. A clientId and clientSecret are generated — the secret is shown only once.
Revoking a client Removes the credentials. Any integrations using that client will immediately lose access.
The table shows client name, creation date, and last-used timestamp.
Tab: Integrations
Formbricks webhook Accept inbound leads from web forms via Formbricks.
- Enable toggle — activates
POST /api/webhooks/formbricks - Webhook URL — displayed with a copy button; paste this into Formbricks
- Webhook secret — optional HMAC-SHA256 signature verification; paste the secret from Formbricks
- Field mapping — map Formbricks question IDs to ArchiJAM opportunity fields (name, company name, contact name, contact email, description, estimated fee)
See Pipeline & Contacts for how incoming leads appear in the pipeline.