OrbitsDocs
esc
    Open Orbits
    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

    KindLines for
    DeploymentsA preview started, production deployed, promoted or rolled back, a build failed
    VariablesEnvironment variables added, updated, removed, restored, revealed or pulled. Lines name the keys, never the values
    ProjectsCreated, renamed, settings changed, paused or resumed, deleted, moved in from another team
    MembersSomeone joined (and who invited them), left, or had their role changed
    TeamThe 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
    IntegrationsA Git provider connected or disconnected
    DomainsA 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.

    Control
    Search activityMatches the sentence, the person's name or the project's name, in any case
    PersonAnyone who appears in the feed. Anyone shows all
    ProjectAny project the feed mentions
    TypeOne 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

    Terminal
    $ orbits activity

    GET /v1/teams/{team}/activity returns a page of lines with:

    Parameter
    qSearch, up to 200 characters
    actorA person's id, from the answer's people
    projectA project's id or slug
    typedeployments, variables, projects, members, team, integrations or domains; several separated by commas
    sinceThe oldest line to return. Defaults to 7 days ago, and can go back 90 days
    limit, cursorUp to 100 a page; send next_cursor back as cursor for more
    One line
    {
      "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.

    Was this page helpful?

    Updated