Organizations, billing and access
PHPSandbox keeps project access, billing and subscription availability in the current organization. Check the organization switcher before changing settings or diagnosing a missing feature.
Personal organization
A personal organization is for solo work and has personal billing. To invite teammates, use a team organization instead.
Team organization
A team organization has shared projects, member roles and seat-based access. Owners and administrators manage organization settings; members have the permissions granted to their role.
Switching organizations
Use the organization switcher in the workspace header to choose another organization. This changes the projects, permissions, subscription and credits available to you.
Inviting members
To invite a colleague or teammate:
- Switch to the team organization that should own the work.
- Open organization settings and choose Members.
- Enter the teammate’s email address and choose a role.
- Send the invitation.
You can resend or revoke pending invitations from Members. Invitations require an authorized role and an available seat. An invitation failure does not mean the address is invalid; read the error beside the form.
Seats
Seat usage includes active members and pending invitations. Review seats in the organization’s general settings before inviting more people. Increase capacity or revoke an unused invitation if there are no available seats.
Billing context
Review the current organization’s plan, credits and billing period in organization settings. A personal plan belongs to a personal organization; a team plan belongs to a team organization. Organization management permissions and subscription availability are separate checks.
The documentation does not establish your current balance or plan. The agent must inspect current account information before saying that you have credits or access to a feature.
Tool approval policies
The Tool approvals settings page is available to eligible subscribed organizations. Policies can apply to a conversation, project, user or organization. Organization-wide changes require the appropriate management permission.
Read each requested action before approving it. Documentation explains a workflow; it does not grant permission to execute it.
Feature availability
Publishing, Advanced model selection, tasks and isolated workspaces follow the current organization’s subscription entitlement. There is no separate per-user publishing or task opt-in. If an upgrade is required and you cannot manage billing, contact an organization administrator.