FAQ

Complete guide for how Pulsar removes setup friction across onboarding workspaces projects tasks files messaging integrations billing and support.

71 of 71 answers

Start

Create workspace and invite core team

Set roles first then connect labels and integrations.

Operate

Run projects tasks files and CRM

Use one workspace surface for execution and delivery.

Scale

Connect integrations and reporting

Add GitHub Claude Vercel and exports as the team grows.

Most Used Answers

Getting Started

How Pulsar is structured and what to do first.

Workspaces and Access

Workspace switching, invites, external memberships and roles.

Projects and Tasks

Project planning, task execution, assignment and status flow.

Calendar and Timers

Scheduling, timeline views and tracked time.

CRM

Contacts, labels, pings, imports and company folder structure.

Files and Explorer

File operations, preview, access rules and external sources.

Messages and Notifications

Internal chat UX, conversation types, mentions and alert center.

Analysis, Reporting, Action Center

Operational visibility, exports and activity feed.

Integrations

Catalog behavior, enablement model and provider setup.

Claude Assistant

Workspace co-worker behavior, model selection and chat workflow.

Billing, Pricing and Payments

Plans, quotas, upgrades, wallet guard and payment modules.

Security and Compliance

2FA, CSRF, rate limiting, role enforcement and data safety.

Support and Ticketing

How support requests and replies work.

Customer Journey

Journey map projects, persona blocks and audience planning.

Troubleshooting

Fast checks for common issues.

Need support beyond FAQ?

Contact support with detailed repro steps or start your workspace and test flows directly.