ProductTeam & roles

Reps see their own. Managers see the team.

Invite people with a role, a market and a scope. Own-scope reps see only their prospects and everything linked to them, enforced by the database rather than the screen. Everyone sends from their own mailbox, managers get a view per person, and when someone leaves, one handover moves their work.

Book a demoHow it works
Settings · Team
SWSanne de WitOwner
JHJoost HendriksAdmin
IMInge MulderEditor
PVPieter VosEditor
LKLisa KokEditor

Manager view · this week

SentRepliesCallsMeetingsInge Mulder16814524Pieter Vos14211613Lisa Kok966482

No leaderboard. Reps see their own numbers; read marks stay private.

How it works

Four moments in the life of a team.

Someone joins, works their own prospects, gets measured fairly, and one day leaves. Each moment has one place in PEMAX and one rule in the database underneath it.

Joining

Invite with a role, a market and a scope.

Four roles in rising rank: viewer, editor, admin and owner. An admin works in the markets they administer, or across the workspace. Every team change goes through one rule: you never touch someone who outranks you and never grant above your own rank.
  • Own scope is for viewers and editors; promoting someone to admin resets it.
  • The invite link is shown once and only its fingerprint is stored. It is valid for 14 days.
  • Send it from your own connected mailbox as a plain, untracked email, or copy it.
  • The last owner can never be demoted, deactivated or removed.
Team · Invite a member

Email

femke.bos@brightwater.example

Role

ViewerEditorAdminOwner

You can grant up to your own rank, never above it.

Scope

Own prospectsWhole market

Own scope exists for viewers and editors only.

Market

NL NetherlandsEurope/Amsterdam

Delivery

Send from my mailboxjoost@brightwater.example · plain, untrackedCopy the linkshown once
Valid 14 days · only its fingerprint is storedSend invite

Working

Own scope is a database rule, not a filter.

A restrictive row-level policy on every prospect-linked table narrows an own-scope member's session to their own rows, and every write path checks the same rule again. Nothing depends on which screen they use or what the browser asks for.
  • A new prospect is owned by whoever created it; ownership is written on every path.
  • Own-scope members can only create rows they own and cannot move ownership.
  • Admins and owners are never narrowed: they see the whole market or workspace.
Prospects · the same table, two people
IMInge · Editorown scope
Mila VisserStroomlijn BVIM
Emma LindqvistKanaal KoeltransportIM
Fleur JansenVos & PartnersIM

3 of 6 · plus their threads, calls, runs, tasks and meetings

SWSanne · Ownerwhole workspace
Mila VisserStroomlijn BVIM
Daan KuipersKuipers TransportPV
Emma LindqvistKanaal KoeltransportIM
Noor BakkerDelta FreshJH
Fleur JansenVos & PartnersIM
Bram de GrootGroot DistributiePV

Not a filter in the browser: a restrictive row-level policy on every prospect-linked table decides what each session can read or write.

Measuring

A manager view per person, without a leaderboard.

Per person: emails sent, replies and positive replies, calls made and connected, talk time from the call provider's own timestamps, meetings booked and leads handed to your CRM. Corrected reply labels count, not the classifier's first guess.
  • Admins and owners see the team; a rep sees their own row.
  • The CSV export carries the same columns and the same rows.
  • Per-person attribution is cleared after 365 days by default, so the view only covers that window.
Analytics · Team · last 7 days
IMInge Mulder4 to CRM
Sent
168
Replies
14
Positive
5
Calls · conn.
52 / 19
Talk
1h 42m
Meetings
4
PVPieter Vos3 to CRM
Sent
142
Replies
11
Positive
3
Calls · conn.
61 / 22
Talk
2h 05m
Meetings
3
LKLisa Kok2 to CRM
Sent
96
Replies
6
Positive
2
Calls · conn.
48 / 15
Talk
1h 11m
Meetings
2
Admins and owners see the team. A rep sees one row: their own.Export carries the same rows

Leaving

Leaving is a handover, not a cleanup.

“Remove and hand over to …” moves everything a person owns in one transaction and shows you the counts before it changes anything. Their mailboxes leave rotation, their personal settings go, and what the law or your windows say to keep is kept on schedule.
  • Hand over to a colleague, or unassign the work back to the pool.
  • The schedule of what is kept, and until when, is written to the audit row.
  • Members can leave by themselves; their work goes to the owner.
Pieter Vos · Remove and hand over
PVJHJoost HendriksAdminor unassign everything

Moves to Joost

  • Prospects owned42
  • Live sequence runs17
  • Open tasks6
  • Unsent emails9
  • Queued power-dial entries3

Ends now

  • pieter@brightwater.example archived, out of rotation
  • Its mailbox credentials disabled
  • Booking page and personal settings removed
  • Sessions in this workspace ended

Kept on schedule

  • Attribution on past workuntil 6 Nov 2027
  • Recordings and transcriptsper call retention
  • Security audit rows730 days
One transaction · one audit row with the scheduleRemove and hand over

Access you can account for

