Organizations
An organization gives a team its own namespace. It has managed members, admin-controlled topics, an organization API key for scripts and agents, and optional end-to-end encryption under a shared master key. Members join with a login code and need no personal setup. 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 loginThis opens the browser to authenticate. Over SSH it uses a device-code flow instead. The session is stored locally and is used by all sp org commands and organization-targeted sends. On first login the organization API key is printed once. Store it safely. The SDKs use it.
2. Invite your team
sp org members invite "Alice"
sp org members invite "Bob" --role adminEach invite prints a one-time login code. The teammate installs the app and enters the code. That is all. No email, no password, no account setup. sp org invites list shows pending invites and sp org invites revoke <id> revokes one. Both members and pending invites count against your seat limit. New organizations start on the free plan with 3 seats. Admins do not occupy a seat. More seats can be added anytime.
3. Create topics (optional)
Organization topics are admin-managed channels. Admins assign members to them. Members 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 --inputsWithout an API token, sp collect uses your organization session. It prints one JSON line per answer and ends with a summary line. The SDKs read the same stream through OrgClient, which connects with the organization API key.
6. Turn on encryption (optional)
sp org encryption enableThis generates a versioned organization master key and wraps it for each onboarded device. From then on, organization sends are end-to-end encrypted by default. sp org encryption sync distributes the key to newly joined devices. key rotate rotates it. See Encryption.
Where to next
- Members & Roles: invites, roles, seats, removal
- Names & Devices: how members and devices are identified
- Broadcasting: organization-wide sends and per-recipient answers
- Billing: plans and seats