LINE Official Account: Roles & Permissions
TL;DR
LINE governs business presence through a badge-tiered Official Account (unverified gray / verified blue / premium green). It has an unusually clear, recently-maintained role model — but split across two consoles: a business console (Admin plus Operator variants) for day-to-day work, and a separate developer console (provider and channel roles) for the API. The Messaging API is authenticated with a per-channel access token the account owner mints and revokes.
On this page
Account tiers
LINE governs business presence through a badge-tiered Official Account: an Unverified Account (gray shield) that anyone can open for free but which is not surfaced in LINE's in-app search, a Verified Account (blue shield) that has passed LINE's regional screening and becomes searchable, and a Premium Account (green shield) that LINE designates at its own discretion (LINE OA Guidelines).
Verification is applied for per market — LINE operates through country entities in Japan, Taiwan and Thailand — and generally requires local business details.
Business roles
Day-to-day management happens in the LINE Official Account Manager, which has named roles:
- Admin — full control, including adding and removing members.
- Operator — everything except managing other users.
- Operator (Sending Restricted) — cannot broadcast messages.
- Operator (Insight Restricted) — cannot view analytics.
Only an Admin can change who has access (LINE OA Help Center).
Developer roles are separate
The technical side lives in a separate LINE Developers Console, organized as Providers that contain Channels. Its roles are distinct from the business console: a developer is Admin or Member at the provider level (or "No role" if granted only channel access), and Admin, Member, or Tester at the channel level, with the two scopes granted independently (LINE Developers — Managing roles).
This two-console split — business roles versus developer roles — is a common source of confusion, since being an Admin in one does not grant access in the other.
Who holds the API keys
The Messaging API is authenticated with a channel access token minted per channel. Whoever holds the owning Provider/Channel and an Admin role controls issuing and revoking that token, and access is delegated or removed by adding or dropping developers from the channel (LINE Developers — channel access token).
So unlike Apple or KakaoTalk, a LINE business can hold and manage its own API credentials directly — no mandatory intermediary — though partners are common for multi-channel setups and higher quotas.
Frequently asked questions
What do the LINE Official Account badge colors mean?
A gray shield is an unverified account (free, not searchable). A blue shield is a verified account that passed LINE's regional business screening and is searchable. A green shield is a premium account that LINE designates at its own discretion, on undisclosed criteria.
Why do LINE roles seem to exist in two places?
Because they do. Business roles (Admin, Operator variants) live in the LINE Official Account Manager and govern messaging and content. Developer roles (provider and channel Admin/Member/Tester) live in the separate LINE Developers Console and govern the API. The two are granted independently.
Does a LINE business need a third-party provider?
No. The account owner can mint and revoke the channel access token directly and hold their own API credentials. Providers are common for multi-channel CRM or higher quotas, but not mandatory the way an MSP is for Apple.
Last updated