Every person, every session, every exit on record.

  • Two-step sign-in

    TOTP with any authenticator app. Require it for nobody, for admins (the default) or for every member in one click. The check sits where every request gets its authority, and fails closed.

  • A login trail

    Sign-ins, sign-outs, password and second-factor changes, with IP address and user agent. Every person sees their own; owners see the workspace's security trail.

  • Mailboxes belong to people

    Each rep connects their own Google Workspace mailbox. Rotation never borrows a colleague's; without a mailbox, a rep's runs pause visibly and resume the moment they connect one.

  • Reassign in bulk

    Admins select prospects and assign them to someone else. Live runs, open tasks and unsent emails move with them, and each prospect gets its own audit row.

  • Removed means signed out

    Removing or suspending a member ends their sessions in this workspace, never in another one. A token already issued expires within ten minutes; we say so rather than pretend it is instant.

  • Staff access you can see

    When Mape staff act inside your workspace for support, entry and exit are audited and visible to owners. A lost second factor is reset only by staff, with a reason, and the member is told.

  • Exports with a gate

    Exporting a whole market is for admins. Every member can take a personal export of their own data, three a day, each one audited.

  • Erasure that sticks

    An admin can erase a prospect under the GDPR. Personal data is anonymised across messages, calls and tasks; the suppression entry stays, so nobody contacts that person again by accident.

  • Private read marks

    Opening a thread marks it read for you only. A manager never sees when a rep read what, and nobody can clear someone else's unread.

Details

Who can do what.

Four roles, one rank order. Every row of this table is checked on the server and in the database, never only by hiding a button.

An admin can hold the role for one market or for the whole workspace. Mape staff are not members: they act inside a workspace only for support, and every act-as is audited and shown to owners.

  • Read prospects, conversations and calls in their markets

    • Viewer: yes
    • Editor: yes
    • Admin: yes
    • Owner: yes

  • Can be limited to their own prospects (own scope)

    • Viewer: yes
    • Editor: yes
    • Admin: no
    • Owner: no

  • Add or import prospects, record a lawful basis

    • Viewer: no
    • Editor: yes
    • Admin: yes
    • Owner: yes

  • Search and enrich with Apollo

    • Viewer: no
    • Editor: yes
    • Admin: yes
    • Owner: yes

  • Connect and send from their own mailbox

    • Viewer: no
    • Editor: yes
    • Admin: yes
    • Owner: yes

  • Edit or clear a recorded lawful basis

    • Viewer: no
    • Editor: no
    • Admin: yes
    • Owner: yes

  • Reassign prospects to a colleague

    • Viewer: no
    • Editor: no
    • Admin: yes
    • Owner: yes

  • Invite, change and remove members, up to their own rank

    • Viewer: no
    • Editor: no
    • Admin: yes
    • Owner: yes

  • See the whole team in the manager view

    • Viewer· own row
    • Editor· own row
    • Admin: yes
    • Owner: yes

  • Export a whole market

    • Viewer: no
    • Editor: no
    • Admin: yes
    • Owner: yes

  • Erase a prospect under the GDPR

    • Viewer: no
    • Editor: no
    • Admin: yes
    • Owner: yes

  • Connect the Apollo key, set the credit budget

    • Viewer: no
    • Editor: no
    • Admin: yes
    • Owner: yes

  • Compliance, retention and sign-in security settings

    • Viewer: no
    • Editor: no
    • Admin· workspace-wide
    • Owner: yes

  • Spend cap and billing

    • Viewer: no
    • Editor: no
    • Admin· read only
    • Owner: yes

  • Make someone owner

    • Viewer: no
    • Editor: no
    • Admin: no
    • Owner: yes

  • Switch off review of AI-drafted steps

    • Viewer: no
    • Editor: no
    • Admin: no
    • Owner: yes

  • See staff act-as in the security trail

    • Viewer: no
    • Editor: no
    • Admin: no
    • Owner: yes

  • Leave the workspace (work goes to the owner)

    • Viewer: yes
    • Editor: yes
    • Admin: yes
    • Owner: no

FAQ

Questions we get

Can a rep see a colleague's prospects?
Not when they have own scope. They see their own prospects and everything linked to them: threads, messages, sequence runs, calls, recordings, meetings and tasks. Shared assets such as sequences and campaigns stay visible to the whole team. Because de-duplication runs across the workspace, two reps still cannot contact the same person twice.
What does a manager see that a rep does not?
Admins and owners see the team rows of the manager view (emails sent, replies, positive replies, calls made and connected, talk time, meetings, leads handed to the CRM) and the per-market table on the dashboard. A rep sees their own row. There is no ranking shown to the team.
What happens to a rep's work when they leave?
An admin opens “Remove and hand over to …”, sees a preview, and confirms. Prospects, live runs, open tasks, unsent emails and queued calls move to the colleague you pick; the leaver's mailboxes are archived and their sessions end. Attribution on past work stays for its retention window, then it is cleared.
Can an admin make themselves owner?
No. Nobody can grant a role above their own, change someone who outranks them, or change their own row. Making someone owner is an owner's action, owners are workspace-wide, and the last owner can never be demoted or removed.
Is two-step sign-in required?
By default for admins and owners. An owner or workspace admin can require it for every member with one click, and the team notice in Settings states the policy in force. Codes come from any TOTP authenticator app.
Can Mape staff see our data?
Only by acting inside your workspace, for support. Every entry and exit is audited and shown to owners in the workspace security trail. Staff cannot use personal account pages while acting. More on the security page.
What do we tell our team about what PEMAX records about them?
Settings holds a notice, “Data we record about team members”, that every member can read. You can edit the text; the lines about how long data is kept and about sign-in security are generated from the settings in force, so they cannot go stale. Voices are never analysed for emotion, tone or enthusiasm.

One workspace

Works with the rest of PEMAX

Put your reps on it, keep your view of them.

We set up a workspace with an owner, an admin and two own-scope reps, and show you what each of them sees, what the manager view counts and what happens when one of them leaves.

Book a demoSign in

Invite-only workspaces · Hosted in the EU · Bring your own keys