Skip to main content
A team is a group of people inside one organization: the designers, the sales people, the members working for one client. Teams let an organization give a tool, or a tool’s projects, to some of its people rather than to everyone.

Who makes teams

Owners and admins of an organization create its teams on account.antasphere.com, under People > Teams. There they name a team, rename it, add and remove its members, and delete it. A team holds only members of its organization, and one person can belong to several teams. Deleting a team removes the group, not the people: its members stay in the organization with the role they had.

What teams are for

  • Opening a tool to some teams only. An owner or admin can make a tool available to chosen teams of the organization instead of to every member. People outside those teams do not see the tool for that organization.
  • Sharing a tool’s projects with a team. A tool’s projects can be shared with a team, and everyone in the team gets them.
Both are settled on the account site, never inside a tool: the tools read the teams from your Antasphere account, so a change made once applies everywhere. Some tools are opened to an organization by Antasphere rather than by its owners: an event’s tool, a tool run for one client. Such a tool appears in your organization’s list only once Antasphere has opened it there, everyone in the organization may then use it, and its card on Settings > Tools says so without a setting to change. Ask Antasphere to open it or to change who has it; an owner or admin cannot from the account site.

What a member sees

Every member of an organization sees the teams they belong to on People > Teams. Inside each tool, they see the teams that share its projects with them.

When someone leaves

A person who leaves an organization, or is removed from it, leaves every team of that organization at the same time. Their teams in other organizations are not affected.

From the command line

The antasphere CLI works on the teams of the organization it acts on: antasphere teams list lists them, antasphere teams members <team> shows who is in one, and create, rename, delete, add <team> <email> and remove <team> <email> change them. Reads need a key with account:read; changes need a key with account:write held by an owner or an admin of the organization (the key antasphere login stores carries both). With several organizations, add --org <id or name> to the command, or run antasphere org use <id or name> once: it sets your default organization on your account, which every command and every tool CLI then act on.