Clear boundaries. Better trust.

People share more than data at work. They share context, concerns and progress. Understand how Pulsewise separates those records, and review the access your team needs.

Start a security review Explore the boundaries
Different records. Different purposes.
Team patternsPulse & moodWorkspace Health

Understand the group experience. Manager-facing insights focus on aggregate patterns, with visibility governed by your workspace.

Individual contextContribution evidenceReputation & growth

Kudos, feedback, goals, todos and completed 1:1 activity provide named contribution context. Private 1:1 notes and anonymous mood responses are not score inputs.

Everyday recordsPeople, time & payHR workflows

Employee records, time off, attendance and payroll serve operational purposes, with access based on roles and permissions. They are separate from health and reputation scoring.

Explore each boundary. Confirm the roles and settings for your workspace during a review.

Start with the purpose.
Then define the access.

One platform includes different kinds of people information. Each deserves a clear reason for collection and a clear audience.

Listening to the team

Pulse and mood responses inform aggregate Workspace Health and suggested team actions. Managers explore patterns to guide a conversation, with visibility governed by workspace settings.

Explore team listening

Understanding a person’s contribution

Named feedback, recognition, goals and completed 1:1 activity provide individual context. Private 1:1 notes and anonymous mood responses do not feed a named Reputation Score.

Understand the contribution view

Supporting everyday work

People records, leave, attendance, pay and expense workflows have operational purposes and their own permissions. Their existence in the platform does not make them health or reputation scoring inputs.

Explore people & HR

AI connections.
Your access rules.

Your permissions travel with you

Pulsewise MCP lets an assistant act as the person who connects it, within their existing permissions. Choose Read only or Read and act when connecting. Before approving or rejecting leave and attendance requests, or checking in, the assistant asks for confirmation.

Access you can end

Disconnect your apps in Settings, MCP. Account admins can review connected apps, revoke any connection or turn AI connections off for the account in Settings, AI connections. Revocation stops access immediately.

Keep the data boundary clear

Through MCP, pulse scores are aggregate and small groups show no score. Survey responses, review submissions, ratings and configuration controls stay in the app. Data handling and model training policies depend on the AI provider you choose.

Explore MCP access controls

A review built around
your requirements.

Bring your questions early. We’ll work through the current product and documentation, with clear distinctions between what’s available and what’s planned.

  1. 1

    Map the data you need

    Start with the workflows you plan to use. Identify which employee records, listening responses and operational details will be involved.

    Which records are needed, and for what purpose?
  2. 2

    Agree who can see what

    Review the employee, manager and administrator roles against your policies. Consider access to named records, aggregate insights and exports separately.

    Who needs access? Who should not have it?
  3. 3

    Confirm the requirements

    Bring identity, hosting, retention, deletion and contractual requirements. Review the available evidence and distinguish current controls from roadmap items.

    What needs to be in place before we start?
  4. 4

    Explain the boundary to your team

    Make it clear what employees are sharing, who can see it and how it will be used. Align your rollout and internal policy with the configuration you choose.

    Would an employee understand what happens to their information?

Know what’s available.
Know what’s planned.

Identity requirements

SSO and SAML are roadmap items. If they’re a requirement for your organization, discuss that before deciding how to proceed.

Policies and agreements

Review the public policies alongside your organization’s requirements. Ask us about the current agreement and any additional documentation your team needs.

Clear answers
before you begin.

Can a manager identify an anonymous pulse response?

Manager-facing pulse and mood reporting is designed around aggregate team patterns rather than named responses. Authorized administrators may have broader access according to workspace configuration and policy. Document the exact boundary and explain it to employees during onboarding.

Are all records anonymous?

No. People records, direct feedback, kudos, goals, 1:1 records and individual Reputation concern named people. Their access rules are distinct from aggregate pulse and mood reporting.

Do private 1:1 notes or anonymous mood responses affect a named Reputation Score?

No. Individual Reputation uses contribution evidence such as kudos, feedback, goals, todos and completed 1:1 activity. Private 1:1 notes and anonymous mood responses are not inputs to that score.

Does Pulsewise support SSO or SAML today?

SSO and SAML are on the roadmap. Bring your identity requirements to a security review so we can distinguish current authentication controls from planned work.

Can we review security documentation and data-processing requirements?

Yes. Contact [email protected] with your questionnaire, DPA request or procurement requirements. We will review the current controls and agreement with you. Confirm any required certifications, hosting, retention or deletion commitments before relying on them.

Bring your security questions.

Let’s review the access model, current controls and requirements for your team.