Pi Durable Platformdocs

People and teams

Managing users, platform roles and suspension, creating and archiving teams, assigning owners, and personal workspaces' limits in Pi Durable Platform.

Users

Admin › Users lists everyone who has signed in to Pi Durable Platform, with their platform role, status, last sign-in and how many teams they're on. Search by name or email.

People appear the first time they sign in. You can't create them; you can add someone to a team by email before they sign in, which makes an invite.

Open a person to see their profile and access (platform role, email, first and last sign-in), their teams and role in each, their connected apps and their activity (the changes they made, from the audit log).

Platform admins can:

  • Change the platform role: none, platform admin or platform auditor.
  • Suspend… (in the page's ⋯ menu): the person can't sign in, their sessions end, and their API keys and connected apps stop working at the next request. Reactivate undoes it.
  • Disconnect one of their connected apps.

The last active platform admin can't be demoted or suspended.

Teams

Admin › Teams lists every team and personal workspace, with its kind, owners and status. Filter by kind to see only teams or only personal workspaces.

Create a team

Create team: a name, a slug (lower-case, used in URLs and the API; it can't change later), a description, and the first owner's email. If that person hasn't signed in yet, they get an invite and become the owner at their first sign-in.

Manage a team

Open a team: Overview, Members, Agents and Settings.

  • Agents (since v0.1.1) lists the team's agents, service-managed ones too, with template, who manages them, status and last use. Each opens the agent's page, which platform staff see read-only: Overview and Settings, and Conversations for platform admins (reading one still takes a reason). There's no Test chat, and staff can't change or hibernate the agent. See Administering the platform.

  • Assign owner makes someone an owner: it promotes a member, adds someone, or invites them.

  • Settings renames the team and changes its description.

  • Archive team… makes it read-only: no new agents or templates, no member or service account changes, and its service accounts' keys stop working. Unarchive team reverses it.

Teams aren't deleted.

Personal workspaces

A personal workspace's page has Overview, Limits, Agents and Settings.

  • The Overview shows its owner, its agents and running agents against its limits, and Audit this workspace: links to its agents' settings and status, its usage and its audit log. Platform staff never see its conversations; a platform admin can read one with a reason (see Reading conversations).
  • Limits overrides Max agents, Max running at once and Monthly budget for this workspace. Leave a field empty to use the platform's default. The defaults are in Settings.
  • Agents lists its agents, as for a team.
  • Settings can archive it, making it read-only.

Service accounts

GET /v1/admin/service-accounts lists every team's service accounts for platform admins and auditors. In the console, open a team's Service accounts page from its overview.

On this page