Globe Telecom’s identity programme shows onboarding can move faster

At a glance

What this is: This is a customer story about Globe Telecom using identity governance to streamline onboarding and reduce manual approval overhead.

Why it matters: It matters because IAM teams across human, NHI, and autonomous programmes face the same scaling problem: manual identity controls do not hold up when identity volume and business speed rise.

By the numbers:

• Globe Telecom reduced the number of days needed to onboard new hires from 19 days to their start date in the company.
• Globe Telecom serves over 85 million customers.
• Globe Telecom has over 8,300 employees and over 1.1 million retailers, distributors, and business partners nationwide.

👉 Read SailPoint's blog on Globe Telecom's identity-led onboarding programme

Context

Identity programme design becomes a scaling problem when a company must manage millions of customer-facing relationships plus a large workforce and partner network. In this case, the article shows how manual onboarding approvals and fragmented identity handling created delay, even though the business needed a more seamless user experience.

For IAM leaders, the important signal is not the telecom sector itself but the governance pattern: when identity workflows are slow, the business absorbs the cost in time, exceptions, and inconsistent access decisions. The same dynamic appears in human IAM, NHI governance, and autonomous access programmes whenever lifecycle controls remain manual.

Key questions

Q: How should organisations reduce onboarding delays without weakening identity controls?

A: Automate the standard joiner path, keep exception handling separate, and base approvals on predefined role rules rather than ad hoc routing. The goal is controlled speed: users should receive timely access through policy, while unusual cases still pause for human review. When onboarding is repeatable, control improves because exceptions become easier to spot.

Q: Why do manual identity workflows create friction in large organisations?

A: Manual workflows create friction because each approval depends on people, queues, and handoffs instead of policy. As identity volume rises, that model slows access, increases inconsistency, and encourages workarounds. Large organisations need standardised entitlement paths and lifecycle automation so identity state changes can be executed at business speed.

Q: What is the difference between identity orchestration and simple provisioning?

A: Provisioning creates or updates access in a target system, while orchestration coordinates the full workflow across approvals, identity sources, and downstream systems. Orchestration is broader because it manages the sequence, timing, and control points that determine whether access is actually usable and auditable.

Q: Who should own onboarding performance in an IAM programme?

A: Onboarding performance should be shared across IAM, HR, application owners, and business process owners because the delay usually sits at the joins between systems. If only the IAM team owns it, the programme misses upstream role design and downstream application readiness. Governance works when ownership matches the end-to-end lifecycle.

Technical breakdown

Why manual onboarding creates identity bottlenecks

Manual onboarding slows access activation because each approval step becomes a queue, not a control. In a large enterprise, the delay is rarely caused by authentication alone. It usually comes from fragmented ownership, inconsistent role assignment, and exceptions that must be resolved by people instead of policy. Identity governance only scales when the entitlement model, workflow, and approval path are standardized enough to support repeatable decisions. Without that, onboarding turns into a business delay rather than a security process.

Practical implication: map onboarding delays to approval handoffs, entitlement design, and role clarity before adding more workflow tooling.

How identity orchestration improves user experience without removing control

Identity orchestration connects joiner workflows, access provisioning, and downstream system updates into one controlled sequence. The point is not to eliminate governance but to remove unnecessary manual intervention from routine cases. When the identity layer is well designed, business users experience faster access while security teams retain policy enforcement, auditability, and lifecycle oversight. This is especially relevant in environments where service delivery depends on many internal systems and partner identities.

Practical implication: automate standard joiner cases first, then preserve manual review only for exceptions and high-risk entitlements.

Why password handling still belongs inside the identity programme

Passwords are not just an authentication issue. They are part of identity operations because account activation, credential reset, and lifecycle timing all affect whether access is usable and secure. If password administration sits outside the broader identity process, users feel friction and administrators create workarounds. A mature programme treats credential management, onboarding, and access provisioning as linked controls rather than separate tasks. That reduces delay and lowers the chance of inconsistent access states.

Practical implication: align password operations with onboarding and access provisioning so users do not wait on disconnected administrative steps.

NHI Mgmt Group analysis

Identity friction is an operating model problem, not just an access workflow problem. When onboarding takes 19 days, the business is signaling that identity decisions are still being made too late and too manually. The issue is not merely process inefficiency. It is a governance model that makes identity dependent on human routing instead of policy-driven execution. Practitioners should treat delay as evidence that the entitlement and approval model needs redesign.

