Teams in Organizations
Teams group people in the organization and own projects. Instead of granting access to each person project by project, you put the project in the team and every team member can see and operate it.
Example: create the Backend team, add three people and move the API projects into it. The three people can now see and operate those projects. Whoever leaves the team loses that access immediately.
The Teams page shows in the Console menu for business organizations.
Team roles
| Role | What they can do in the team |
|---|---|
| Maintainer | See and operate the team projects, create projects in the team, add and remove people, change roles, edit the name and description and archive the team |
| Member | See and operate the team projects (or only their own, see Who sees the team projects). Creates projects in the team only when Members can create projects in the team is on |
The organization owner always has access to every team and project.
Teams work alongside direct permissions and reusable policies: a person's access is the sum of their direct permissions, linked policies and the teams they belong to. See Granular Permissions.
Create a team
- In the menu, open Teams.
- Click Create team.
- Enter the Name and, optionally, the Description.
- Click Create team.
Whoever creates the team joins it as Maintainer. To create teams you must be the owner or have the Create teams permission. Two active teams in the organization cannot share the same name.
Add people
- In Teams, select the team.
- In Members, enter the Email of an organization member.
- Choose the role (Member or Maintainer) and click Add.
Only people who are already organization members can be added. To bring someone new, invite them to the organization first or use a team join link.
To change a role, use the selector next to the name. To remove someone from the team, click the remove icon: they immediately lose the access that came from the team. Anyone removed from the organization also leaves all its teams.
Team join link
To bring several people at once, such as a whole class, create a join link. Whoever opens the link joins the organization as a Member, with no permissions of their own, and the team as a Member.
- In Teams, select the team.
- In Join link, click Create link.
- Choose the Validity (1 to 180 days), the Maximum uses (empty for no limit) and, optionally, turn on Verified domain emails only.
- Copy the link and share it. The full link is shown only at this moment.
Whoever receives the link:
- already has an account: signs in to Zenifra and confirms joining the team;
- has no account: signs up as usual and, after confirming the email, goes back to the link and confirms joining.
The same link works for many people until it expires, reaches the maximum uses or is revoked. The list shows the active links with validity and uses; to cancel a link, click Revoke. People who already joined stay in the team.
With Verified domain emails only on, only people with an email from one of the organization's verified domains can join. Accounts created through another organization's invite cannot use the link.
To create links you must be able to manage the team members and have the organization's Invite members permission.
Everyone who joins can connect their own GitHub and create projects in the team from their own repositories.
Create a project in the team
When creating a project, database or managed service, choose the Team in the basic information section. The project belongs to the team, and the access goes to the team, not to the person who created it.
- Whoever has the Create project permission (or the permission to create databases and managed services) in the organization can choose any team or No team.
- Whoever can only create projects inside teams sees only those teams, without the No team option.
Move projects into and out of the team
In the team detail, under Team projects:
- Move to team: choose a project without a team and click Move to team. Team members get access to it.
- Remove from team: the project no longer belongs to the team, and members lose the access that came from it. Whoever removed the project from the team gets direct access to it.
To move a project you need to be able to Delete project on it and to create it at the destination: Create projects in the teams on the destination team, or the organization permission to create projects to leave it with No team.
See projects by team
On the Projects page, each team project shows the team name. In Filters, use Team to list only one team's projects or the projects with No team.
On the Members page, the Teams column shows each person's teams and their role in each one.
Limit the number of projects
In the team details, under Project limits, whoever can edit the team sets:
- Team maximum: how many projects the team can have in total;
- Per-member maximum: how many projects each person with the Member role can create in the team. Maintainers and people outside the team have no individual limit.
Leave a field empty for no limit. The limits apply when creating a project in the team and when moving a project into it; paused projects count. Lowering a limit never deletes or pauses existing projects, it only blocks new ones.
Who sees the team projects
In the team details, under Project visibility, whoever can edit the team chooses:
- Members see every team project (default): each member sees and operates every project in the team;
- Members see only their own projects: each member sees and operates only the projects they created in the team. Their teammates' projects, with logs, metrics and environment variables, stay out of their reach. In the team details, they see only themselves under Members.
Maintainers and the owner always see every team project. The change applies immediately, to existing and new projects.
Plans allowed for members
In the team details, under Plans allowed for members, whoever can edit the team chooses which plans people with the Member role can use in the team projects. Leave it at All plans for no restriction.
The restriction applies when creating a project in the team, when changing the plan of a team project and when moving into the team a project created by a member. Maintainers and the owner can use any plan. Removing a plan from the list does not change existing projects, it only blocks new ones and plan changes.
See when members signed in
Maintainers see, under Members in the team details, the Last sign-in to Zenifra column for each person in the team. View sign-ins shows when that person signed in to Zenifra in the last 30 days. Only the date and time of each sign-in are shown.
On the organization Members page, the same column appears for the owner and for whoever has the View members' sign-in times permission, with everyone in the organization.
Turn off the team's projects at a set time
To pause the team's projects every day at a set time, use a scheduled Job that calls the API. The steps are in Turn off a team's projects at a set time.
Archive a team
In the team detail, click Archive. The team must have no projects: move them to another team or to No team first. When archived, everyone leaves the team.
Team permissions
These permissions can be given directly to a member or through a policy, in Members:
| Permission | What it allows |
|---|---|
| Create teams | Create new teams in the organization |
| View teams | See every team, its members and projects |
| Edit teams | Rename teams, turn Members can create projects in the team on or off, set the Project limits, the Project visibility and the Plans allowed for members and, with Invite members, create Join links |
| Archive teams | Archive teams without projects |
| Manage team members | Add and remove people and change roles |
| Be a maintainer of the teams | Have, in every team, the same access as a maintainer, including to its projects and to its members' sign-in times |
| Create projects in the teams | Create projects in any team |
A policy with these permissions helps someone who coordinates several teams without joining each one.
Last updated on
Granular Permissions in Organizations
Configure permissions by member, resource, and action, directly or with reusable policies, to protect projects, databases, billing, Git sources, AI keys, and global API keys.
Organization API Keys
Create global organization API keys for automation, the Zenifra CLI, and custom integrations with RBAC and IP allowlists.