Roles & Permissions

Available via: Dashboard only

Every action in the Inflow Dashboard is gated by an atomic permission of the form resource:action, where the action is either read or write:

read — view the resource (lists, details, exports).
write — create, modify, or trigger actions on the resource. Write always implies read.
No permission — the resource is not accessible at all (default deny).

Each member gets their permissions from their role: one of the four built-in roles (a fixed permission preset) or a custom role (a permission set you define). See Team & Members for inviting members and assigning roles.

Permission Resources

Permissions are grouped into four families:

Family	Resources
Treasury & outgoing funds	Balances & accounts, payouts, auto-payout, payout policy, swaps, virtual accounts, deposits
Payments & operations	Payments, checkout sessions, payment links, subscriptions, subscription offers, products & prices, coupons, customers, disputes, activity
Developers	API keys & SDK, webhooks
Organization	Team members, merchant settings, onboarding, Connect / marketplace, affiliates

Built-in Role Presets

The four built-in roles are presets over this catalog. Legend: Read & write — full access; Read — view only; — — no access.

Treasury & Outgoing Funds

Resource	Owner	Admin	Member	Viewer
Balances & accounts	Read & write	Read & write	Read	Read
Payouts (execute, approve, cancel)	Read & write	Read & write	Read	Read
Auto-payout configuration	Read & write	Read & write	Read	Read
Payout policy & signers	Read & write	—	—	—
Swaps	Read & write	Read & write	Read	—
Virtual accounts	Read & write	Read & write	Read & write	Read & write
Deposits	Read & write	Read & write	Read & write	Read & write

Payments & Operations

All four built-in roles have read & write access to the whole family: payments (including refunds and captures), checkout sessions, payment links, subscriptions (including cancellations and waitlists), subscription offers, products & prices, coupons, customers, disputes, and the activity feed.

This means every built-in role — including Member and Viewer — can manage subscriptions: change plans, cancel, pause, approve waitlists, and edit offers. If you need teammates who can only view this data, use a custom role that grants read without write on these resources.

Developers

Resource	Owner	Admin	Member	Viewer
API keys & SDK	Read & write	Read & write	—	—
Webhooks	Read & write	Read & write	Read & write	Read & write

Organization

Resource	Owner	Admin	Member	Viewer
Team members & invitations	Read & write	Read & write	Read	Read
Merchant settings & integrations	Read & write	Read & write	Read & write	Read & write
Onboarding & KYC	Read & write	Read & write	Read & write	Read & write
Connect / marketplace	Read & write	Read & write	Read & write	Read & write
Affiliates	Read & write	Read & write	Read & write	Read & write

Beyond Permissions

A few rules apply on top of the permission matrix:

There is exactly one Owner per account, and only the Owner can promote another member to Owner or delete the account.
Only Owner and Admin can be picked as signers in the Payout Policy.
Some sensitive actions additionally require step-up Two-Factor authentication, regardless of role.

Custom Roles

When the built-in presets don't fit — for example, a support teammate who should handle subscriptions but never touch offers or payouts — you can create custom roles with an exact permission set.

Go to Settings → Members → Roles in your Dashboard.
Click Create Role, name it, and toggle read / write per resource.
Assign the role to members like any built-in role.

Custom roles follow three rules:

Rule	Meaning
Write implies read	A role cannot have `write` on a resource without `read`.
Organization resources are always visible	`read` cannot be removed on the Organization family (team members, merchant settings, onboarding, Connect, affiliates) — every role can at least see the account it belongs to. Only `write` is optional.
You can only grant what you hold	A member creating, editing, or assigning a role can never grant a permission they don't have themselves. An Admin cannot create a role with payout-policy access, and cannot escalate their own access through a custom role.

Creating and managing custom roles requires write access on team members, which among the built-in roles is held by Owner and Admin.

Frequently Needed Setups

Goal	How
True read-only auditor	Custom role: `read` everywhere, no `write` anywhere
Subscription support agent	Custom role: `read` + `write` on subscriptions (and optionally customers), `read` elsewhere
Finance teammate	Custom role: `read` on treasury and payments, no `write` — or Viewer if editing operations data is acceptable
Developer	Admin (API keys require it), or a custom role with `api_key` + `webhook` write