Help Center Overview
The Help Center is the fastest way to resolve setup, usage, and workflow issues without waiting for support responses.
Browse by topic first, then use troubleshooting flows to isolate root causes.
For team leads, use this page as a shared runbook during onboarding and incident response.
Account, Profile, and Security
Profile Management
Update name, phone, role title, company, location, website, avatar, and bio from the profile route.
Email is identity-linked and should remain immutable from standard profile edits.
After updating profile details, verify they reflect in both top-right avatar and dashboard bootstrap data.
Login and Lockouts
If login fails repeatedly, account lock rules may apply temporarily for security.
Wait for lock period expiry or use password recovery flows where enabled.
Ensure browser time and system timezone are correct when diagnosing lock timing issues.
Workspace and Project Administration
Membership and Roles
Only workspace admins should manage invites and role-sensitive settings.
When inviting members, validate pending invites to avoid duplicate entries and confusion.
Use consistent role definitions: admin for governance, member for execution.
Project Cleanup
Before deleting a project, confirm downstream impacts on tasks, boards, and time logs.
Schedule cleanup windows to avoid accidental data loss during active delivery periods.
Keep project naming and archival strategy documented for future audits.
Tasks, Notifications, and Activity
Status Change Notifications
When task status changes, include the actor name and the from-status to to-status transition.
If a third member updates status, notify both assignee and assigner when they are different users.
Normalize status keys before comparing to prevent duplicate notifications like inreview vs in_review.
Notification Refresh Without Reload
Use background polling and visibility/focus refresh so users see new notifications in real time.
Pause polling in hidden tabs to reduce unnecessary network usage.
Use mark-all-read actions with optimistic UI where possible for smoother UX.
Recent Activity Quality
Each activity item should capture user, workspace, project, task, action, and timestamp.
Keep action labels consistent: task_created, task_updated, task_deleted, task_status_changed.
Avoid writing low-value noise events; prioritize actions that affect execution and accountability.
Contact Support
When contacting support, include workspace ID, project ID, task ID, and exact reproduction steps.
Attach screenshots and timestamps so support can correlate logs quickly.
Provide expected vs actual behavior and whether issue is user-specific or workspace-wide.
For urgent blockers, include business impact and deadline context in the first message.