Product organization membership and public developer-key tenancy are separate contracts. Do not infer API authority from a product role alone.
Provided capabilities
Example outcomes
- Run a multi-user conversation. Invite participants and verify everyone sees the same scoped conversation and agent output.
- Use a team channel. Ask Praxa for a channel summary and confirm it only uses content visible to the current member.
- Review organization usage. Open the organization usage view and verify the selected workspace and reporting period.
- Manage a subscription. Change a plan through the platform-specific billing surface and confirm the resulting entitlement.
Verify the surface
- Confirm the capability status and listed surface in the Capability Atlas.
- Sign in to the intended Praxa product surface and select the correct personal or organization workspace.
- Exercise the example with the smallest safe scope and inspect the visible result or approval card.
- Test one unavailable, denied, or disconnected state so the surface fails honestly.
- Use a developer tutorial only when this guide links to a supported public developer contract.