Administrator vs Configuration Agent vs Dialer User

MYLO separates three practical responsibilities: Administrator, Configuration Agent and Dialer User. These are not decorative job titles. They determine which areas a person can see, which operations they can request, and which consequential decisions they may approve.

A small business may have one person covering more than one responsibility, but it should still understand the boundaries. Giving every employee the same powerful account makes mistakes harder to contain and actions harder to explain. MYLO’s role and page permissions let the business grant access according to the work each person actually performs.

The Administrator owns control and accountability

The Administrator is responsible for the MYLO environment as a business system. Typical responsibilities include managing users, assigning permitted roles and pages, controlling high-impact settings, reviewing protected operational information, and approving consequential changes where policy requires administrator authority.

This role should understand the difference between MYLO, Asterisk, Linux and external services. MYLO records users, permissions, proposals, approvals and operating state. Asterisk remains the telephony authority. Linux remains the authority for host and network state. SIP and AI providers remain responsible for their services. An administrator coordinates these boundaries; the role does not make every external fault locally fixable.

Administrators may need access to protected functions such as credential retrieval through an authenticated browser or API path. That does not mean secrets should be pasted into chat or displayed routinely. Administrative power carries an obligation to use the narrow protected path, limit disclosure and preserve audit evidence.

The first administrator often becomes the owner of user setup, approval policy and escalation. The business should name a backup responsible person and establish an account-recovery process. Sharing one administrator password among a team defeats individual accountability.

The Configuration Agent manages supported telecom change

A Configuration Agent works with the supported telephony configuration journey. The person can inspect relevant state, describe a requirement, answer MYLO’s clarifying questions, review a proposed difference and perform the steps permitted by the configured role. Their work commonly concerns endpoints, trunks, inbound routing, IVRs or other supported Asterisk scope.

The word “agent” here describes a user responsibility, not an autonomous AI with unrestricted control. MYLO’s AI layer can understand language, interpret a provider document and draft a structured proposal. Deterministic services still validate scope, enforce permissions, obtain approval, create a pre-change snapshot, apply the supported change and verify the result.

A Configuration Agent should be able to explain the requested outcome and gather evidence, but should not automatically manage users, reveal credentials or approve their own high-impact operation. Whether that user can apply a particular proposal depends on the exact configured permissions and approval policy, not the label alone.

This role also carries a verification responsibility. “Saved successfully” is not an acceptable finishing point. The agent checks reload status, live Asterisk state and the relevant real call path, then records or escalates the outcome.

The Dialer User operates approved campaigns

A Dialer User focuses on outbound campaign operations. Typical work includes viewing permitted campaigns, preparing or selecting approved lead material, monitoring progress, pausing work when needed, reviewing call outcomes and resuming through the authorised flow. This role does not need general access to telephony configuration or user administration.

Campaign creation, functional testing and Start are distinct responsibilities in MYLO’s operating model. A conversational flow can gather requirements and prepare a structured campaign. A representative test proves the real path. Starting customer calls is consequential and requires the appropriate approval. The Dialer User’s exact authority should match the business’s campaign policy.

The deterministic dialer, not the language model, controls pacing, capacity, caller-ID selection, retry eligibility and campaign state. The Dialer User supervises this operational system. They should not be expected to change Asterisk files or diagnose an entire office network to do their daily job.

Lead data and recordings may contain personal or sensitive information. Dialer access should therefore be limited to the campaigns and reports needed for work, with retention and export handled under the organisation’s policy.

Page visibility follows configured access

MYLO’s navigation should reflect page permissions, so different users may see different areas after login. Hiding a menu item helps keep the interface relevant, but it is not the only security boundary. Backend authorisation must enforce the same decision when an API request is made directly.

This matters when roles overlap. A supervisor may need campaign reporting without permission to alter a trunk. A technical person may need configuration evidence without permission to create users. An owner may approve a change without operating every campaign. Page and action access should be intentionally assigned rather than inferred from a broad job title.

If a person cannot see a required page, the answer is not to lend an administrator account. The administrator should review the need, grant the smallest suitable access if justified, and record the change. Temporary responsibilities should be removed when the task ends.

