{"id":3534,"date":"2020-07-07T17:52:09","date_gmt":"2020-07-07T17:52:09","guid":{"rendered":"https:\/\/www.k12insight.com\/kc\/?post_type=article&p=3534"},"modified":"2026-03-16T21:37:31","modified_gmt":"2026-03-16T21:37:31","slug":"user-roles","status":"publish","type":"post","link":"https:\/\/www.k12insight.com\/kc\/getting-started\/user-roles\/","title":{"rendered":"User Roles"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Ensuring team members understand their roles in Onflo helps ensure a successful implementation and exceptional service for your community. In Onflo there are System roles and Category\/Topic roles. System Permissions<\/b> determine the level of access in Onflo a user is granted. Category and Topic roles<\/b> determine your topic-specific responsibilities in Onflo.<\/p>\n

To view your role, hover on your name in the top right corner.<\/span><\/p>\n

\"\"<\/span><\/p>\n

System Permissions<\/strong><\/p>\n

There are four roles in the Onflo system. These roles determine a user's permission level within the platform. <\/span><\/p>\n

    \n
  1. System Administrator<\/b>: This role has full access to the Onflo Account, overseeing all activity, and has the ability to customize all account settings, including the Topics, Users, and Roles for the district.<\/span><\/span><\/li>\n
  2. Global User<\/b>: This role serves as an overseer of all ticket activities within the district account. Global Users have access to all tickets and dashboards within the system, but limited access to account settings.<\/span><\/span><\/li>\n
  3. Team Member<\/b>: Most users in Onflo will be assigned this role. Team Members can access tickets submitted to the Topic(s) they belong to and any tickets they are added to.
    <\/span><\/li>\n
  4. Recorder<\/b>: This role allows a user to exclusively create tickets from in-bound inquiries, such as in-person visits, phone calls, or letter communications. Recorders are unable to respond to tickets.<\/li>\n<\/ol>\n\n\n\n\n\t\n\n\t\n\t\n\t\n\t
    Role<\/th>Settings Access<\/th>Tickets Access<\/th>Dashboard Access<\/th>Reply to Customers?<\/th>\n<\/tr>\n<\/thead>\n
    System Administrator<\/td>All Features<\/td>All Tickets<\/td>Overview - All Data
    \nComparison - All Data
    \n<\/td>    		Yes<\/td>\n<\/tr>\n
    Global User<\/td>Role-specific Features<\/td>All Tickets<\/td>Overview - All Data
    \nComparison - All Data
    \n<\/td>    		Yes<\/td>\n<\/tr>\n
    Team Member<\/td>Role-specific Features<\/td>Topic Specific <\/td>Overview - Topic Data<\/td>Yes<\/td>\n<\/tr>\n
    Recorder<\/td>Role-specific Features<\/td>Topic or Ticket Specific <\/td>Overview - Topic Data<\/td>No<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n

    Custom User Roles for Granular Permission Control<\/strong><\/h2>\n

    Define exactly what each user can view or manage
    <\/b>System Administrators can create custom roles allowing granular control over system settings, locations, asset types, inboxes, and more. This ensures roles match real district job functions\u2014for example, giving school principals view-only access while granting IT managers full administrative control\u2014and protecting sensitive areas, such as Campaign Manager, Global Tickets, Call Recordings.<\/p>\n

    Category and Topic Roles<\/strong><\/h2>\n

    Users can also be assigned category and topic specific roles. Users can hold multiple roles across different categories and topics they are assigned to. For instance: a user might be the owner of a Special Education topic, and a team member of a Transportation topic. <\/span><\/p>\n

    Category Administrator<\/b><\/h4>\n

    Category Administrators are responsible for an entire Category (a group of related Topics). Even if a user is not a system administrator, they will have similar privileges for the Category they are made administrator over. Category Administrators have the ability to create Topics within that Category and assign users within each of those Topics, as well as see all data and metrics for the category. <\/span><\/p>\n

    Responsibilities<\/strong><\/h5>\n
      \n
    • Oversee Topics within the Category, including dashboard metrics.<\/span><\/li>\n
    • Create Topics within the Category.<\/span><\/li>\n
    • Assign users to Topics within the Category.<\/span><\/li>\n
    • Create Category-specific access points such as Landing Pages and Tabs.<\/span><\/li>\n
    • Customize Category-specific settings, including translations. <\/span><\/li>\n<\/ul>\n

      Category Administrators are assigned by System Administrators on the <\/span>Categories<\/b> page under <\/span>Settings<\/b> > <\/span>Tickets<\/b> ><\/span>Topic Manager > Topics<\/b>. This role is optional, and only one Category Administrator can be assigned per Category. Only users with <\/span>Team Member<\/b> system permissions can be made Category Administrator.<\/span><\/p>\n

      Topic Owner<\/b><\/h4>\n

      Topic Owners are responsible for all tickets received from that Topic. Owners are notified when new tickets are received, but can delegate tickets to Team Members or reassign tickets to other Topics. <\/span><\/p>\n

      Responsibilities<\/strong><\/h5>\n
        \n
      • Oversee ticket activity within the Topic, including dashboard metrics.<\/span><\/li>\n
      • Ensure all tickets are closed out in a timely manner.<\/span><\/li>\n
      • Customize form messages for the Topic.<\/span><\/li>\n
      • Add users to the Topic.<\/span><\/li>\n<\/ul>\n

        Topic Owners are assigned by System Administrators or Category Administrator. This is a required role, and only one Topic Owner can be assigned per Topic.<\/span><\/p>\n

        Team Member<\/b><\/h4>\n

        Team Members have access to all tickets within an assigned Topic. Team members may be assigned because they have been identified as a content expert for the topic of interest. Team members are responsible for ensuring any tickets assigned to them by the Topic Owner are handled within the agreed upon service level agreement. <\/span><\/p>\n

        Responsibilities<\/strong><\/h5>\n
          \n
        • Collaborate with the topic owner and other team members to ensure tickets are responded to within a timely manner. <\/span><\/li>\n
        • Oversee ticket activity within the Topic, including dashboard metrics.<\/span><\/li>\n<\/ul>\n

          Team Members are assigned by System Administrators, Category Administrator or Topic Owners. There is no limit to the number of team members per Topic. <\/span><\/p>\n

          Landing Page Manager<\/b><\/h4>\n

          The Landing Page Manager designation can be used to provide a user with limited access to maintain and update specific landing pages. Landing page managers enable efficient delegation and management of landing page content across users.<\/span><\/p>\n

          Responsibilities & Capabilities:<\/b><\/h5>\n
            \n
          • Edit landing page content, layout, and design features.<\/span><\/li>\n
          • Manage categories and featured topics.<\/span><\/li>\n
          • Preview and publish content.<\/span><\/li>\n<\/ul>\n

            System Administrators can assign any user to be a Landing Page Manager by following these steps:<\/p>\n

              \n
            1. Click <\/span>Settings<\/b> <\/span>> Tickets ><\/b> <\/span>Portals<\/b> > <\/span>Landing Page \/ Tab<\/b>. <\/b> <\/b><\/li>\n
            2. Click the name of the landing page, then select the correct user from the dropdown menu on the right side of the page.<\/b><\/li>\n
            3. Click <\/span>Save<\/b>.<\/li>\n<\/ol>\n

              \"\"<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

              Ensuring team members understand their roles in Onflo helps ensure a successful implementation and exceptional service for your community. In Onflo there are System roles and Category\/Topic roles. System Permissions determine the level of access in Onflo a user is granted. Category and Topic roles determine your topic-specific responsibilities in Onflo. To view your role, hover on your...<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"categories":[451],"class_list":["post-3534","post","type-post","status-publish","format-standard","hentry","category-getting-started"],"_links":{"self":[{"href":"https:\/\/www.k12insight.com\/kc\/wp-json\/wp\/v2\/posts\/3534","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.k12insight.com\/kc\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.k12insight.com\/kc\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.k12insight.com\/kc\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.k12insight.com\/kc\/wp-json\/wp\/v2\/comments?post=3534"}],"version-history":[{"count":28,"href":"https:\/\/www.k12insight.com\/kc\/wp-json\/wp\/v2\/posts\/3534\/revisions"}],"predecessor-version":[{"id":15959,"href":"https:\/\/www.k12insight.com\/kc\/wp-json\/wp\/v2\/posts\/3534\/revisions\/15959"}],"wp:attachment":[{"href":"https:\/\/www.k12insight.com\/kc\/wp-json\/wp\/v2\/media?parent=3534"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.k12insight.com\/kc\/wp-json\/wp\/v2\/categories?post=3534"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}