Skip to content

Admin and security

The controls your risk team will ask about, already in place.

Roles and permissions, two-step verification, maker-checker approvals and a record of sensitive actions.

The problem

A WhatsApp tool that anyone can sign in to, where anyone can send to everyone and nothing is logged, will not pass a vendor risk review.

How Senderr solves it

  • The right access for each person

    Owner, admin and member roles, with extra permissions per member, such as who may build campaigns.

  • Two-step verification

    An organisation can require it for every member. Senderr refuses access until it is set up.

  • A record of what happened

    Sensitive actions such as approvals, number changes, exports and setting changes are written to an audit trail that cannot be edited.

See it work

What it looks like in Senderr

A member builds a campaign and submits it. The approval request reaches an admin, who approves it, and the action appears in the audit trail with who, what and when.

What's included

  • Owner, admin and member roles, with per-member permissions
  • Maker-checker approvals with a named approver role
  • Two-step verification (authenticator app), enforceable per organisation
  • Each client's data separated in the database, with automated cross-client tests
  • Business tokens encrypted with AWS Key Management Service
  • Phone numbers masked and message text removed from logs and error reports
  • Astitva staff work in a separate admin console with two-step verification, short sessions and their own audit trail
  • Audit trail export, prepared by Astitva on request
Coming soon

single sign-on (SAML) and SCIM, audit log inside Senderr, phone number masking by role, IP allow-lists

Share this with your security team