Approval authority is about effect

Routine observation should not need the same approval as a live configuration mutation or campaign start. MYLO ties approval to the effect of an operation. Reading current endpoint status, for example, is different from changing endpoint credentials; viewing a campaign is different from starting calls to customers.

A Configuration Agent can prepare a technically sound proposal while an Administrator makes the business decision to proceed. A Dialer User can monitor a campaign while a designated approver authorises Start or Resume. The exact assignment may differ by organisation, but the separation should be explicit.

Approval is not a substitute for permission. A user who is not authorised to perform an operation should not gain that ability merely by presenting an approval identifier. Conversely, a powerful account should not bypass approval simply because its user can reach the button. MYLO’s deterministic services should enforce both.

A practical division of work

Consider a service business launching an appointment-reminder campaign while also changing its inbound menu. The Configuration Agent gathers department hours, checks current Asterisk routing and prepares the IVR proposal. The Administrator reviews the before-and-after difference, confirms the snapshot scope and approves the change. The team then performs a real inbound call and verifies prompt, keypad, destination and audio.

Separately, the Dialer User prepares the permitted lead list and campaign details. MYLO validates the file, caller IDs, operator or IVR destination, pacing and recording choice through the supported flow. The team runs a representative functional test. A designated approver authorises Start, and the Dialer User monitors deterministic progress and exceptions.

No one needs to paste SIP credentials into chat. The Dialer User does not obtain user-management privileges. The Configuration Agent does not silently start a campaign. The Administrator remains accountable without having to operate every call. Clear division makes the whole process faster to review.

Suggested responsibility matrix

• User and role management: Administrator.
• Protected credential retrieval or rotation approval: Administrator through the protected path, with technical assistance where permitted.
• Current telephony inspection and proposal preparation: Configuration Agent within assigned scope.
• Consequential configuration approval: authorised Administrator or other explicitly configured approver.
• Post-change functional verification: Configuration Agent with the business owner of the affected call flow.
• Campaign preparation and monitoring: Dialer User within permitted campaigns.
• Campaign Start or Resume: the role explicitly authorised for that effect.
• Periodic access review: Administrator with management oversight.

This matrix is a starting point, not a promise that every installation has identical permissions. The actual MYLO configuration and business policy remain decisive.

Questions to ask before assigning a role

• Which pages and records does this person need for normal work?
• Do they need to observe, propose, approve, execute or only monitor?
• Could the permission start customer calls, interrupt service or expose protected information?
• Should a second person approve the effect?
• How will their actions be attributed without using a shared login?
• When will the access be reviewed or removed?

Roles work best when they reduce uncertainty. An Administrator governs the environment, a Configuration Agent manages supported telecom change, and a Dialer User operates approved campaign work. When every person receives only the access required for that responsibility, MYLO remains understandable to both the business and the people supporting it.

How to handle temporary and emergency access

Temporary work should receive temporary access. If a Dialer User must assist with a one-off configuration test, grant the smallest suitable page or supervised function and remove it after verification. Do not convert the account permanently to Administrator because that is quicker than reviewing the requirement.

Emergency access also needs a defined owner. The business should know who can recover the primary Administrator account, how identity will be checked and how the exceptional action will be reviewed afterward. Storing one shared master password in a group chat creates availability and security problems at the same time.

Review role design after incidents. If routine work repeatedly requires administrator intervention, the answer may be a better bounded permission or operating procedure. If a role can reach a protected action it never needs, narrow it. MYLO’s page model should support work, while backend authorisation remains the final enforcement point.

Finally, train each user on the limits of the role. A Configuration Agent should know when approval is required; a Dialer User should know the difference between Pause and a completed campaign; an Administrator should know that protected access is not permission to share secrets. Clear expectations are as important as the technical assignment.

The Three MYLO Roles

ADMIN owns full administration and responsibility assignment. CONFIGURATION_AGENT performs authorised telephony-configuration work within its permitted boundary. DIALER operates approved campaign and calling workflows. These are business-control boundaries: a campaign operator does not need provider secrets or unrestricted system administration.