Team accounts are now available in Postscale
Invite teammates, assign roles, and limit member access to specific domains without sharing an owner login.
Today, June 24, 2026, Team accounts are available to all Postscale customers.
This release adds the account model teams need once email infrastructure stops being a one-person job. You can invite teammates, choose whether they are admins or members, and grant members access to only the domains they should work on.
Why we built Team accounts
Email infrastructure usually starts with one founder or engineer adding a domain, creating an API key, and wiring the first webhook. That works while the surface area is small.
As usage grows, more people need access:
- a support lead needs inbound aliases and forwarding rules
- a product engineer needs to verify a staging domain
- an operations teammate needs delivery stats and DMARC reports
- a developer needs an API key for one application domain
The bad version of that workflow is sharing an owner login or creating organization-wide API keys for everyone. It is convenient for a week and risky after that.
Team accounts are the safer default: give people access to the exact parts of the account they need, keep billing and organization settings with admins, and make domain ownership explicit.
Roles
Postscale now supports three organization roles.
| Role | Intended use |
|---|---|
| Owner | The primary account holder. Owners can manage billing, organization settings, users, invitations, and all domains. |
| Admin | A trusted teammate who can manage users, invitations, organization settings, and all domains. |
| Member | A scoped teammate. Members only see domains assigned to them and cannot manage the organization. |
Owners and admins can invite users from Dashboard > Account > Team. An invited user signs up through the invitation link, verifies their email, and lands directly in the dashboard instead of being sent through organization onboarding or plan selection.
Domain access for members
Members get domain-level access control.
For each member, an admin can choose:
- Read - view the assigned domain, DNS setup, DKIM records, stats, DMARC data, warming status, aliases, and rules.
- Read/write - do the setup work for the assigned domain, including domain settings, DNS verification, DKIM management, aliases, inbound rules, and warming actions.
Unassigned domains are hidden from members. If a member opens a direct URL for a domain they do not have access to, Postscale treats it as not found.
This is useful when one account contains production, staging, customer-specific,
or business-unit domains. The teammate working on staging.example.com does not
need access to every production sender.
Scoped API keys
Members can create API keys only for domains where they have read/write access.
If a member creates an API key without choosing explicit domains, Postscale automatically scopes that key to the member's writable domains. Read-only domain access does not become write-capable through an API key.
Admins and owners can still create organization-wide keys when that is the right fit for server-side infrastructure.
What members cannot do
Member access is intentionally bounded.
Members cannot:
- change billing or plan settings
- delete or modify the organization
- manage other users or invitations
- promote themselves or change their own role
- access unassigned domains
- create API keys for read-only or unassigned domains
That keeps organization control with the admin group while still letting teammates do real operational work.
Where to start
Open Dashboard > Account > Team.
- Invite a teammate as an admin or member.
- For members, open Access and assign the relevant domains.
- Choose read or read/write access per domain.
- Ask the teammate to accept the invitation and verify their email.
For setup patterns, role examples, API-key behavior, and offboarding notes, read the Team accounts and domain access guide.
Team accounts are available now for every Postscale customer.