Organizations

An organization gives a team its own namespace: managed members, admin-controlled topics, an org API key for scripts and agents, and optional end-to-end encryption under a shared master key. Members onboard with a login code, no personal setup, and senders address people by name.

Prerequisites

• An organization on the Team plan. Contact us to set one up.
• The CLI: npm install -g @simplepush/cli
• Each teammate has the Simplepush app installed.

1. Log in

sp auth login

Opens the browser to authenticate (or a device-code flow over SSH). The session is stored locally and powers all sp org commands and org-targeted sends. On first login the org API key is printed once. Store it safely; it's what the SDKs use.

2. Invite your team

sp org members invite "Alice"
sp org members invite "Bob" --role admin

Each invite prints a one-time login code. The teammate installs the app and enters the code, and they're in. No email, no password, no account setup. Pending invites are listed with sp org invites list and revoked with sp org invites revoke <id>; both members and pending invites count against your seat limit. New organizations start on the free plan with 3 seats. Admins don't occupy a seat, and more seats can be added anytime.

3. Create topics (optional)

Org topics are admin-managed channels; members are assigned and never handle topic values:

sp org topics create field-crew
sp org topics assign field-crew "Alice"
sp org topics assign field-crew "Bob"

4. Send

# to one member, by name
sp task -m "Alice" --title "Gate 4" --text-input "What's the status?"

# to an org topic
sp task -o field-crew --title "Morning checklist" -c "All clear,Issues found"

# to everyone
sp notify -b --title "All hands" --content "Meeting at 3pm"

Each recipient gets an independent task instance, so every answer is tracked per person.

5. Collect the answers

sp task -b --format json --title "Site check" -c "Done,Blocked" \
  | sp collect --inputs

sp collect without an API token uses your org session and prints one JSON line per answer, ending with a summary. SDKs connect with the org API key via OrgClient for the same stream.

6. Turn on encryption (optional)

sp org encryption enable

Generates a versioned org master key, wrapped to each onboarded device. From then on org sends are end-to-end encrypted by default; sp org encryption sync distributes the key to newly joined devices, and key rotate rolls it. See Encryption.

Where to next

• Members & Roles: invites, roles, seats, removal
• Names & Devices: how members and devices are identified
• Broadcasting: org-wide sends and per-recipient answers
• Billing: plans and seats