Organizations and teams: one plan, shared credits, members and roles

Every project in VarynForge belongs to exactly one organization. The organization holds the plan, the research credits and the usage limits, and every member shares them. A research run started by one member spends the organization's credit, and a brief forged by another counts against the same daily cap.

Your personal organization#

Every account has a personal organization, created at sign-up. It is where your projects land unless you say otherwise. Invite someone into it and it becomes a shared workspace, or create a separate organization for a team or a client and keep your personal one to yourself. You switch between organizations from the sidebar in the web app.

Members and roles#

Invitations and roles live in the web app, under Settings, then Organization. Your agent can read them but not change them. There are three roles:

An invitation goes out by email, as a member or an admin, and expires after 48 hours. Owners cannot be removed or demoted from that screen, and making someone an owner cannot be undone there either. Any member who is not an owner can leave an organization; nobody leaves their personal one.

Project caps#

The free cap is 3 projects per organization, and create_project enforces it against the organization the project would land in. A paid plan on your personal organization does not lift the cap on a free organization you also belong to, and the reverse holds too. When the cap is reached, create_project returns a PAYMENT_REQUIRED answer with the free alternatives: reuse an existing project, or repoint one at a new market with update_niche.

Paid plans list a larger allowance: 5 projects on Forge Starter, 10 on Forge Pro, and no project cap on Forge Master. get_account_status reports the figure for the organization it describes. Today the app enforces only the free cap at creation. Free and paid has the rest of each plan.

What your agent sees#

list_organizations returns each organization you belong to with its id, name, your role (owner, admin or member), is_personal, its plan and member_count, plus any pending invitations. Your agent can see an invitation but not accept it; you accept it in the web app.

{
  "organizations": [
    { "id": "org-…", "name": "<your name>", "role": "owner", "is_personal": true, "plan": "free", "member_count": 1 },
    { "id": "…", "name": "<agency name>", "role": "admin", "is_personal": false, "plan": "pro", "member_count": 4 }
  ],
  "invitations": []
}

Three other tools carry the organization:

• get_account_status names the organization its plan and limits describe. It defaults to your personal one. Pass organizationId when working a project that belongs to another organization, because that organization's caps are the ones its project actions spend.
• list_projects and get_project carry each project's organization.
• create_project takes an organizationId. Without one, the project lands in your personal organization. With one you are not a member of, the call fails rather than placing the project somewhere you did not ask for.

Working across organizations#

When you belong to more than one organization, your agent groups and labels projects by organization in everything it tells you, so work in a shared workspace is never mistaken for personal work. When it reports quotas, it reads them for the organization that holds the project in question, not your personal one.

Where to go next#

Client reports covers the documents an agency hands each client. Connect your agent sets up the connection every member uses.