Teams: Group Users into Teams
Grouping users into teams aids efficiency by assigning leadership within groups of users. In the access console, each team appears as a separate queue for sessions.
Add New Team, Edit, Delete
Create a new team, modify an existing team, or remove an existing team. Deleting a team does not delete those user accounts, only the team with which they are associated.
Add or Edit Team
Create a unique name to help identify this team.
Set a code name for integration purposes. If you do not set a code name, PRA creates one automatically.
Add comments to help identify the purpose of this object.
Note any group policies which assign members to this team. Click the link to go to the Group Policies page to verify or assign policy members.
Search for users to add to this team. You can set each member's role as a Team Member, Team Lead, or Team Manager. These roles play a significant part in the Dashboard feature of the access console.
In the table below, view existing team members. You can filter the view by entering a user's name in the filter box. You can also edit a member's role or delete a member from the team.
To add a group of users to a team, go to Users & Security > Group Policies and assign that group to one or more teams in a given role.
You can click the group policy link to modify the policy as a whole. Any changes made to the group policy apply to all members of that group policy.
You can also add the individual to the team, overriding their settings as defined elsewhere.
Within a team, a user can administrate only others with roles lower than their own. Note, however, that roles apply strictly on a team-by-team basis, so a user may be able to administrate another user in one team but not be able to administer that same user in another team.
Monitoring Team Members from Dashboard
If enabled, a team lead or manager can monitor team members from the dashboard. Choose to Disable the ability to monitor, or choose Only Access Console to allow a team lead or manager to monitor a team member's access console. Monitoring affects team leads and managers for all teams on the site.
Enable Session Join and Take Over in Dashboard
If this option is checked, a team lead can join or take over a team member's sessions. Similarly, a team manager can administrate both team members and team leads. The team lead must have start session access to the Jump Item that was used to create the session, unless the option below is also checked.
Allow Team Managers/Leads to use "Transfer", "Take Over" and "Join Session" for sessions that are started from Jump Items to which they do not have "Start Session" access.
If this option is checked, a team lead can join or take over a team member's sessions, even if the team lead does not have start session access to the Jump Item that was used to create the session.
Team Chat History
Enable Replay of Team Chat History
If this option is checked, chat messages to everyone in the Team Chat area of the access console persist between access console logins. This prevents loss of chat history if the connection is lost. This does not affect chat within a session, or private chats.
Hours of Team Chat History to Replay
By default, 8 hours of history is retained. This can be changed from a minimum of 1 to a maximum of 24, using the + and - icons or entering the desired value. The time is set in one hour increments. Click Save after changing the time.
A maximum of 1000 chat messages is replayed. This limit applies regardless of the number of hours selected.