<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Teams, Groups &amp; Organizations: Published Ordered Knowledge Base: : General | Helprace Support</title>
    <description>Published Ordered Knowledge Base: Teams, Groups &amp; Organizations</description>
    <generator>Helprace RSS</generator>
    <link>https://support.helprace.com/s1-general/knowledgebase/c26-teams-groups-organizations?format=rss</link>
    <item>
      <title>About Teams, Groups &amp; Organizations</title>
      <description><![CDATA[<p>Need a compelling reason to group people in your help desk into categories?</p>
<p>Take control of your ticket workflows or limit access to tickets and areas in your user portal. Improve productivity of your support agents, allowing them to offer better customer service.</p>
<p>  What are Teams?</p>
<p>Teams are a collection of your staff members, also known as Agents in Helprace. How you structure your Teams depends on how you want your tickets to behave. Simply put, you may want to create Teams to:</p>
<ul>
<li>assign a ticket to a group of agents, rather than one agent;</li>
<li>group issue type with support[_cuted_]</li></ul>]]></description>
      <pubDate>Fri, 08 Nov 2019 10:43:53 +0000</pubDate>
      <link>https://support.helprace.com/i736-about-teams-groups-organizations</link>
      <guid>https://support.helprace.com/i736-about-teams-groups-organizations</guid>
      <author>Vic</author>
      <dc:creator>Vic</dc:creator>
      <content:encoded><![CDATA[<p>Need a compelling reason to group people in your help desk into categories?</p>
<p>Take control of your ticket workflows or limit access to tickets and areas in your user portal. Improve productivity of your support agents, allowing them to offer better customer service.</p>
<h2><i class="fa fa-user-friends fa_20" style="color: #00abc9;">  </i>What are Teams?</h2>
<p>Teams are a collection of your staff members, also known as Agents in Helprace. How you structure your Teams depends on how you want your tickets to behave. Simply put, you may want to create Teams to:</p>
<ul>
<li>assign a ticket to a group of agents, rather than one agent;</li>
<li>group issue type with support type or staff expertise;</li>
<li>answer for various departments in your help desk;</li>
<li>set different visibility permissions for various tickets;</li>
<li>restrict ticket visibility based on rules &amp; notifications (ie: the mailbox a ticket was sent to).</li>
<li>use them in ticket rules &amp; notifications.</li>
</ul>
<p><a href="https://support.helprace.com/i721-teams">Learn more about Teams</a></p>
<h2><i class="fa fa-users fa_20" style="color: #00abc9;">  </i>What are User Groups?</h2>
<p>User Groups are a collection of your end-users, customers, or anyone with the User role in Helprace. You can have one user belong to various Groups, which makes it particularly easy to segment users according to your needs. Use Groups to:</p>
<ul>
<li>segment customers by value;</li>
<li>segment customers by support type needed;</li>
<li>restrict access to areas of your user portal;</li>
<li>use them in ticket rules &amp; notifications.</li>
</ul>
<p><a href="https://support.helprace.com/i722-user-groups">Learn more about User Groups</a></p>
<h2><i class="fa fa-building fa_20" style="color: #00abc9;">  </i>What are Organizations?</h2>
<p>Organizations are a collection of your end-users by company. Unlike User Groups, Organizations make it easy for users to participate in tickets between each other. It also gives staff a bird's eye view of what's going on. Use Organizations to:</p>
<ul>
<li>allow staff to see all member participation within an organization (tickets or topics started).</li>
<li>allow organization users to share or view shared tickets;</li>
<li>automatically add users to an organization with a domain;</li>
<li>restrict access to areas of your user portal;</li>
<li>use them in ticket rules &amp; notifications.</li>
</ul>
<p><a href="https://support.helprace.com/i723-organizations">Learn more about Organizations</a></p>
<blockquote>
<p>Teams, User Groups and Organizations are available in the Complete plan.</p></blockquote>]]></content:encoded>
    </item>
    <item>
      <title>Teams</title>
      <description><![CDATA[<p>About Teams</p>
<p>Teams are a collection of your support agents. By grouping your agents into Teams you are able to control the visibility and behavior of tickets. Use teams to:</p>
<ul>
<li>assign a ticket to a group of agents, rather than one agent;</li>
<li>group issue type with support type or staff expertise;</li>
<li>answer for various departments in your help desk;</li>
<li>set different visibility permissions for various tickets;</li>
<li>restrict ticket visibility based on rules &amp; notifications;</li>
<li>use them in rules &amp; notifications.</li>
</ul>
<p>Teams cannot contain end-users. End-users can only be grouped in User Groups and Organizations.</p>
<p>When you separate your support agents[_cuted_]</p>]]></description>
      <pubDate>Tue, 30 Apr 2019 09:08:09 +0000</pubDate>
      <link>https://support.helprace.com/i721-teams</link>
      <guid>https://support.helprace.com/i721-teams</guid>
      <author>Edward</author>
      <dc:creator>Edward</dc:creator>
      <content:encoded><![CDATA[<div class="mce-toc">
<div style="display: none;"> </div>
<ul>
<li><a href="#mcetoc_1cr59sn661c" rel="nofollow">About Teams</a></li>
<li><a href="#mcetoc_1cr59sn661d" rel="nofollow">What you can do with Teams</a></li>
<li><a href="#mcetoc_1cr59sn661e" rel="nofollow">Managing Teams</a>
<ul>
<li><a href="#mcetoc_1cr59sn661f" rel="nofollow">Creating Teams</a></li>
<li><a href="#mcetoc_1cr59sn661g" rel="nofollow">Adding &amp; removing agents</a>
<ul>
<li><a href="#mcetoc_1cr59sn661h" rel="nofollow">Teams page</a></li>
<li><a href="#mcetoc_1cr59sn661i" rel="nofollow">User profile</a></li>
</ul>
</li>
<li><a href="#mcetoc_1cr59sn661j" rel="nofollow">Default Teams</a></li>
<li><a href="#mcetoc_1cr59sn661k" rel="nofollow">Editing &amp; deleting Teams</a>
<ul>
<li><a href="#mcetoc_1cr59sn661l" rel="nofollow">Teams page</a></li>
<li><a href="#mcetoc_1cr59sn661m" rel="nofollow">Team view</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#mcetoc_1cr59sn661n" rel="nofollow">Using Teams with Tickets</a>
<ul>
<li><a href="#mcetoc_1cr59sn661q" rel="nofollow">Assign tickets to a Team</a></li>
<li><a href="#mcetoc_1cr59sn661o" rel="nofollow">Ticket access and visibility</a></li>
<li><a href="#mcetoc_1cr59sn661r" rel="nofollow">Searching tickets by Team</a></li>
<li><a href="#mcetoc_1cr59sn661p" rel="nofollow">Managing Team Filters</a></li>
<li><a href="#mcetoc_1cr59sn661r" rel="nofollow">Using Teams in Macros</a></li>
<li><a href="#mcetoc_1cr59sn661s" rel="nofollow">Using Teams in Rules &amp; Notifications</a>
<ul>
<li><a href="#mcetoc_1cr59sn661t" rel="nofollow">Specifying Teams in Conditions &amp; Actions</a></li>
<li><a href="#mcetoc_1cr59sn661u" rel="nofollow">Auto-assign tickets within a Team</a></li>
<li><a href="#mcetoc_1cr59sn661v" rel="nofollow">Sending notifications to Teams</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#mcetoc_1cr59sn6620" rel="nofollow">Teams in User Portal</a>
<ul>
<li><a href="#mcetoc_1cr59sn6621" rel="nofollow">Content Restrictions</a></li>
</ul>
</li>
</ul>
</div>
<h2 id="mcetoc_1cr59sn661c">About Teams</h2>
<p>Teams are a collection of your support agents. By grouping your agents into Teams you are able to control the visibility and behavior of tickets. Use teams to:</p>
<ul>
<li>assign a ticket to a group of agents, rather than one agent;</li>
<li>group issue type with support type or staff expertise;</li>
<li>answer for various departments in your help desk;</li>
<li>set different visibility permissions for various tickets;</li>
<li>restrict ticket visibility based on rules &amp; notifications;</li>
<li>use them in rules &amp; notifications.</li>
</ul>
<p>Teams cannot contain end-users. End-users can only be grouped in <a href="https://support.helprace.com/i722-user-groups">User Groups</a> and <a href="https://support.helprace.com/i723-organizations">Organizations</a>.</p>
<p>When you separate your support agents into Teams, you must take into account the various <a href="https://support.helprace.com/i84-user-roles-and-staff-privileges">user roles</a> in Helprace.</p>
<h2 id="mcetoc_1cr59sn661d">What you can do with Teams</h2>
<p>Here are some of the things you are able to do with Teams in Helprace:</p>
<p><b>Assign a team to mailbox</b></p>
<p>You want to ensure that emails to billing@acme.com are addressed by the Billing team.</p>
<p><b>Separate responsibility for requests</b></p>
<p>You want to assign billing and refund tickets to the Billing team. Assign tickets that contain common questions to the Level 1 Team.</p>
<p><b>Restrict access to confidential requests</b></p>
<p>You want to ensure that no one except certain agents (with the exception of Admins, Owners) see tickets meant for the Billing team.</p>
<p><b>Escalate requests according to complexity</b></p>
<p>Tier 1 team, Tier 2 team, Tier 3 team. Tier 1 and 2 agents can only see tickets assigned to each other, while Tier 3 agents can see everyone's tickets. Some agents may be part of both teams.</p>
<p><b>Divide up teams according to expertise</b></p>
<p>Support Team and Product Team can share a a support agent with expertise in both areas. However, other agents do not see contents of teams they do not belong to.</p>
<p><b>Assign requests to a team based on tags</b></p>
<p>Tickets with the word refund in the subject or body get tagged "refund" and are assigned to the Billing Team.</p>
<p><b>Divide support by time zone, language, etc</b></p>
<p>EST-E Team is for supporting English-speaking customers on the east coast and the PST-S Team is for supporting Spanish-speaking customers on the west coast.</p>
<h2 id="mcetoc_1cr59sn661e">Managing Teams</h2>
<p>Only Admins and Owners can manage (create, modify, delete, add agents to) Teams.</p>
<h3 id="mcetoc_1cr59sn661f">Creating Teams</h3>
<ul>
<li>Go to  <i class="fa fa-address-book"> </i>People and select Teams.</li>
<li>Create a new Team by clicking on the <b>+</b> button and adding a title and optional description.</li>
</ul>
<h3 id="mcetoc_1cr59sn661g">Adding &amp; removing agents</h3>
<p>As soon as you create a Team, you can add existing agents to it. You can add users automatically using <a href="#default" rel="nofollow">Default Teams</a>. Manage agents via:</p>
<h4 id="mcetoc_1cr59sn661h">Teams page</h4>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/721/media/add-agent.png" alt="" data-file="___chdfid_2760___"></p>
<ul>
<li>Click on a desired team in Teams.</li>
<li>Click <b>Add Agent</b>. Start typing in their name or pick from the list.</li>
<li>Remove the agent by clicking X to the right of their name.</li>
</ul>
<blockquote>If a particular person is not available in the list or if you can't find them, they likely have a role of User. Change their role to Agent before adding them to a Team.</blockquote>
<h4 id="mcetoc_1cr59sn661i">User profile</h4>
<div>
<p>When Teams are added, they're displayed in the sidebar. Click to change them.</p>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/721/media/change-team.png" alt="" data-file="___chdfid_2761___"></p>
</div>
<h3 id="mcetoc_1cr59sn661j"><a id="default"></a>Default Teams</h3>
<p>Adding new agents in Helprace will add them to a default Team automatically. Note that this will only happen after a default Team is set.</p>
<p>This is regardless if agents are added via the API, imported in bulk, or added individually. To make a Team default:</p>
<ul>
<li>Go to  <i class="fa fa-address-book"> </i>People and select Teams.</li>
<li>You'll see a list of your Teams. Click the ⋮ button to the right of the desired Team and select Make Default.</li>
</ul>
<p>Remove default Team if you want new agents created without being assigned to a Team. To remove a default Team:</p>
<ul>
<li>Click the ⋮ button to the right of the desired Team and select Remove Default.</li>
</ul>
<h3 id="mcetoc_1cr59sn661k">Editing &amp; deleting Teams</h3>
<h4 id="mcetoc_1cr59sn661l">Teams page</h4>
<ul>
<li>Go to  <i class="fa fa-address-book"> </i>People and select Teams.</li>
<li>You'll see a list of your Teams. Click the ⋮ button to the right of the desired Team and select Edit or Delete.</li>
</ul>
<h4 id="mcetoc_1cr59sn661m">Team view</h4>
<p>Edit or delete with the pencil and trashbin icons.</p>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/721/media/edit-team.png" alt="" data-file="___chdfid_2758___"></p>
<blockquote>Deleting Teams carries some implications. If you set up any Rules &amp; Notifications, they will no longer function as intended. The tickets that were assigned to a Team will revert to Unassigned, but you'll be able to see ticket history in All Events.</blockquote>
<h2 id="mcetoc_1cr59sn661n">Using Teams with Tickets</h2>
<h3 id="mcetoc_1cr59sn661q">Assign tickets to a Team</h3>
<p>Any staff member can assign a ticket to anyone, including to Teams. Tickets can be <a href="#rules" rel="nofollow">automatically assigned</a> to Teams as well.</p>
<p>Tickets can be a assigned in various of ways from the assignment drop down:</p>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/721/media/assign.png" alt="" data-file="___chdfid_2759___"></p>
<ul>
<li><b>Unassigned</b> removes assignment
<ul>
<li>removes agent but leaves Team if ticket is assigned to agent</li>
</ul>
</li>
<li><b>Unassign Team</b> removes Team assignment
<ul>
<li>visible when ticket is assigned to Team or to agent within it</li>
<li>makes Unassigned if assigned to Team</li>
<li>removes Team but leaves agent if ticket is assigned to agent</li>
</ul>
</li>
<li><b>Assign to Me</b> assigns ticket to yourself</li>
<li><b>Team</b> assigns ticket to:
<ul>
<li>a Team as a whole</li>
<li>an agent within that Team</li>
</ul>
</li>
<li><b>No Team</b> lets you select an agent without a Team</li>
</ul>
<p>Here's an example:</p>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/721/media/teams-guide-small.png" alt="" data-file="___chdfid_2763___"></p>
<h3 id="mcetoc_1cr59sn661o">Ticket access and visibility</h3>
<p id="mcetoc_1cr7k55nt0">Owners and Admins always have access to all tickets.</p>
<p>Agents don't have access to tickets assigned to Teams other than their own, unless assigned to them personally.</p>
<blockquote>
<p>If an agent assigns a ticket to a Team they do not belong to, they will lose access to the ticket upon submission.</p>
</blockquote>
<h3 id="mcetoc_1cr59sn661r">Searching tickets by Team</h3>
<p>To search for tickets assigned to a certain Team</p>
<pre>team:Billing</pre>
<p>To search for Pending tickets not assigned to a certain Team</p>
<pre>status:pending -team:Billing</pre>
<p><a href="https://support.helprace.com/i93-helprace-search-guide">Learn more about searching</a></p>
<h3 id="mcetoc_1cr59sn661p">Managing Team Filters</h3>
<p>There are three types of ticket filters:</p>
<ul>
<li><b>Shared</b> (visible globally for everyone).
<br>
Owners and Admins can manage them. Agents can only view them.</li>
<li><b>Team</b> (visible to members of certain Team).
<br>
Owners and Admins can manage them. Agents within the Team can only view them.</li>
<li><b>My Filters</b> (visible to the individual only).</li>
</ul>
<p>Therefore, you can set up <a href="#filters" rel="nofollow">filters</a> (or views) that will be available to a specific Team. For example, you can have tickets that are assigned to that team to show up in the filter. You can add additional filters that list the tickets assigned to each agent within that Team.</p>
<ul>
<li>Go to the <b>Tickets</b> page and click on the ⋮ button in the left pane and select Add Filter.</li>
<li>
<p>To show unresolved tickets assigned to a Team named Billing, type in the search query</p>
<pre>team:"Billing" status:(new OR open)</pre></li>
<li>
<p>Choose what Team you'd like it available to.</p>
</li>
</ul>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/721/media/filter-team.png" alt="" data-file="___chdfid_2762___"></p>
<h3 id="mcetoc_1cr59sn661r">Using Teams in Macros</h3>
<p>You can assign a ticket to a specific Team using saved commands (macros). <a href="https://support.helprace.com/i138-macros">Learn more about Macros</a></p>
<h3 id="mcetoc_1cr59sn661s">Using Teams in Rules &amp; Notifications</h3>
<h4 id="mcetoc_1cr59sn661t">Specifying Teams in Conditions &amp; Actions</h4>
<p><b>You can assign your mailboxes to Teams.</b></p>
<p>Example: You want to ensure that emails to billing@acme.com are addressed by the Billing team. Simply set the Condition</p>
<pre>Ticket: Received At &gt; Is one of &gt; billing@acme.com</pre>
<p>And Action</p>
<pre>Ticket: Team &gt; Billing</pre>
<p><b>You can make a ticket's Team a criteria for additional action.</b></p>
<p>Example: You want to send an email to the Owner whenever a ticket is assigned to the Billing Team. Simply set Conditions</p>
<pre>Ticket: Assignee &gt; Is &gt; Changed<br>Ticket: Team &gt; Is &gt; Billing</pre>
<p>and Action</p>
<pre>Notification: Email user: &gt; Mr. Owner</pre>
<h4 id="mcetoc_1cr59sn661u"><a id="rules"></a>Auto-assign tickets within a Team</h4>
<p><b>You can escalate tickets to a Team.</b></p>
<p>Example: You want tickets tagged "urgent" assigned to an agent automatically in Experienced Team. Simply set the Condition</p>
<pre>Ticket: Tags &gt; Contains at least one of the following &gt; urgent</pre>
<p>and Actions</p>
<pre>Ticket: Team &gt; Experienced Team<br>Ticket: Assignee &gt; (Auto: Least Busy)</pre>
<p><b>You can check if a ticket is unassigned to a Team.</b></p>
<p>Example: You want tickets unassigned to a Team to be assigned to a specific agent. Simply set the Condition</p>
<pre>Ticket: Team &gt; Is &gt; Unassigned</pre>
<p>and Action</p>
<pre>Ticket: Assignee &gt; John Doe </pre>
<p>You can also use <a href="https://support.helprace.com/i722-user-groups">User Groups</a> and <a href="https://support.helprace.com/i723-organizations">Organizations</a> in <a href="https://support.helprace.com/i123-setting-instant-ticket-rules-triggers">instantaneous</a> business rules and <a href="https://support.helprace.com/i122-setting-time-based-ticket-rules-automations">time-based</a> business rules.</p>
<h4 id="mcetoc_1cr59sn661v">Sending notifications to Teams</h4>
<p><b>You can send an email to members of a whole team at once.</b></p>
<p>Example: You want to let agents know a ticket has been assigned to their Team. Simply set the Condition</p>
<pre>Ticket: Team &gt; Changed</pre>
<p>and Action</p>
<pre>Notification: Email user &gt; (Assigned Team)</pre>
<h2 id="mcetoc_1cr59sn6620">Teams in User Portal</h2>
<h3 id="mcetoc_1cr59sn6621">Content Restrictions</h3>
<p>You can use space restrictions to limit Team access to portal content.</p>
<p>For example, you can restrict access to your portal in a number of ways:</p>
<p><b>FAQ page for Billing &amp; Refund staff</b></p>
<p>A questions and answers page for top management and those with the authority to issue billing &amp; refunds.</p>
<p><b>Knowledge base for Support Tiers</b></p>
<p>A knowledge base for Tier 1 - Tier 3 support engineers to share tips and troubleshooting steps.</p>
<p><b>Issue tracking for Product Teams</b></p>
<p>A problem tracking page for product development teams to report internal issues.</p>
<p><b>Idea lab for support staff</b></p>
<p>An idea and suggestion gathering page to improve support processes.</p>
<p>Learn more about <a href="https://support.helprace.com/i126-space-restrictions">Space restrictions</a></p>]]></content:encoded>
    </item>
    <item>
      <title>User Groups</title>
      <description><![CDATA[<p>About User Groups</p>
<p>User Groups are a collection of your end-users and Organizations. You can have one user or Organization belong to various Groups.</p>
<p>Use Groups to:</p>
<ul>
<li>segment customers by value;</li>
<li>segment customers by support type needed;</li>
<li>restrict access to areas of your user portal;</li>
<li>use them in ticket rules &amp; notifications.</li>
</ul>
<p>Groups cannot contain support agents, because support agents can only be grouped in Teams.</p>
<p>What you can do with Groups Separate requests by user You are an online store that needs to separate your retail customer requests from internal help desk requests. Segment customers by value You are[_cuted_]</p>]]></description>
      <pubDate>Thu, 22 Nov 2018 09:04:37 +0000</pubDate>
      <link>https://support.helprace.com/i722-user-groups</link>
      <guid>https://support.helprace.com/i722-user-groups</guid>
      <author>Edward</author>
      <dc:creator>Edward</dc:creator>
      <content:encoded><![CDATA[<div class="mce-toc">
<div style="display: none;"> </div>
<ul>
<li><a href="#mcetoc_1cr5brhkb22" rel="nofollow">About User Groups</a></li>
<li><a href="#mcetoc_1cr5brhkb23" rel="nofollow">What you can do with Groups</a></li>
<li><a href="#mcetoc_1cr5brhkb24" rel="nofollow">Managing Groups</a>
<ul>
<li><a href="#mcetoc_1cr5brhkb25" rel="nofollow">Creating Groups</a></li>
<li><a href="#mcetoc_1cr5brhkb26" rel="nofollow">Adding &amp; removing users</a>
<ul>
<li><a href="#mcetoc_1cr5brhkb27" rel="nofollow">User Group page</a></li>
<li><a href="#mcetoc_1cr5brhkb28" rel="nofollow">People page</a></li>
<li><a href="#mcetoc_1cr5brhkb29" rel="nofollow">User profile</a></li>
<li><a href="#mcetoc_1cr5brhkb2a" rel="nofollow">Ticket view</a></li>
</ul>
</li>
<li><a href="#mcetoc_1cr5brhkb2b" rel="nofollow">Editing &amp; deleting Groups</a></li>
</ul>
</li>
<li><a href="#mcetoc_1cr5brhkb2c" rel="nofollow">Using Groups with Tickets</a>
<ul>
<li><a href="#mcetoc_1cr5brhkb2d" rel="nofollow">Searching tickets by Groups</a></li>
<li><a href="#mcetoc_1cr5brhkb2e" rel="nofollow">Using Groups in Rules &amp; Notifications</a>
<ul>
<li><a href="#mcetoc_1cr5brhkb2f" rel="nofollow">Specifying Groups in Conditions &amp; Actions</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#mcetoc_1cr5brhkb2g" rel="nofollow">Using Groups with Organizations</a>
<ul>
<li><a href="#mcetoc_1cr5brhkb2h" rel="nofollow">What you can do with Groups and Organizations</a></li>
<li><a href="#mcetoc_1cr5brhkb2i" rel="nofollow">Adding Organizations to Group</a>
<ul>
<li><a href="#mcetoc_1cr5brhkb2j" rel="nofollow">User Groups page</a></li>
<li><a href="#mcetoc_1cr5brhkb2k" rel="nofollow">Organization page, User profile, Ticket view</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#mcetoc_1cr5brhkb2l" rel="nofollow">Using Groups with Organizations and Teams</a></li>
<li><a href="#mcetoc_1cr5brhkb2m" rel="nofollow">Groups in User Portal</a>
<ul>
<li><a href="#mcetoc_1cr5brhkb2n" rel="nofollow">Content Restrictions</a></li>
</ul>
</li>
</ul>
</div>
<h2 id="mcetoc_1cr5brhkb22">About User Groups</h2>
<p>User Groups are a collection of your end-users and Organizations. You can have one user or Organization belong to various Groups.</p>
<p>Use Groups to:</p>
<ul>
<li>segment customers by value;</li>
<li>segment customers by support type needed;</li>
<li>restrict access to areas of your user portal;</li>
<li>use them in ticket rules &amp; notifications.</li>
</ul>
<p>Groups cannot contain support agents, because support agents can only be grouped in <a href="https://support.helprace.com/i721-teams">Teams</a>.</p>
<div>
<h2 id="mcetoc_1cr5brhkb23">What you can do with Groups</h2>
<p><b>Separate requests by user</b></p>
<p>You are an online store that needs to separate your retail customer requests from internal help desk requests.</p>
<p><b>Segment customers by value</b></p>
<p>You are a store that needs to separate your most valuable customers from customers that spend less.</p>
<p><b>Support users in different time zones or languages</b></p>
<p>Create a Group for every time zone and language, assigning your user base to whatever Group you see fit.</p>
<p><b>Limit user portal content to different users</b></p>
<p>Make your user portal viewable to all registered users, but have a hidden area limited to users from VIP Customers Group.</p>
</div>
<h2 id="mcetoc_1cr5brhkb24">Managing Groups</h2>
<p>Only Owners and Admins can manage (create, modify, delete) Groups.</p>
<p>Agents can only add/remove Users and Organizations to Groups.</p>
<h3 id="mcetoc_1cr5brhkb25">Creating Groups</h3>
<ul>
<li>Go to  <i class="fa fa-address-book"> </i>People and select User Groups.</li>
<li>Create a new Group by clicking on the + button and adding a title and optional description.</li>
</ul>
<h3 id="mcetoc_1cr5brhkb26">Adding &amp; removing users</h3>
<p>As soon as you create a Group, you can add existing users to it. Manage users via:</p>
<h4 id="mcetoc_1cr5brhkb27">User Group page</h4>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/722/media/add-users.png" alt="" data-file="___chdfid_3634___"></p>
<ul>
<li>Click on a desired Group.</li>
<li>Click <b>Add User</b>. Start typing in their name or pick from the list. The magnifying glass searches for users already in the Group.</li>
<li>Remove the user by clicking X to the right of their name.</li>
</ul>
<div>
<h4 id="mcetoc_1cr5brhkb28">People page</h4>
<p>Click ⋮ to the right of their name and pick Change Groups.</p>
</div>
<h4 id="mcetoc_1cr5brhkb29">User profile</h4>
<div>
<div>
<p>Click ... to the right of User Participation and pick Change Groups.</p>
</div>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/722/media/user-participation.png" alt="" data-file="___chdfid_3635___"></p>
<p>When Groups are added, they're displayed in the sidebar. Click to change them.</p>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/722/media/user-groups-change2.png" alt="" data-file="___chdfid_3628___"></p>
</div>
<div>
<h4 id="mcetoc_1cr5brhkb2a">Ticket view</h4>
<div>
<p>Click ⋮ to the right of their name and pick Change Groups.</p>
</div>
<p><img src="https://s3.amazonaws.com/chd-data/data/support/items/722/media/user-groups-change.png" alt=""></p>
<blockquote>
<p>If a user assigned to Groups becomes an agent, they will be unassigned from their Groups.</p>
</blockquote>
</div>
<h3 id="mcetoc_1cr5brhkb2b">Editing &amp; deleting Groups</h3>
<ul>
<li>Go to  <i class="fa fa-address-book"> </i>People and select User Groups.</li>
<li>You'll see a list of your Groups. Click the ⋮ button to the right of the desired Group and select Edit or Delete.</li>
</ul>
<div>
<blockquote>Deleting Groups carries some implications. If you set up any Rules &amp; Notifications, they will no longer function as intended.</blockquote>
<h2 id="mcetoc_1cr5brhkb2c">Using Groups with Tickets</h2>
</div>
<h3 id="mcetoc_1cr5brhkb2d">Searching tickets by Groups</h3>
<p>To search for tickets belonging to a certain Group:</p>
<pre>group:"VIP Customers"</pre>
<p>To search for Pending tickets not assigned to a certain Group:</p>
<pre>status:pending -group:"Billing Team"</pre>
<p>Note: searching for a Group in the People page displays users belonging to the Group.</p>
<p><a href="https://support.helprace.com/i93-helprace-search-guide">Learn more about searching</a></p>
<h3 id="mcetoc_1cr5brhkb2e">Using Groups in Rules &amp; Notifications</h3>
<h4 id="mcetoc_1cr5brhkb2f">Specifying Groups in Conditions &amp; Actions</h4>
<p><b>You can filter out incoming requests from a Group.</b></p>
<p>Example: You want tickets from "VIP Customers" to be assigned to the Owner. Simply set the Condition</p>
<pre>Requester: User Group &gt; Is &gt; VIP Customers</pre>
<p>and Action</p>
<pre>Ticket: Assignee &gt; Mr. Owner</pre>
<p><b>You can make a ticket's Group a criteria for additional action.</b></p>
<p>Example: You want tickets from "VIP Customers" and "Bonus Program" Group to be assigned to a Team. Simply set the Condition</p>
<pre>Ticket: Is &gt; Added<br>Requester: User Group &gt; Is &gt; VIP Customers, Bonus Program</pre>
<p>and Action</p>
<pre>Ticket: Assignee &gt; Tier 3 Team</pre>
<p><b>You can add, remove or set one or more Groups to to a user.</b></p>
<p>Example: You want users with tickets tagged "vip" to only belong to the "VIP Customers" and "Bonus Program" Groups. Simply set the Condition</p>
<pre>Ticket: Tags &gt; Contains at least one of the following &gt; vip</pre>
<p>and Action</p>
<pre>Requester: User Group &gt; Set &gt; VIP Customers, Bonus Program</pre>
<p><b>You can check if a ticket is not part of a Group.</b></p>
<p>Example: You want tickets that do not belong to any Group to be automatically assigned to Tier 1 Team. Simply set the Condition</p>
<pre>Requester: User Group &gt; Is &gt; Unassigned</pre>
<p>and Action</p>
<pre>Ticket: Assignee &gt; Tier 1 Team </pre>
<h2 id="mcetoc_1cr5brhkb2g"><a id="inheritance"></a>Using Groups with Organizations</h2>
<p>A Group can have multiple <a href="https://support.helprace.com/i723-organizations">Organizations</a> in it. If a user belongs to Organization that is assigned to a Group, the user will be treated as a member of that Group by inheritance.</p>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/722/media/group-diagram-small.png" alt="" data-file="___chdfid_3633___"></p>
<h3 id="mcetoc_1cr5brhkb2h">What you can do with Groups and Organizations</h3>
<p><b>User Groups can act as support hubs for Organizations</b></p>
<p>Example: Create a User Group consisting of tickets from users belonging to different Organizations.</p>
<p><b>Define access to your user portal by combining User Groups with Organizations</b></p>
<p>Example: Create a portal where customers from ACME and MCC Organizations can participate with VIP Customers Group.</p>
<h3 id="mcetoc_1cr5brhkb2i">Adding Organizations to Group</h3>
<p>Any staff member can add or remove Organizations to a Group.</p>
<p>As soon as you create a Group, you can add existing users to it. Manage users via:</p>
<h4 id="mcetoc_1cr5brhkb2j">User Groups page</h4>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/722/media/user-groups-and-organizations.png" alt="" data-file="___chdfid_3636___"></p>
<ul>
<li>Select Organizations tab.</li>
<li>Start typing Organization name or pick from the list. Remove the Organization by clicking X beside it.</li>
</ul>
<blockquote>
<p>An Organization belonging to a Group will assign users within that Organization to Group by inheritance.</p>
</blockquote>
<h4 id="mcetoc_1cr5brhkb2k">Organization page, User profile, Ticket view</h4>
<p>An Organization has a list of Groups it's assigned to. Click on them to change these associations.</p>
<p><img src="https://s3.amazonaws.com/chd-data/data/support/items/722/media/user-organization-change2.png" alt=""></p>
<h2 id="mcetoc_1cr5brhkb2l">Using Groups with Organizations and Teams</h2>
<p>Viewing:</p>
<ul>
<li>Save views as filters for tickets from User Groups</li>
<li>
<div>Restrict customer support agents to tickets from a Group or a combination of Groups</div>
</li>
<li>Create off-limits content (Spaces) in your portal for certain Teams and Groups</li>
</ul>
<p>Rules &amp; Notifications:</p>
<ul>
<li>Automatically assign ticket received from users in a Group to a specific Team or agent</li>
<li>Automatically add new users to an Organization based on their email domain</li>
</ul>
<h2 id="mcetoc_1cr5brhkb2m">Groups in User Portal</h2>
<h3 id="mcetoc_1cr5brhkb2n">Content Restrictions</h3>
<p>You can use space restrictions to limit user access to portal content.</p>
<p>For example, you can restrict access to your portal in a number of ways:</p>
<p><b>FAQ page for paying customers</b></p>
<p>A questions and answers page for features for paid customers.</p>
<p><b>Knowledge base for VIP Clients</b></p>
<p>A knowledge base with premium content for VIP clients.</p>
<p><b>Issue tracking for technical users</b></p>
<p>A problem tracking page for customers familiar with your product.</p>
<p><b>Idea lab for beta testers</b></p>
<p>An idea and suggestion gathering page for users testing the product.</p>
<p>Learn more about <a href="https://support.helprace.com/i126-space-restrictions">Space restrictions</a></p>]]></content:encoded>
    </item>
    <item>
      <title>Organizations</title>
      <description><![CDATA[<p>About Organizations</p>
<p>Organizations are a collection of your end-users by company. A user can be part of one Organization and Organizations can be part of User Groups.</p>
<p>Use Organizations to:</p>
<ul>
<li>keep track of what company is contacting you;</li>
<li>allow staff to see all member participation within an organization (tickets or topics started).</li>
<li>allow organization users to share or view shared tickets;</li>
<li>automatically add users to an organization with a domain;</li>
<li>restrict access to areas of your user portal;</li>
<li>use them in ticket rules &amp; notifications.</li>
</ul>
<p>Organizations cannot contain support agents, because support agents can only be grouped in Teams.</p>
<p>What[_cuted_]</p>]]></description>
      <pubDate>Tue, 18 Dec 2018 12:05:20 +0000</pubDate>
      <link>https://support.helprace.com/i723-organizations</link>
      <guid>https://support.helprace.com/i723-organizations</guid>
      <author>Edward</author>
      <dc:creator>Edward</dc:creator>
      <content:encoded><![CDATA[<div class="mce-toc">
<div style="display: none;"> </div>
<ul>
<li><a href="#mcetoc_1cr5h59292o" rel="nofollow">About Organizations</a></li>
<li><a href="#mcetoc_1cr5h59292p" rel="nofollow">What you can do with Organizations</a></li>
<li><a href="#mcetoc_1cr5h59292q" rel="nofollow">Managing Organizations</a>
<ul>
<li><a href="#mcetoc_1cr5h59292r" rel="nofollow">Creating Organizations</a>
<ul>
<li><a href="#mcetoc_1cr5h59292s" rel="nofollow">Domains</a></li>
<li><a href="#mcetoc_1cr5h59292t" rel="nofollow">Ticket Restrictions</a></li>
</ul>
</li>
<li><a href="#mcetoc_1cse44h7c0" rel="nofollow">Settings</a>
<ul>
<li><a href="#mcetoc_1cse55lnv2" rel="nofollow">Shared Organizations</a></li>
<li><a href="#mcetoc_1cse55lnv3" rel="nofollow">Auto-create Organizations</a></li>
</ul>
</li>
<li><a href="#mcetoc_1cr5h59292u" rel="nofollow">Adding &amp; removing users</a>
<ul>
<li><a href="#mcetoc_1cr5h59292v" rel="nofollow">Organization view</a></li>
<li><a href="#mcetoc_1cr5h592930" rel="nofollow">User profile, Ticket view</a></li>
</ul>
</li>
<li><a href="#mcetoc_1cr5h592931" rel="nofollow">Editing, merging &amp; deleting Organizations</a>
<ul>
<li><a href="#mcetoc_1cr78otcr0" rel="nofollow">Organization view</a></li>
</ul>
</li>
<li><a href="#mcetoc_1cr5h592932" rel="nofollow">Viewing Organizational activity</a>
<ul>
<li><a href="#mcetoc_1cr5h592933" rel="nofollow">Organizations view</a></li>
<li><a href="#mcetoc_1cr5h592934" rel="nofollow">User profile, Ticket view</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#mcetoc_1cr5h592935" rel="nofollow">Using Organizations with Tickets</a>
<ul>
<li><a href="#mcetoc_1cr5h592a36" rel="nofollow">Searching tickets by Organizations</a></li>
<li><a href="#mcetoc_1cr5h592a37" rel="nofollow">Using Organizations in Rules &amp; Notifications</a>
<ul>
<li><a href="#mcetoc_1cr5h592a38" rel="nofollow">Specifying Organizations in Conditions &amp; Actions</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#mcetoc_1cr5h592a39" rel="nofollow">Using Organizations with Groups</a>
<ul>
<li><a href="#mcetoc_1cr5h592a3a" rel="nofollow">Group associations</a>
<ul>
<li><a href="#mcetoc_1cr78otcr1" rel="nofollow">Organizations view</a></li>
<li><a href="#mcetoc_1cr5brhkb2k" rel="nofollow">Organization page, User profile, Ticket view</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#mcetoc_1cr5h592a3b" rel="nofollow">Using Organizations with User Groups and Teams</a></li>
<li><a href="#mcetoc_1cr5h592a3c" rel="nofollow">Organizations in User Portal</a></li>
</ul>
</div>
<h2 id="mcetoc_1cr5h59292o">About Organizations</h2>
<p>Organizations are a collection of your end-users by company. A user can be part of one Organization and Organizations can be part of User Groups.</p>
<p>Use Organizations to:</p>
<ul>
<li>keep track of what company is contacting you;</li>
<li>allow staff to see all member participation within an organization (tickets or topics started).</li>
<li>allow organization users to share or view shared tickets;</li>
<li>automatically add users to an organization with a domain;</li>
<li>restrict access to areas of your user portal;</li>
<li>use them in ticket rules &amp; notifications.</li>
</ul>
<p>Organizations cannot contain support agents, because support agents can only be grouped in <a href="https://support.helprace.com/i721-teams">Teams</a>.</p>
<h2 id="mcetoc_1cr5h59292p">What you can do with Organizations</h2>
<p><b>Track and manage tickets and topics by company</b></p>
<p>You are a B2B which sells items to other companies. Organizations help you manage this.</p>
<p><b>Maintain and divide up requests based on email domains</b></p>
<p>You frequently get emails from users with an @acme.com email, so every time a user with that domain contacts you, it can automatically get added to that Organization.</p>
<p><b>Let everyone in an Organization to see each other's tickets or collaborate on them</b></p>
<p>You want users from ACME to see and respond to all tickets submitted by other members within their organization. You want users from MCC Inc to see tickets submitted by members, but not respond to them (read-only).</p>
<p><b>Limit user portal content to Organizations</b></p>
<p>Your user portal may be visible to all your registered users, but an area can stay hidden to customers from VIP clients who belong to an Organization.</p>
<h2 id="mcetoc_1cr5h59292q">Managing Organizations</h2>
<h3 id="mcetoc_1cr5h59292r">Creating Organizations</h3>
<p>Any staff member can create Organizations.</p>
<ul>
<li>Go to  <i class="fa fa-address-book"> </i>People and select Organizations.</li>
<li>Create a new Organization by clicking on the + button. Enter a name.</li>
</ul>
<p>You can also add organization directly from the sidebar in Ticket view or User profile.</p>
<h4 id="mcetoc_1cr5h59292s"><a id="domain"></a>Domains</h4>
<p>If you have users with an email address @acme.com, including the domain (acme.com) will add them to the Organization automatically. This is regardless of whether your users or Organization are created first.</p>
<p>Leave this blank if you don't want to associate your Organization with domains.</p>
<p>Here are some things to keep in mind:</p>
<ul>
<li>Removing a domain won't automatically disassociate included users.</li>
<li>A previously associated user will not be removed if their associative email is changed.</li>
<li>If a user already belongs to an Organization, they won't be assigned to another one automatically.</li>
<li>If a user has multiple emails they will be checked individually, starting from the primary email. If an email's domain matches the Organization, the user will be assigned to Organization.</li>
</ul>
<h4 id="mcetoc_1cr5h59292t">Ticket Restrictions</h4>
<p>Every Organization restricts its members' ticket functions. </p>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/723/media/organization-restrictions.png" alt="" data-file="___chdfid_4701___"></p>
<p>There are three options:</p>
<ul>
<li>Restricted allows users to view and respond to their own tickets only.</li>
<li>Visible allows users to view and respond to their own tickets as well as view all tickets within their Organization.</li>
<li>Shared allows users to view and respond to all tickets within their Organization.</li>
</ul>
<p>How users can <a href="https://support.helprace.com/i87-your-user-profile-and-account-settings">work with their Organization's tickets</a></p>
<h3 id="mcetoc_1cse44h7c0"><a id="settings"></a>Settings</h3>
<h4 id="mcetoc_1cse55lnv2">Shared Organizations</h4>
<p>This ticket restriction setting will be set as the default one. Ticket restrictions can be changed anytime.</p>
<h4 id="mcetoc_1cse55lnv3">Auto-create Organizations</h4>
<p>You can automatically create an Organization when a user with a new corporate domain in their email address contacts you.</p>
<p>Previously created users with domains matching that of an existing Organization will be added to it once they display some sort of activity.</p>
<blockquote>
<p>Free domains, such as those used by email clients (gmail.com, outlook.com) cannot be added to Organizations. However, users with a free email account can be added to an Organization manually.</p>
</blockquote>
<h3 id="mcetoc_1cr5h59292u">Adding &amp; removing users</h3>
<p>Any staff member can add or remove users.</p>
<p>As soon as you create an Organization, you can add existing users to it. You can add users automatically using <a href="#domain" rel="nofollow">domains</a>.</p>
<p>Manage users via:</p>
<h4 id="mcetoc_1cr5h59292v">Organization view</h4>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/723/media/add-users.png" alt="" data-file="___chdfid_4713___"></p>
<ul>
<li>When viewing an Organization, Click <b>Add User</b>. Start typing in their name or pick from the list. The magnifying glass searches for users already in the Organization.</li>
<li>Disassociate the user from Organization by clicking X beside their name.</li>
</ul>
<blockquote>
<p>If a user already belongs to a different Organization, you won't see their name in the suggestions to add.</p>
</blockquote>
<h4 id="mcetoc_1cr5h592930">User profile, Ticket view</h4>
<p>Click Organization in the sidebar. If a user does not have an Organization, you can add one.</p>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/723/media/user-organization-change.png" alt="" data-file="___chdfid_4703___"></p>
<p>If the user already has an Organization, you'll see it (as well as any Group associations).</p>
<p>You can leave Organization notes which will be visible with the Organization in the sidebar.</p>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/723/media/user-organization-change2.png" alt="" data-file="___chdfid_4704___"></p>
<h3 id="mcetoc_1cr5h592931">Editing, merging &amp; deleting Organizations</h3>
<ul>
<li>Go to  <i class="fa fa-address-book"> </i>People and select Organizations.</li>
<li>Click the ⋮ button to the right of the desired Organization and select Edit, Merge Into and Delete.</li>
</ul>
<h4 id="mcetoc_1cr78otcr0">Organization view</h4>
<p>When viewing an Organization, click the Pencil icon, Merge or the Trashbin icon.</p>
<blockquote>
<p>You cannot merge an Organization into itself.</p>
</blockquote>
<blockquote>Deleting Organizations carries some implications. If you set up any Rules &amp; Notifications, they will no longer function as intended.</blockquote>
<h3 id="mcetoc_1cr5h592932">Viewing Organizational activity</h3>
<p>Support staff can view all interactions, including tickets submitted or topics started by members of a given Organization.</p>
<h4 id="mcetoc_1cr5h592933">Organizations view</h4>
<p>When viewing an Organization,</p>
<p>Select <b>Tickets</b> to see all tickets participated in by Organization members.
<br>
Filter tickets by status (All, New, Open, Pending, On-hold, Solved, Closed)</p>
<p>Select <b>Community</b> to see all topics participated in by Organization members.
<br>
Filter content by type (All, Questions, Ideas, Problems, Praise, Articles, Updates, Actions)</p>
<h4 id="mcetoc_1cr5h592934">User profile, Ticket view</h4>
<p>Click <b>Organization</b> in the sidebar. All tickets and community topics started by Organization members will be visible here.</p>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/723/media/user-organization-change2.png" alt="" data-file="___chdfid_4704___"></p>
<h2 id="mcetoc_1cr5h592935">Using Organizations with Tickets</h2>
<h3 id="mcetoc_1cr5h592a36">Searching tickets by Organizations</h3>
<p>To search for tickets belonging to a certain Organization, type in the query</p>
<pre>organization:"ACME Inc"</pre>
<p>To search for Pending tickets not assigned to a certain, type in the query</p>
<pre>status:pending -organization:"ACME Inc"</pre>
<p>Searching for an Organization in the People page displays users belonging to the Organization.</p>
<p><a href="https://support.helprace.com/i93-helprace-search-guide">Learn more about searching</a></p>
<h3 id="mcetoc_1cr5h592a37">Using Organizations in Rules &amp; Notifications</h3>
<h4 id="mcetoc_1cr5h592a38">Specifying Organizations in Conditions &amp; Actions</h4>
<p>You can specify an Organization in business rule conditions and actions. This allows you to filter out incoming requests from an Organization they belong to.</p>
<p><b>You can make a user's Organization a criteria for additional action.</b></p>
<p>Example: You want tickets from ACME Organization to automatically get assigned to ACME Team. Simply set the Condition</p>
<pre>Ticket: Is &gt; Added<br>Requester: Organization &gt; Is &gt; ACME</pre>
<p>and Action</p>
<pre>Ticket: Assignee &gt; ACME Team</pre>
<p><b>You can set or remove an Organization from a user.</b></p>
<p>Example: You want users with tickets tagged "acme" assigned to the ACME Organization. Simply set the Condition</p>
<pre>Ticket: Tags &gt; Contains at least one of the following &gt; ACME</pre>
<p>and Action</p>
<pre>Requester: Organization &gt; ACME</pre>
<p><b>You can check if a user does not belong to an Organization.</b></p>
<p>Example: You want tickets that do not belong to any Organization to be automatically assigned to someone. Simply set the Condition</p>
<pre>Requester: Organization &gt; Is &gt; Unassigned</pre>
<p>and Action</p>
<pre>Ticket: Assignee &gt; John Doe </pre>
<h2 id="mcetoc_1cr5h592a39">Using Organizations with Groups</h2>
<p>A <a href="https://support.helprace.com/i722-user-groups">Group</a> can have multiple Organizations in it. If a user belongs to Organization that is assigned to a Group, the user will be treated as a member of that Group by inheritance.</p>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/723/media/group-diagram-small.png" alt="" data-file="___chdfid_4714___"></p>
<p><b>User Groups can act as support hubs for Organizations</b></p>
<p>Example: Create a User Group  consisting of tickets from users belonging to different Organizations.</p>
<p><b>Define access to your user portal by combining User Groups with Organizations</b></p>
<p>Example: Create a portal where customers from ACME and MCC Organizations can participate with VIP Customers Group.</p>
<h3 id="mcetoc_1cr5h592a3a">Group associations</h3>
<p>Any staff member can add or remove Organizations to a Group.</p>
<h4 id="mcetoc_1cr78otcr1">Organizations view</h4>
<p><img src="//s3.amazonaws.com/chd-data/data/support/items/723/media/change-groups.png" alt="" data-file="___chdfid_4705___"></p>
<ul>
<li>Click <b>Change Groups</b>.</li>
<li>Start typing Group name or pick from the list. Remove Group by clicking X beside it.</li>
</ul>
<h4 id="mcetoc_1cr5brhkb2k">Organization page, User profile, Ticket view</h4>
<p>An Organization has a list of Groups it's assigned to. Click on them to change these associations.</p>
<p><img src="https://s3.amazonaws.com/chd-data/data/support/items/722/media/user-organization-change2.png" alt=""></p>
<h2 id="mcetoc_1cr5h592a3b">Using Organizations with User Groups and Teams</h2>
<p>Viewing:</p>
<ul>
<li>Save views as filters for tickets from Organizations.</li>
<li>
<div>Restrict customer support agents to tickets only from an Organization or combination of Organizations</div>
</li>
<li>Create off-limits content (Spaces) in your portal for certain Teams and Organizations.</li>
</ul>
<p>Rules &amp; Notifications:</p>
<ul>
<li>Automatically assign ticket received from users in an Organization to a specific Team or agent</li>
<li>Automatically add new users to an Organization based on their email domain</li>
</ul>
<h2 id="mcetoc_1cr5h592a3c">Organizations in User Portal</h2>
<p>Depending on Organization permissions, you can allow (or deny) users to view or participate in their Organization's tickets.</p>
<p>Users can work with their Organization's tickets in the user portal. <a href="https://support.helprace.com/i87-your-user-profile-and-account-settings">Learn more</a></p>
<p><span style="font-size: 18px;">Content Restrictions</span></p>
<p>You can use space restrictions to limit an Organization's users access to portal content.</p>
<p>For example, you can restrict access to your portal in a number of ways:</p>
<p><b>FAQ page for ACME</b></p>
<p>A questions and answers page for everyone from the ACME Organization.</p>
<p><b>Knowledge base for Technical Department of ACME</b></p>
<p>A knowledge base with ticketing collaboration for a technical users within ACME.</p>
<p><b>Issue tracking from all users and ACME</b></p>
<p>A problem tracking page for all users as well as input from ACME.</p>
<p><b>Idea lab for beta testers from all Organizations</b></p>
<p>An idea and suggestion gathering page for users belonging to any Organization.</p>
<p>Learn more about <a href="https://support.helprace.com/i126-space-restrictions">Space restrictions</a></p>]]></content:encoded>
    </item>
  </channel>
</rss>
