KakaoTalk Business Account Roles and Permissions

Kakao business access is spread across several products. The Kakao Talk Channel Partner Center is where the channel’s public profile, messages, chat, administrators, and management history live. Kakao Developers holds the app, its platform keys, API settings, and app members. A Biz Wallet and a dealer connection can also exist for paid messaging. A person who can answer channel chats is not automatically the Owner of the Developers app, and an app Editor does not become the channel Master. Kakao describes channel operations in its business guide and app membership in Kakao Developers.

Begin with the channel URL or profile ID. Kakao says the profile ID is the part after pf.kakao.com/ in the Channel URL shown at Channel > Channel Info > Channel URL. That is the ID to match when inspecting a connected app. Next, find the app under Kakao Developers and note its App ID and Owner. The app may be a basic app, a Biz app with registered business information, or a test app. Kakao’s app guide explains those categories. Do not create another app merely because a contractor cannot see the existing one; Kakao recommends using one app per service and a formal owner-change path if access is lost.

The paid-message lane deserves its own entry in an access inventory. A Channel message sent to friends from Partner Center is not the same workflow as an AlimTalk transaction sent through an official dealer. Kakao’s AlimTalk page says the service is supplied by official dealers. Record the dealer account owner, operational contact, sender profile, approved templates, and termination process with the same care as the channel Master and app Owner.

Kakao’s channel business guide names Master and Manager. It says they share normal channel operation permissions, but only the Master can invite or expel Managers, create or connect the channel wallet, and request channel deletion. The guide’s role explanation is the clearest place to decide whether an agency actually needs the top role. A support lead who schedules posts and answers chats can usually work as Manager. The brand’s accountable employee should retain Master.

Kakao’s channel-management guide says a channel supports one Master and up to 49 Managers, 50 administrators in total. That is a ceiling, not a target. An agency with six staff should explain why six individual accounts are needed; a shared Kakao login would hide which person changed a message. The same guide says Channel Management History can be filtered by menu and administrator, making it useful when a campaign went live unexpectedly. Check history before assuming the Master was the person who sent it.

The Partner Center provides both desktop and mobile administration. Kakao’s channel creation guide describes Kakao Business Partner Center PC, its app, and management from KakaoTalk itself. For an invitation, use the Partner Center channel’s Administrator area; the invitee accepts the administrator invitation on their own Kakao Account. If a person needs access but is not yet an administrator, the guide describes requesting permission from the current Master. For removal, the Master expels the Manager in that same channel administration area. Check the channel history afterward to confirm the handoff.

Do not infer wallet ownership from channel operation. The channel guide reserves wallet creation and connection for Master, while Kakao’s Biz Wallet guide describes a separate wallet administrator list. A company may have cleaned up channel Managers but left a former agency member in a wallet. Review the wallet only if the channel uses one, and keep the billing approver separate from a campaign editor where possible.

A Kakao Developers app has four named member roles. Owner holds all app configuration permissions and controls Owner-only key and deletion actions. Editor can configure the app except Owner-only settings. Message Editor can view app information and register or update message templates. Viewer can only view app information. Kakao lists these roles and the Owner-only actions. Do not give an agency app Owner to let it inspect a template; choose the role that matches its job.

An app can be connected to a Business Channel only when the business information matches, the channel has passed Business Channel review, the app is a Biz app, and the actor has suitable permissions on both sides. Kakao’s connection guide says the channel actor needs Master or Manager and the app actor needs Owner or Editor. A connected Business Channel can be linked to only one Biz app. If the channel is absent from the connectable list, inspect its verification state, registered business information, existing app connection, and the two role grants before starting another application.

Kakao Developers names the menu [App] > [Member]. Its member guide says Add member invites a Kakao Account email, while the Owner can use Edit to change roles and Delete to remove members. A dormant member cannot be edited but can be removed. Only one developer account is the app Owner; to transfer that role, the present Owner adds the replacement as a member and then edits that member to Owner. This is a separate transfer from any channel Master handoff.

