Team and Settings

The Settings area is where you manage your Pulse workspace: team access, SDK configuration, notification channels, and data preferences.

SDK Configuration

Navigate to Settings → SDK Configuration to find:

• API Keys — Keys used for API authentication
• Project ID — Your unique project identifier for SDK initialization

These values are needed during SDK setup.

Two types of API keys

The project API key above initializes mobile SDKs. External AI tools (Cursor, Claude Desktop) use a separate personal MCP token — see Personal Access Tokens (MCP) below.

Personal Access Tokens (MCP)

External AI assistants connect to Pulse through Pulse MCP using a personal access token — not the project SDK API key.

1. Open the profile menu (avatar, bottom-left) → Personal Access Tokens under Access (route /account/tokens)
2. Click Generate New Key, enter a name, and click Generate
3. Copy the key immediately — it is shown only once
4. Keys are prefixed with pulse_mcp_ and are used as PULSE_API_KEY in MCP client config

	Project SDK key	Personal MCP token
Used for	SDK initialization in your app	IDE and MCP clients (Cursor, Claude Desktop)
Created in	Settings → SDK Configuration	Profile menu → Personal Access Tokens
Prefix	(project key format)	pulse_mcp_

See Pulse MCP setup for client configuration.

Team Management

Inviting Members

1. Go to Settings → Team
2. Click Invite Member
3. Enter their email address and assign a role

Roles

Role	Permissions
Admin	Full access: manage team, settings, billing, interactions, alerts
Member	View and investigate: access dashboard, interactions, session replays, PulseAI
Viewer	Read-only: view dashboards and interactions, no configuration changes

Notification Channels

Configure where alerts are delivered. See Alerting for details on setting up:

• Email
• Slack
• PagerDuty
• Custom webhooks

Environment Configuration

Pulse supports multiple environments (e.g., production, staging) to keep telemetry separated:

• SDK sends an environment global attribute
• Dashboard filters by environment
• Alerts can be scoped to specific environments

Data Retention

Pulse retains telemetry data based on your plan:

Data Type	Retention
Session data	Based on plan tier
Interaction metrics	Based on plan tier
Session replays	Based on plan tier
Aggregated metrics	Extended retention for trend analysis

Contact your Pulse account team for details on retention policies for your plan.

Next Steps

• Quickstart — Use the SDK configuration values to set up your first integration
• Alerting — Configure notification channels
• Dashboard Overview — Navigate the Pulse web portal