Seamless user experience and strong control are not opposing goals. The article shows that faster onboarding came from better identity management, not from weakening controls. That matters because many programmes still assume speed requires exception-making. In practice, the better pattern is to standardize low-risk access paths and reserve human review for unusual cases. Practitioners should design for controlled speed, not controlled delay.

Lifecycle automation: this case illustrates how joiner workflows become a governance advantage when identity state changes are handled as a repeatable lifecycle, not as one-off tickets. That concept matters across human IAM, NHI provisioning, and future autonomous access patterns because lifecycle control is what keeps access aligned with business change. The practitioner conclusion is straightforward: if access changes cannot be executed consistently, the programme will keep trading security for waiting time.

Identity programmes earn executive support when they visibly reduce business friction. The most persuasive identity metrics are often operational rather than abstract. Faster onboarding, fewer manual approvals, and fewer help desk interventions tell leadership that governance is enabling the business instead of slowing it down. Practitioners should present identity as a service enabler with controls embedded, not as a back-office approval function.

From our research:

• Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, according to Ultimate Guide to NHIs.
• Only 5.7% of organisations have full visibility into their service accounts, which shows how often lifecycle control is still operating without complete inventory data.
• For a broader view of lifecycle and access governance, see Top 10 NHI Issues for the issues that most often slow identity programmes down.

What this signals

Lifecycle automation is becoming a programme-level differentiator. When onboarding and access decisions remain manual, the organisation pays in delay, support effort, and inconsistent access outcomes. The same pattern appears across identity domains, which is why teams should treat workflow design as a control surface, not a back-office convenience. For a governance baseline, the NIST Cybersecurity Framework 2.0 remains a useful reference for tying identity work to business outcomes.

Identity programmes that reduce friction tend to win executive sponsorship. The practical test is whether the identity layer shortens time-to-productivity while keeping auditability intact. That is as relevant for human joiners as it is for service accounts and future autonomous identities. Teams that can show measurable reductions in manual approvals will find it easier to defend identity investment in planning cycles.

For practitioners

• Standardise joiner workflows Map the top onboarding paths into policy-based workflows so routine hires do not require repeated manual approval decisions. Keep only genuinely high-risk exceptions in human review.
• Separate exception handling from standard provisioning Define which access requests can be auto-approved by role and which must pause for review. This prevents low-risk onboarding from being blocked by unrelated high-risk cases.
• Measure onboarding delay as a governance signal Track time-to-access, approval handoffs, and exception rates together. If delays persist, the root cause is usually entitlement design or ownership, not the ticketing system.
• Align credential tasks with lifecycle events Treat account activation, password handling, and access provisioning as one lifecycle sequence so users are not forced into separate support steps before they can work.

Key takeaways

• The core issue in this case is not telecom scale alone, but the cost of manual identity governance when business growth demands faster access.
• The evidence shows that identity process redesign can cut onboarding from 19 days to same-day readiness without abandoning control.
• IAM teams should treat onboarding speed, approval design, and lifecycle automation as one governance problem, not three separate projects.

Key terms

• Identity Orchestration: Identity orchestration is the coordination of approvals, provisioning, and downstream updates across multiple systems so access changes happen as one controlled flow. It reduces manual handoffs and keeps identity state consistent across the lifecycle, which is especially important when the business needs speed without losing auditability.
• Joiner Workflow: A joiner workflow is the set of steps used to create, approve, and activate access for a new employee or other identity subject. In mature programmes, it is policy-driven, repeatable, and tied to role design so that onboarding does not depend on individual administrator decisions.
• Lifecycle Governance: Lifecycle governance is the discipline of controlling access as identities enter, move through, and leave an organisation. It covers approvals, provisioning, recertification, and offboarding, and its purpose is to keep access aligned with business need while reducing delay, privilege creep, and unmanaged exceptions.
• Entitlement Model: An entitlement model defines which access rights are assigned to which roles, conditions, or identity types. When it is well structured, onboarding is faster because most requests can follow a standard rule set. When it is weak, every request becomes a custom decision and the programme slows down.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.

This post draws on content published by SailPoint: Globe Telecom: Identity Empowers a Seamless User Experience. Read the original.