App keys deserve special handling. Kakao’s Owner-only list includes deleting a Platform key, viewing and managing Admin keys, and changing the Primary key. Its security guidelines say to use roles according to purpose and an allowed IP address for API requests where appropriate. A credential placed in a server can outlive a former employee’s membership; after removing an app Editor who saw production configuration, inspect the keys and deployed secrets with the technical owner.

For channel access, have the current Master open the Kakao Talk Channel Partner Center, select the right channel, and inspect its Administrator area. Invite a Manager using the invite action, then ask that person to accept on their own Kakao Account. Kakao’s channel guide shows an administrator invitation acceptance in the account flow, and its role guide reserves Manager invitations and expulsions for Master. The person should verify they can open the intended channel before you remove a predecessor.

For a Developers app, select the existing app, open [App] > [Member], choose Add member, enter the Kakao Account login email, and choose one of the named roles. The new person may need to complete Kakao Developers registration after receiving the email. The Owner uses Edit for a role change or Delete to remove a member. Kakao documents the member state and controls. A person can have the same email in both consoles, but you still need to check both grants.

Before an agency contract ends, review the channel Master and Managers, app Owner and members, connected channel, Biz Wallet members, and dealer relationship. Remove people from the appropriate surfaces, then ask the dealer to revoke any dealer-side login or integration credential it issued under the contract. The precise dealer procedure depends on that dealer; Kakao’s official AlimTalk page directs customers to official dealers for quotes and detailed functions. Do not assume removing a Channel Manager cancels an AlimTalk service agreement.

When changing the app Owner, follow Kakao’s documented transfer before deleting the old owner’s membership. For the channel Master, arrange the change with the current Master through Partner Center or Kakao Business support, and verify the result in the administrator list. Do not borrow a procedure from Kakao Ads, Biz Wallet, or chatbot products; those are separately managed Kakao assets with their own Master rules.

A general Kakao Talk Channel can be created before it becomes a Business Channel. Kakao describes Business Channel as a reviewed channel with a verification mark beside its name. Its developer guide lists restricted categories, including private loans, adult products, alcohol, tobacco, and industries harmful to minors. The Business Channel review is handled by the Kakao Business Partner Center and usually takes about three to five business days. A badge signals Kakao’s business review; it does not tell you who can edit the app or whether a dealer still has access.

For a Biz app connection, register the same business information in the channel and app. Kakao’s troubleshooting FAQ says mismatched business registration numbers, a dormant or sanctioned channel, or an already connected app can keep the channel out of the list. A former agency may have set up the app under the wrong business operator. Fixing that ownership mismatch is more important than changing a Manager role.

Do not tell a foreign business that a Korean registration certificate is universally mandatory. Kakao’s Business Channel documentation explicitly points United States foreign operators to an overseas Business Channel conversion request and official agencies. That route is specific to the published United States case. For other locations, check the current Kakao Business eligibility guide or ask Kakao Business support for the relevant documents before committing to a launch date. A local agency can help with paperwork and messaging operations, but the brand should still know which legal entity and Kakao Account hold the channel and app.

Verification is not a substitute for channel discoverability settings. Kakao’s channel guide separates Channel public and Search allowed controls. A verified channel can be configured so people cannot find it in search, and an operational team may mistake that for a failed review. Inspect the channel’s public and search settings before submitting another verification request.

Kakao’s business messaging products have different recipient rules. AlimTalk is for informational notices such as order, payment, and delivery updates; Kakao’s AlimTalk page says it is provided through official dealers. Kakao i Connect Message API documentation says AlimTalk can reach users who have not added the channel as a friend. Its FriendTalk description says FriendTalk can be informational or advertising, but reaches only people who added the Kakao Talk Channel. The same current API reference also names Brand Message, whose eligible audience can include users with marketing consent as well as channel friends. Do not plan an advertising campaign as though every phone number is automatically reachable.

