Skip to main content

​
Overview

Every useful connector needs a clear answer to one question: what is the assistant allowed to do for this user right now? Satsuma designs and implements the authorization layer for your connector so customers can safely connect their account, grant the right access, and revoke it when needed. We align with your existing identity system instead of inventing a parallel account model.

​
What Satsuma Owns

Account Linking

The customer-facing flow that lets a user connect their product account from an AI assistant.

Consent UX

Clear authorization screens and confirmation moments before sensitive actions run.

Token Handling

Secure storage, refresh behavior, expiration handling, and revocation support for connected accounts.

Permission Mapping

Translation from assistant-visible tools to the scopes and roles your backend already understands.

​
What Your Team Provides

  • Identity provider details, including OAuth, SSO, or custom auth requirements
  • Available scopes, roles, and permission boundaries
  • Test users for staging and production validation
  • Revocation requirements and account deletion behavior
  • Legal or compliance language that must appear in the consent flow

​
Authorization Model

Satsuma keeps authorization explicit at three levels:
  1. Account access: the user connects the assistant to the correct account or workspace.
  2. Tool access: the connector only exposes actions the user is allowed to perform.
  3. Action confirmation: higher-impact actions can require a visible confirmation before completion.

​
Security Expectations

Do not send long-lived secrets, production credentials, or customer data through email or chat. Satsuma will coordinate secure credential exchange during implementation.
Production connectors should include:
  • Least-privilege scopes for every assistant action
  • Separate staging and production credentials
  • Auditability for account linking, token refresh, revocation, and sensitive actions
  • Clear handling for expired, missing, or revoked authorization
  • A support path for customers who need to disconnect or reconnect their account

​
Launch Checklist

  • Identity provider and auth flow confirmed
  • Required scopes mapped to connector actions
  • Consent copy approved
  • Staging credentials validated
  • Token expiration and revocation tested
  • Production credential exchange completed securely