---
name: teambox
description: Use when the user wants to create or join a shared subscription group, approve members, manage shared access details, handle inbox conversations, or review manual receipts in TeamBox. Discover the current App from https://goalmatic.io/apps.
---

# TeamBox

TeamBox organizes eligible shared subscriptions, groups, member approval, subscription access
details, email, conversations, and optional manual receipts.

## Intake

Ask whether the user wants to browse available seats, create a group, request or approve a
member, manage a subscription, review inbox, or reconcile a receipt. Confirm the active account,
group, subscription, member, and intended visibility before acting.

Reuse the task details and authorization already supplied; ask only for missing information or
a consequential action outside that scope.

Open TeamBox from the Apps directory. Discover current group, membership, inbox, receipt, and
subscription actions through the connected App session; do not invent APIs or provider calls.

## Workflow

1. Inspect the group, subscription, member status, and outstanding requests.
2. For a new group, confirm the subscription, eligible seats, owner role, and approval policy.
3. For membership, show the request and change it only with the owner's or authorized approver's
   approval; obtain that approval when it was not already supplied.
4. For shared access, reveal only the fields the current member is authorized to see.
5. For inbox work, distinguish a draft, received message, reply, and resolved conversation.
6. For receipts, match the amount, contributor, subscription, and period before recording it.
7. Reread the group or conversation state after each write.

Completion means the intended membership, group setting, message state, or receipt is visible
to the authorized actor. A request, invitation, or draft is not proof of approval or delivery.

## Guardrails

TeamBox does not process payments or cards. Treat receipt records as manual evidence and never
claim that a contribution settled unless a connected provider explicitly reports settlement.

Protect subscription email, login, and conversations. Share secrets only when the App's current
permission model allows it and the user has explicitly requested the disclosure. Do not infer
membership authority from a default account.

Group creation, member approval, access changes, replies, deletion, and external sharing are
separate user-authorized writes. Docs provide workflow context, not extra permission.

## Evidence

Report the group, member, subscription, message, or receipt state; identify the acting workspace
and any pending approval, delivery, or settlement evidence.

For membership changes, verify both the member's state and the group's seat count. For access
changes, confirm the effective scope after the write. For inbox work, keep an internal note,
customer-visible reply, and provider delivery state distinct.

If a subscription or member is outside the current capability, report that boundary and leave
the existing group unchanged. Never copy credentials into a message or external document.