Account
Teams
Create or join a Jennefer team in the portal, invite members, set roles and per-member permissions, share API keys safely and manage team sandboxes.
On this page
A team lets several people share one plan, pooled Cloud hours and connected apps, with an owner and admins controlling what each member may use. Teams are managed in the portal under Team. For agent teams, see Agent teams.
Create or join a team#
- 1
Get a team plan
Creating a team needs an active Team or Cloud Team subscription. See Plans and account.
- 2
Create the team
In the portal, open Team and give it a name of 2 to 60 characters. You become the Owner.
- 3
Or join one
Accept an invitation. Your verified email address must match the address it was sent to. You can be in one team at a time.
Invite members#
- Owners and admins invite people by email, as a member or an admin. Only the owner can invite admins.
- Each invitation has a code in the format
JNT-XXXX-XXXX-XXXX. It works once, for 7 days, and is shown only once. - A team can have up to 50 open invitations.
Roles#
| Role | Can do |
|---|---|
| Owner | Everything: change roles, invite admins, delete the team. The owner holds the subscription, cannot leave the team and is never restricted. |
| Admin | Invite and remove members, set member permissions, manage shared keys, see usage, and pause or delete members' sandboxes. |
| Member | Use the team within the permissions set for them, or leave. |
Seats and what members get#
- Seats follow the number of members, with a minimum of two, and are prorated.
- Every member gets the Team plan: Pro limits in every app, up to 25 agents in a team and 8 parallel agents.
- With Cloud Team, Cloud hours are pooled (80 per seat), and each person can run 3 sandboxes at once.
- Connected apps are pooled: 10 per seat.
- Each member's library backup gets 100 GB. The owner's storage add-ons are not shared.
- If the team subscription ends, members go back to their own plans. Nothing is deleted.
Member permissions#
Admins can restrict each member. Permissions can only lower what a member gets, never raise it above the plan.
| Permission | Effect |
|---|---|
| Cloud on or off | Turns cloud sandboxes off for that member. |
| Max sandboxes | How many sandboxes they can keep, 1 to 50. |
| Monthly Cloud hours | A cap on the hours they can use. |
| Allowed machine sizes | Which sandbox sizes they can pick. |
| App access | Which apps they can use: IDE, CLI, Studio, Workshop and Cloud. |
| IDE panels | Turns the IDE's terminal or chat off. A turned-off panel says This panel was turned off by your team admin. |
| Shared keys | Whether they can use the team's shared keys. |
Shared API keys#
Admins can store up to 20 provider API keys for the team. Keys are stored encrypted on Jennefer's servers. Members who are allowed to use a key can see its value.
Team sandboxes#
Admins can see members' sandboxes and usage, and pause or delete sandboxes. See Cloud sandboxes.
Leaving or deleting a team#
- A member can leave at any time and returns to their own plan.
- Admins can remove members, but not other admins.
- Only the owner can delete the team. Members keep their own accounts and work.
FAQ#
How many people does a team need?
At least two seats.
Do invited members need to pay?
No. They get the Team plan while they are members.
I cannot use Cloud.
An admin may have turned Cloud off for you. Ask them to check your permissions.