The dealer boundary changes the offboarding question. A dealer may issue its own client ID, client secret, sender profile configuration, and account logins under a contract. The Kakao i Connect Message API reference requires OAuth 2.0 authentication using contract-issued client information. Its examples also identify a sender key. That is dealer-side integration access, not the Kakao Developers app Owner role. Ask the dealer to identify every credential and sender profile associated with the business and to confirm the contractual revocation procedure. Keep those details in the company’s vendor register.

Treat templates as controlled customer communications. Kakao’s AlimTalk product description frames the service around informational notices. A template reviewer should check the actual order or payment event, recipient phone source, and fallback route before approving a send. For example, a retailer should not turn a shipment-status template into a coupon campaign merely because it can reach a customer who has not befriended the channel. The technical API may accept a request only after the service’s policy and template process are satisfied; the dealer can explain the current review queue and permitted categories for the contract.

A developer app connection and an AlimTalk dealer are different integrations. Kakao Developers lists channel APIs for relationships, chat entry, and customer management. Kakao’s AlimTalk sales page directs AlimTalk customers to dealers. Inventory both, but do not expect revoking an app Editor to cancel a dealer-issued BizMessage credential.

A channel has one Master according to the Kakao channel-management guide, and a Developers app has one Owner according to the app guide. Those two people can differ. If the founder’s personal Kakao Account is both, arrange a planned handoff before the phone number, password, or employment status changes. Keep the legal business documents and the App ID in company records so support can identify the asset if the account holder disappears.

Kakao says an existing app Owner can add a replacement under [App] > [Member] and change that member to Owner. Its app guide points to a separate owner-change FAQ when the Owner is unknown or missing. Do not delete and recreate a production app as a recovery shortcut; the app guide says an app deletion cannot be restored and users lose API features. The business guide’s channel permission request path is useful when someone needs access, but a request still depends on the Master or Kakao’s support process for approval.

Protect each Kakao Account used for these roles. Kakao’s account safety guide says two-step verification can be set under Settings > Kakao Account > Two-step verification, with KakaoTalk or phone authentication and an emergency email. Kakao’s privacy guide also describes login history for the previous 90 days and a list of signed-in devices. Check those views with the account holder after a suspicious login, and sign out an unfamiliar device. A channel history entry and a Kakao Account login record answer different questions: what changed in the channel, and whether the person’s account was accessed.

For integration security, apply Kakao’s developer guidance: give each app member a suitable role, protect the Owner account with a strong password, keep client secrets on the server, and consider Allowed IP address for API calls. The app settings guide warns that IP restrictions can affect a running service; test the production egress addresses before enabling them. Channel Management History helps investigate a suspect edit, while a dealer’s own logs are needed for AlimTalk traffic outside Partner Center.

Offboard in this order: identify the replacement Master and app Owner; finish any ownership handoffs; remove the person from channel Managers and Developers app members; review Biz Wallet and other connected Kakao business assets if used; ask the dealer to revoke its separate access; inspect channel history and API activity; and test a customer chat plus a controlled transactional notice. The final test catches a broken webhook or message route before customers report it.

Mistake: inviting an agency as channel Master just to schedule posts. Kakao says Master alone can add or expel Managers, link the channel wallet, and request deletion. Give a Manager role for ordinary operations and keep Master with the company. The role boundary is in Kakao’s channel guide.

Mistake: creating a second Biz app when a channel will not connect. A Business Channel can connect to only one Biz app, and app and channel business information must match. Check both role grants and the existing connection first. Kakao’s connection checklist gives the conditions.

Mistake: treating a FriendTalk list like an AlimTalk list. The former requires channel friendship; the latter is for informational notices and may reach nonfriends. The Kakao i Connect Message reference states both recipient rules. Segment the campaign before handing phone numbers to a dealer.

Mistake: assuming the blue Business Channel mark proves every business integration is ready. The mark follows channel review. The app still needs Biz app eligibility, matching business information, permissions on both assets, and an approved connection. Kakao documents these separate gates.

Mistake: ending a dealer contract without disabling its credentials. Channel roles do not control dealer OAuth credentials. Ask for a revocation confirmation and keep a record of the last permitted send; Kakao’s official AlimTalk page sends service inquiries to official dealers.