Skip to main content
Changing your default team affects what you can create and which team your issues and processes belong to.

​
Team based permissions

Every issue or process is associated with a team at the time of creation. The “owned by my team” permission condition gives people access to data that originate from their own team. It is this default team that is saved along with the issue and process that lets the system know who should have access to such data. Because your permissions to add may differ between different teams, changing the default team would affect what you can create. If on Team A you can create an issue but on Team B you cannot, selecting Team B as the default team will result in you not being able to create an issue. If on Team A you can create an issue of Standard Issue Category 1, and on Team B of Category 2, which default team you select will affect the kind of issues you can create. In general, you should check which default team you have before creating issues and processes. But it serves as a hint that you may have the incorrect setting if you cannot create certain data when you believe you should be able to. Default team does not affect read, edit or delete permissions. It only affects add permissions. To know how to switch team? Please click here.