Updated September 27, 2026
Teams
Share layouts, watchlists, notes, and a private chat channel with a group, while personal content stays personal.
What a team is
A team is a group of Gloom Cloud accounts that share layouts, watchlists, paper portfolios, notes, custom views, and private chat channels.
Team content sits next to yours, marked by the team's accent color, or a short prefix such as MD· on terminals without color. When you create something shareable, a picker asks whether it belongs to you or to a team.
Creating a team needs a Pro plan, and you can create one only while you are in fewer than 5 teams. Joining is free. A new team holds up to 25 members; a Team plan sets its own seat count.
A team can also be on the Team plan, billed to the team rather than to each person. Everyone on it gets Pro for as long as they are a member, and anyone with their own subscription keeps it. Contact us to set one up.
Create a team
In the terminal, run TEAM. With no teams yet it opens a short wizard: a name, an accent color, and an invite step. On the web, open the Teams section of your account.
Every team gets a #general channel in chat and appears in the chat sidebar under its accent color. Any member can add channels from the sidebar (+ next to the team) or from the team pane; owners and admins can remove them. #general stays.
Invite people
Owners and admins can invite in three ways:
- Invite link. The most common path.
TEAM invite linkin the terminal or New link on the web. Links last seven days by default and can be capped to a number of uses. Anyone with the link joins as a member. Owners can allow every member to create links from the team settings; it is off by default. - By username.
TEAM invite @name. The person sees the invite in their terminal and can accept or decline fromTEAM. - By email. For people not on Gloom yet. They get an email, create an account with that address, and land on the team.
Roles
Three roles, no per-object permissions:
| Role | Can |
|---|---|
| Owner | Everything, including transfer ownership and delete the team. |
| Admin | Invite, remove members, change settings, manage anyone's shared content. |
| Member | Publish layouts, edit shared notes, watchlists, and portfolios, create their own shared content. |
Anyone can delete what they created. Owners and admins can also delete what others created.
Shared layouts
Publishing from a tab creates or updates a team layout; opening one from the gallery creates a linked tab on your machine.
- Content, not arrangement. Pane instances, bindings, and pane settings are shared. Where the panes sit on your screen stays yours.
- Publish and pull. A linked tab shows
*when you have local changes and an arrow when the team has a newer revision. If you have no local changes, updates pull silently on open. If you do, the terminal asks. - Conflicts. Publishing over a newer revision fails safely. You can save your version as a personal copy and pull, overwrite with yours, or discard yours.
- Missing plugins. A pane from a plugin you do not have renders as a placeholder with an install action. Your copy still carries it, so publishing from your machine never drops a teammate's pane.
Personal financial data never travels with a team layout. Broker-linked portfolios, positions, credentials, and AI threads stay private; the same scrubber that protects public shares applies to team publishing.
Shared watchlists and paper portfolios
Team watchlists and paper portfolios update live: when someone adds a symbol, everyone sees it. Broker-linked portfolios are always personal and cannot be shared with a team.
Notes
Notes are stored in Gloom Cloud so your devices agree and a team can share them. The notes tab shows Mine first, then one section per team. Saving a note that a teammate edited since you opened it keeps your buffer and offers to reload or overwrite.
Local .md notes written while signed out are imported the first time you sign in and stay on disk. Export Notes in the terminal or gloomberb notes export [dir] writes everything back to files.
Custom views
A VIEW pane is a table (columns, filter, sort) that an agent builds over remote control. Published to a team, it appears as a pane template for every member.
Leaving and deleting
Leaving a team, or being removed, drops the channel, notes, and collections from your terminal. Linked tabs become personal copies. Your personal data is untouched.
Deleting a team removes everything it owned for every member. Only the owner can, and the terminal or web page asks for the team's name to confirm.
Focus
FOCUS collapses the tabs and mutes the channels of everything except what you pick: personal, one team, or all. It also sets the default in owner pickers. It never changes what a command means.