Teams and members
Everything in SpacePost belongs to a team: domains, API keys, emails, webhooks, audiences, contacts, broadcasts, suppressions, usage and billing. API keys are scoped to a single team, so a key can only ever see that team’s data.
Why it matters
Section titled “Why it matters”- Quotas and plan are per team.
- Reputation is isolated per team. Each team has its own sending tenant at Amazon SES, so a problem in one team cannot pause another team’s sending. Automatic pausing is also per team.
- Domains are unique across SpacePost: a domain can belong to one team at a time.
- Use separate teams for separate products or clients (for example
acme-prodandacme-staging) when you want separate keys, quotas and suppression lists.
Members
Section titled “Members”Invite colleagues from Settings, Members in the dashboard. Members sign in with their own accounts and see the team’s data.
Member email addresses are special in one place: the shared test sender onboarding@test.spacepost.dev can deliver only to the email addresses of your team’s members and to test addresses.
Switching teams
Section titled “Switching teams”If you belong to several teams, use the team switcher in the dashboard. The API needs no switching: the key you use determines the team.
Best practices
Section titled “Best practices”- Give each service its own API key with the narrowest permission.
- Remove members who leave, and rotate any keys they had access to.