Notifications
Clear all
Topic starter
25/06/2026 1:31 am
TL;DR: Globe Telecom says its identity programme cut new-hire onboarding from 19 days to same-day readiness while reducing manual approvals and improving access management, according to SailPoint. The case shows that identity governance can remove operational friction without weakening control when onboarding, password handling, and user experience are treated as one programme.
NHIMG editorial — based on content published by SailPoint: Globe Telecom: Identity Empowers a Seamless User Experience
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.
Questions worth separating out
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.
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.
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.
Practitioner guidance
- Standardise joiner workflows Map the top onboarding paths into policy-based workflows so routine hires do not require repeated manual approval decisions.
- Separate exception handling from standard provisioning Define which access requests can be auto-approved by role and which must pause for review.
- Measure onboarding delay as a governance signal Track time-to-access, approval handoffs, and exception rates together.
What's in the full article
SailPoint's full blog covers the operational detail this post intentionally leaves for the source:
- The specific onboarding workflow changes Globe Telecom made to move from 19 days to same-day readiness.
- The way identity management was tied to employee experience, password handling, and internal process simplification.
- The customer context behind the scale of Globe Telecom's identity environment across employees, customers, and partners.
👉 Read SailPoint's blog on Globe Telecom's identity-led onboarding programme →
Identity-led onboarding at Globe Telecom: what changes for IAM teams?
Explore further
25/06/2026 11:00 am
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.
A few things that frame the scale:
- 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.
A question worth separating out:
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.
👉 Read our full editorial: Globe Telecom’s identity programme shows onboarding can move faster
