Skip to content
OTOBO Community Guide

OTOBO Agent Administration

This section covers everything related to agent administration in OTOBO – from groups and roles through access control lists to authentication mechanisms.

Topics

Section titled “Topics”

Frequently asked questions

What is an agent in OTOBO and what responsibilities do they typically have?

An agent in OTOBO refers to a user who interacts with the OTOBO backend, typically to manage and process service requests, tickets, or other operational tasks. These individuals are often members of IT service management teams, facility management, human resources, or marketing departments, utilizing OTOBO as a central platform for their work. Agents are distinct from customer users, who interact via the customer portal. Their responsibilities can range from handling incoming tickets, communicating with customers, managing queues, and configuring system settings, depending on their assigned permissions and roles within the system. Effective agent administration ensures that each agent has the appropriate access and tools to perform their duties efficiently and securely.

Quellen / Sources:

What are the core components of agent administration covered in this section?

This section of the OTOBO Community Guide provides a comprehensive overview of agent administration, covering several critical areas to ensure efficient and secure operation. Key topics include:

  • Groups & Roles: Managing permissions by assigning agents to specific groups and roles, which dictate their access to queues and functions.
  • Access Control Lists (ACLs): Configuring fine-grained rules to control agent access to various OTOBO resources and functionalities, enabling precise permission management.
  • Authentication Mechanisms: Setting up secure login methods, including Single Sign-On (SSO) with Kerberos and authentication via OpenID Connect.
  • Communication: Managing communication channels such as emails, notifications, OAuth2 integrations, and SMS for agents.
  • Customer Management: Administering customer records, customer users, and external interfaces related to customer interactions.
    These components collectively empower administrators to maintain a robust and controlled environment for all OTOBO agents.

Quellen / Sources:

How does OTOBO manage agent permissions and access control?

OTOBO manages agent permissions and access control primarily through a combination of Groups & Roles and Access Control Lists (ACLs). Agents are assigned to one or more groups, and roles are then assigned to these groups. These roles define the broad permissions an agent has, such as access to specific queues, functions, or modules within the OTOBO system. For more granular control, administrators can configure Access Control Lists (ACLs). ACLs allow for the creation of fine-grained rules that dictate precisely what an agent can see, modify, or execute based on various criteria, including ticket states, queue assignments, or even specific field values. This layered approach ensures that agents only have access to the information and functionalities necessary for their specific tasks, enhancing security and operational efficiency.

Quellen / Sources:

What authentication methods are supported for OTOBO agents?

OTOBO supports several robust authentication methods for agents, ensuring secure and flexible login options. This documentation specifically highlights two advanced mechanisms: Single Sign-On (SSO) with Kerberos and OpenID Connect. Kerberos SSO allows agents to log into OTOBO automatically using their existing network credentials, eliminating the need for separate OTOBO usernames and passwords and streamlining the login process within an enterprise environment. OpenID Connect provides a modern, identity layer on top of the OAuth 2.0 protocol, enabling agents to authenticate using third-party identity providers. These options enhance security, improve user experience by reducing password fatigue, and simplify identity management for administrators.

Quellen / Sources:

Can OTOBO integrate with external user directories for agent management?

Yes, OTOBO is designed to integrate seamlessly with external user directories for agent management, offering significant flexibility and scalability. The system provides the capability to manage agents across multiple backend sources, supporting up to ten different backends simultaneously. This means that agent information, such as usernames, passwords, and group memberships, can be pulled from existing corporate directories like LDAP, Active Directory, or other database systems, rather than being managed solely within OTOBO's internal database. This feature is crucial for organizations with established identity management systems, as it centralizes user administration, reduces duplication of effort, and ensures consistency in user data. Furthermore, some of these external backends can be configured as read-only, preventing changes to agent data directly from OTOBO.

Quellen / Sources:

How does OTOBO handle communication channels and customer management for agents?

OTOBO provides comprehensive features for managing both communication channels and customer interactions for agents. Under "Communication," the system allows administrators to configure various methods through which agents can interact with customers and receive notifications. This includes setting up email accounts, managing notification preferences, integrating with OAuth2 for secure access to external services, and configuring SMS gateways for text-based communication. For "Customer Management," OTOBO offers tools to administer customer records, manage individual customer users, and configure external interfaces. This ensures that agents have all the necessary information and channels to effectively communicate with and support customers, maintaining a unified and efficient service experience.

Quellen / Sources: