Settings & administration
Settings is where you administer a Pulse workspace. It brings together workspace-level controls, personal preferences, and management surfaces for every major product capability in one place.
Workspace administration
Workspace admin covers the controls that govern the whole team:
| Area | What it controls |
|---|---|
| Users | Members of the workspace |
| Roles | Permissions assigned to members |
| Invitations | Bringing new people into the workspace |
| API tokens | Admin-managed access credentials for approved technical connections |
| Feature flags | Enabling and disabling features |
| Usage quotas | Limits on consumption |
These settings define who is in the workspace, what they can do, and how the workspace's capacity is bounded.
Personal settings
Alongside workspace admin, each user has personal settings for their own preferences. These are scoped to you and do not affect the rest of the team.
Managing Pulse capabilities
Most of Pulse's capabilities have a dedicated management area in settings:
- Integrations — connect and manage provider integrations
- Skills — review the available skill library
- Memory — curate facts and set write policy
- Tasks — view and manage scheduled and recurring tasks
- Approvals — review requests and configure policies
- Webhooks — create incoming webhooks and configure listeners
- Devices — manage connected devices
- Files and storage — manage the workspace file system
Each area is the control surface for the corresponding capability, so configuration lives next to the feature it governs.
Usage and plan tracking
Settings also tracks usage and plan. You can see consumption against your quotas and understand where the workspace stands relative to its plan, which pairs with the usage quotas set in workspace admin.
Sharing policies
Sharing policies are configured here too. They set the defaults that govern how files and resources are shared and revoked, giving admins control over how work leaves the workspace.
TIP
Use roles and approval policies together. Roles decide who can configure what, while approval policies decide which agent actions still require a human — two layers of control over the same workspace.
One place to govern Pulse
Because Pulse spans timeline, tasks, approvals, integrations, skills, memory, files, voice, devices, and webhooks, settings is the single place those pieces are administered. It is where an admin shapes how the assistant behaves for the whole team.
Use the Developer Hub when a technical team needs to use API tokens or custom webhook implementations.