VIGPT for teams

Say you want your whole team on VIGPT. With separate accounts, each person handles their own payment, and at the end of the month you're left with a handful of invoices and no clear picture of the spend.

Organizations exist for exactly this. One shared Toman wallet pays for everyone's plans, each member gets their own plan, each person's chats stay private, and the owner runs it all from one console.

One shared wallet, separate plans

At the center is an organization wallet: a balance that belongs to the org, not to one person. The owner tops it up and buys plans for members straight from it.

Each member gets their own plan — it can be Standard, Pro, or Max — and that plan's price comes out of the shared wallet. Members don't enter card details or buy a subscription; inside the org workspace, buying a plan isn't even an option for them, and they don't see the wallet. Billing is the owner's job.

If a member's monthly budget runs out, they aren't cut off. They drop to the free tier in that same org workspace and can ask the owner for an upgrade. That request lands in the owner's requests inbox to approve or decline.

Plan prices in this post are current at the time of writing — see pricing for the live numbers.

Each member's chats stay private

Being part of an org doesn't mean someone is reading over your shoulder. In the org workspace, each member has their own set of chats, visible only to them. Neither other members nor the owner can open one person's chats directly.

Every user has two separate spaces: a personal one and the org one. Personal chats and org chats stay apart, and a switcher moves you between them. Signing in is the same as always — an Iranian phone number and an SMS one-time code. There's no new kind of account to create.

The owner's console

The org owner gets one central console that does three things in one place:

• Members — invite new people, assign or cancel plans, and remove anyone who's no longer on the team.
• Requests — handle members' requests to get or upgrade a plan; approve or decline, with an optional note.
• Billing — top up the wallet and see where the money went.

Members are invited by phone number: an SMS with an invite link goes out, and the person accepts after signing in. The owner can attach a plan to the invite so it's charged from the wallet the moment the invite is accepted.

How an organization gets set up

The path is short and a few steps long:

1. Request an organization with a name for the team.
2. The VIGPT team reviews the request. Once it's approved, you become the owner.
3. Top up the wallet. Top-ups happen through web checkout, with a minimum of 1,000,000 Toman each. This step is optional — the org works on the free tier with an empty wallet — but you need a balance to buy paid plans.
4. Invite members and assign each of them a plan.

Organizations roll out gradually and may need to be requested and enabled for your team. That "request an organization" step, and the review before it goes live, are part of the process.

Who it's for

Organizations earn their keep wherever a few people will use VIGPT and one person owns the budget:

• A studio or agency that wants everyone working under a single budget.
• A company that would rather have one wallet and a clear view of spend than a scatter of invoices.
• A team that wants to give each member the plan that fits their work — some on Standard, some on Max — without anyone touching payment.

If you work solo, a personal account is all you need and none of this applies. Organizations only start to matter once there's a team and a shared budget in the picture.

In short

VIGPT for teams means one shared wallet instead of separate payments, a plan per member, chats that stay private, and a console for the owner. To get started, request an organization, wait for the review, top up the wallet, and invite your members.