Security

Your client context. Your control.

Clear permissions. Workspace access controls. Read-only Gmail access.

Read-only Gmail permission Workspace access controls

rapportstudio · security

Workspace access controlsEnabled
Authenticated connectionsEnabled
Gmail permission requestedgmail.readonly

Read-only. Matched. Nothing else.

Gmail uses a read-only permission. It does not grant permission to send, edit or delete messages.

  • gmail.readonly, not gmail.modify or gmail.send
    The Gmail connection requests read-only access. It does not grant permission to send, edit or delete messages.
  • Matched to known client domains only
    Messages are matched to known client domains or saved contact addresses before they are stored and analysed as client conversations.
  • Disconnect in one click
    Revoking access is immediate and available from your own settings at any time, no support ticket required.

Gmail permission requested

scope: https://www.googleapis.com/auth/gmail.readonly

✕ Cannot send email

✕ Cannot delete email

✕ Cannot modify labels or folders

✓ Read permission covers Gmail messages; Rapport filters stored conversations to known clients

Your agency’s information stays within its workspace.

Access follows the person’s role and client assignment.

  • Client ownership
    Account managers can open their assigned client records. Managers can review clients across their workspace.
  • Source permissions
    Access to a call or assigned action does not automatically grant access to the full client record.
  • Controlled management
    Changes to client ownership and serious risk periods require manager permissions.

rapportstudio · security

Workspace access controlsEnabled
Authenticated connectionsEnabled
Gmail permission requestedgmail.readonly

How access is protected.

Controls used across the application and API.

Encrypted in transit

Every connection to Rapport Studio runs over HTTPS. Nothing is sent in the clear.

Passwords protected by hashing

Passwords are hashed before they ever touch the database. Nobody at Rapport Studio can read yours.

Rate limited

API and authentication routes apply request limits to reduce repeated login attempts and abuse.

Validated inputs

Input checks and access controls protect application routes. Checks depend on the operation being performed.

Security headers enforced

Standard protections against clickjacking, sniffing and injection are on by default, not opt-in.

Workspace activity logged

Actions inside your workspace are recorded to an audit trail your team can review.

Access matches the role, nothing more.

Account managers see their own clients. Managers see the whole agency. Rapport Studio's own team never touches your data through your account.

  • Role-based access
    What a teammate can see is scoped to their role, not an all-or-nothing switch.
  • Internal tooling, fully separated
    Staff who support your account use a different login system entirely, with its own access controls.
  • Review your requirements
    Talk to us about your access and compliance requirements before connecting your team.

Account separation

Your workspace

Account managers, leads, owners

Rapport Studio staff

Separate login system, separate database table

There is no shared account table between the product and internal tooling. Customer and staff access use separate authentication and role checks. Staff tools still require controlled access to shared service data.

Questions your security team would ask, answered.

Happy to walk your IT or security lead through this directly before you connect anything.