Skip to main content
Execution status: Public /v1 execution remains limited to admitted personal tenants. Organization praxa_sk_ keys, organization execution, pooled organization billing, organization key administration, and enterprise governance are unavailable.
Praxa’s existing product has organizations, memberships, roles, and team surfaces. The developer portal now has a source-ready management view over that existing authority. This documentation does not claim that the new portal view is deployed or production-canaried.

​
Source-ready portal management

After deployment, a signed-in user can use the developer portal to:
  • list the Praxa organizations they belong to and see their current role;
  • create an organization through the existing organization authority;
  • inspect an organization’s member directory;
  • add an existing Praxa username as a member or admin;
  • change eligible member/admin roles; and
  • remove an eligible member after explicit confirmation.
Owners and admins receive the mutation controls allowed by the existing organization rules. Other members receive a read-only directory. Owner roles and self-removal constraints remain protected by the existing server and database authority. An add action is not an email invitation or SCIM provisioning flow. It requires an existing Praxa username and uses the existing membership contract.

​
Current public tenant

A live preview key resolves to one server-derived personal tenant. The client cannot set or switch tenant, user, organization, billing account, or role in a request body. Keys, runs, events, cancellations, webhooks, and usage are re-authorized against that personal tenant. The signed-in personal key console supports list, create, rotate, and revoke for admitted accounts. Membership shown in the portal does not make an organization key appear and does not delegate organization execution.

​
What an admitted user can inspect today

  • customer-safe durable run projections;
  • resumable lifecycle events;
  • evidence-bounded personal usage and API-key attribution when proven; and
  • existing Praxa organization data through already-deployed product surfaces.
The new developer-portal membership UI remains in the source-ready lane until a Worker deployment and authenticated browser canary are recorded.

​
Organization execution gates

Organization execution requires more than attaching an organizationId:
  1. server-authoritative organization-unit delegation for every public route;
  2. organization billing ownership and fail-closed reservation authority;
  3. least-privilege organization key create, rotate, revoke, and audit controls;
  4. tenant-isolation and cross-tenant negative tests across keys, runs, events, approvals, webhooks, usage, and cancellation;
  5. offboarding and revocation semantics that invalidate delegated access; and
  6. authenticated production canaries before documentation moves the capability to live.
SSO, SCIM, invitation lifecycle, segregation-of-duties policy, centralized broker revocation, organization evidence export, and dedicated isolation remain enterprise roadmap capabilities. Existing custom-agent organization deployments are a separate supported surface. They do not prove organization Execution Fabric access.

​
See also

Last modified on August 14, 2026