Team and accountActivity
Activity
Who changed what across the team, one sentence a line, kept for 90 days. Filter it by person, project and kind, search it, and export it as CSV.
The activity feed
Team › Activity is the team's record of what happened: who deployed, who changed a variable, who joined, which domain went live. Each line is one sentence, newest first, like:
- Ada started a preview of checkout
- storefront failed to deploy on main
- Tunde revealed DATABASE_URL
- shop.example.ng is live with HTTPS
- Checkout errors fired: 8% errors over 5 minutes
A failed build's line is shown in red. Lines that are about a deployment link to it.
Every project has its own Activity tab too, with just that project's lines.
What's in it
| Kind | Lines for |
|---|---|
| Deployments | A preview started, production deployed, promoted or rolled back, a build failed |
| Variables | Environment variables added, updated, removed, restored, revealed or pulled. Lines name the keys, never the values |
| Projects | Created, renamed, settings changed, paused or resumed, deleted, moved in from another team |
| Members | Someone joined (and who invited them), left, or had their role changed |
| Team | The team created, renamed or its settings changed; Pro upgraded, cancelled, resumed, a payment failed or the team went back to Free; an API token created or revoked |
| Integrations | A Git provider connected or disconnected |
| Domains | A domain added, changed, redirected or removed; live with HTTPS; stopped pointing at Orbits; a certificate that couldn't be issued or is about to expire |
Alerts firing and resolving are in the feed as well.
Some things aren't news and aren't written: builds starting or being cancelled, and invites being sent.
Each line names who did it: a member, a commit's author for a push, or Orbits itself for something that happened on its own, like a domain going live. Lines read as they did at the time. If a project or person is renamed later, older lines keep the old name, and a deleted project's lines stay.
Lines appear a moment after what they describe.
Filter and search
| Control | |
|---|---|
| Search activity | Matches the sentence, the person's name or the project's name, in any case |
| Person | Anyone who appears in the feed. Anyone shows all |
| Project | Any project the feed mentions |
| Type | One kind from the table above, or several |
Export CSV downloads the lines that match your filters.
Any member of the team can read the feed, viewers included.
Activity, notifications and the bell
The feed has everything. The bell shows the few lines worth a nudge (a failed deploy, a domain going live or failing, someone joining, an alert firing) and remembers what you've read. Emails, Slack and webhooks are set up in notifications and integrations.
From the CLI and the API
$ orbits activityGET /v1/teams/{team}/activity returns a page of lines with:
| Parameter | |
|---|---|
q | Search, up to 200 characters |
actor | A person's id, from the answer's people |
project | A project's id or slug |
type | deployments, variables, projects, members, team, integrations or domains; several separated by commas |
since | The oldest line to return. Defaults to 7 days ago, and can go back 90 days |
limit, cursor | Up to 100 a page; send next_cursor back as cursor for more |
{
"id": "act_…",
"type": "deployment.failed",
"category": "deployments",
"actor": { "kind": "git", "user_id": null, "name": "Ada Obi" },
"summary": "storefront failed to deploy on main",
"project": { "id": "prj_…", "slug": "storefront", "name": "storefront" },
"deployment_id": "dpl_…",
"failed": true,
"created_at": "2026-11-10T09:14:03Z"
}total counts matching lines up to 10,000. See API › Usage and activity.