Heads up: putting in Team and SKU structures into the user account management

General Questions
1

Hi everyone,

This week, we’re making some platform changes to (a) define SKUs, (b) group paying user accounts into Teams and associate each team with a SKU, LLM API keys, etc, (c) enable/throttle some features based on the SKU.

So far, we worked around all of this by each user either working on a Free basis with our platform LLM API key, or by adding a separate LLM API key associated with their user account. When a user added their own LLM API key, our system would transparently creating a separate Team record 1:1 for that user to record the LLM key.

Going forward, here is what we’re setting up — I wanted to make sure you aren’t surprised …

If you are a free user working alone, you will not see any meaningful changes.

If you use Thunk.AI as a user within a company that has a contract with us,

  1. There will be a single team owned by one of you. The owner will be able to add/delete/manage LLM API keys for this team from their Account → Organization page.

  2. The team owner can add the other users to the same team as long as they share the same email domain. By doing so, they will share the same LLM API keys.

  3. The team will be assigned to a specific SKU. Only Thunk.AI support can change the SKU assignment.

  4. In your account settings page, you will see an Organization tab that tells you which team you are in (each of the users in the team will see the same team).

  5. In your account settings page, you will also see a Subscription tab that tells you the SKU associated with your team, and lists its capabilities/constraints.

We will gradually start enforcing these constraints in the product so please let us know if we inadvertently interfere with the operation of your thunks.

We intend none of this to be disruptive, but wanted to give you all a heads up to avoid any surprises. If you have any concerns or see any issues, please let us know.