Basic Administration > Managing User Participation > Teams > About Context Teams > Defining a Context Team
  
Defining a Context Team
A context team can consist of one of the following:
A local team. The team that is associated with an application context. A local team is managed from the context. You can change roles and members using the Team page that is available from the application context after the creation steps are complete.
A shared team. This team is maintained in the organization context and then selected when application contexts are created. There can only be one shared team in a context team and the shared team cannot be modified from the application context. Modifications to a shared team affect all context teams using the shared team and are done from the organization context.
Both a local team and a shared team.
To use a shared team, the shared team must be available before creating the application context. If you select a shared team when creating a context, the shared team attributes determine if you can add local team members to the team:
If the shared team you select can be extended to allow local team members, then when you create the application context, you can choose to allow roles and members to be added locally. For more information, see About Shared Teams.
If the shared team you select cannot be extended, then you are not able to allow roles and members to be added locally.
If the context team consists of only a local team or is a team that has both local and shared teams, you can modify the local team from the Team page available from the application context by adding and removing roles, users, and groups. You can define the local team using any of the predefined roles for your organization or for your context, or you can define new custom roles that are specific to a context. Then, you can invite members to one or more roles in the local team. Users in local teams can have different roles in each context in which they are a participant. In one context, a user can be the manager, while in another context, the user can be a member. Users in shared teams have the same role in all contexts.
If the team established for a specific application context is a shared team that is not extended locally, then the entire context team can only be modified from the organization context.
As part of saving an existing application context as either a new application context or as a context template, you can recreate an established context team (both local and shared teams, if applicable) in another application context. When using a context template that has a shared team named in the template, the shared team named must be available in the organization context before the template can be used to create a new context. After creating the new context, the original context’s local team and new context’s local team are the same, but can be updated separately without affecting each other. For more information about saving an application context as a template, see Methods of Creating Additional Context Templates.
Related Topics