Modeling of roles and teams through RASIC (Responsible, Approves, Supports, Informed, Consulted) allows a clear assignment to an activity or a workflow. A direct assignment through role identifies the expectations through that role. A indirect assignment to a role happens through a team. A team comprises a standard set of roles who work typically work together on a recurring basis to carry specific set of activities. Change Control Board (CCB) and Engineering Process Group (EPG) are some examples of a team.

A team can be modeled and associated with other process elements like activities, workflows, guidance just like roles. To create a team, navigate to Roles and select 'Team' by either clicking or tapping on three dots or plus symbol.

More information about the team can be added under description by clicking on the pencil icon <font inherit/inherit;;#ffffff;;#c0392b>(1)</font> . However, any information on which roles comprises of this team should be modeled by adding roles in the Roles widget <font inherit/inherit;;#ffffff;;#c0392b>(2)</font>. If there any trainings or similar guidance that is applicable to the the team as a whole, it should be modeled under Guidance <font inherit/inherit;;#ffffff;;#c0392b>(3)</font>.

A team can be assigned in any capacity i.e. Responsible, Approves, Supports, Informed, Consulted like Roles to an activity or a workflow as shown in following example in the screenshot.

Because a team comprises of roles, thee visualization for a role shows the team responsibilities in addition to the direct RASIC.

This can also be used for more precisely model cross-functional agile teams and other instances where responsibilities are shared across multiple roles.