How to set up a sub-account on Alibaba.com

Desk take: This 4-prong garden fork inquiry has not landed on this person’s own login. Exeter is already chasing the old thread. Open Account and Permissions. Create this person. Tick inquiry. Leave product edit and ads off. Do not treat five empty accounts, a group main password, or personal WeChat as already set this week. If sales already wrote “we have five sub-accounts,” pull that sentence out of the thread.

The Exeter farm shop searched 4 prong garden fork 1200mm ash, entered the old thread, and wrote reply on THIS thread, your new person cannot log in, do not share the main password. Account settings sit at Manage your Alibaba.com account settings. The page writes you can set sub-accounts and change email and password. It does not audit whether this person owns this fork, and it does not treat a shared main login as already set.
The inquiry treasure chest sits at Inquiry treasure chest. The page writes who can see a thread and how to assign. It does not prove five empty logins let this person enter the old thread. How-to-sell sits at How to start selling. The page writes reply soon. Reply soon is this person’s own login, not a faster drop of the main password into the group.

Monday 09:50, an Exeter farm shop asked on the old thread for 4 prong garden fork 1200mm ash handle, 800 pcs, then added reply on THIS thread, your new person still uses the main login, do not share the password or open a new chat. Sales wrote we have five sub-accounts, he will use the main account Friday. Twelve minutes later ops dropped the main password into the sales group. Buyer WhatsApp: I asked this thread. A shared password is not a sub-account.

Hong Kong shops have this meeting in the week someone heard “reply soon” as “give the new hire the main login first.” Sales likes five empty accounts to cover the owner. Ops likes to treat a group password as already set. The warehouse likes one internal number, GF-4-1200-ASH. Exeter walked in from the front. They already stopped on the old thread. “We have many sub-accounts” does not fill which pages this person can enter. Corpable Marketing Limited is a Hong Kong Alibaba.com official channel partner. An advisor can sit with you and read the ticks. The advisor cannot set the login for you, and cannot promise the box the day you set it.

Login already there, box empty, owner is someone else: sub-account cannot see the inquiry. Rights already on, price changed: sub-account changed the price. Departure and stolen main: sub-account security. Whole-shop buttons grey: account limited. First reply still has not answered spec: how to reply to an inquiry. Who can change the daily cap: how to control ad budget. Exeter did not ask assignment, revoke, theft, a grey button, a first reply, or the budget cell. They asked how to set this person’s login.

The new hire already started. The main password is still in the group

Anyone who can enter My Alibaba, do not drop the main password into the group first. Open Account and Permissions. See whether this person already has their own login. Sales saying “we already set it” is not enough. If a sub-account can only see their empty box and cannot enter Account and Permissions, copy the original to the person who can create. Before you write back, do not send five empty logins as already set.

Exeter’s original wrote 4 prong, 1200mm, ash, 800 pcs, THIS thread, do not share the main password. They did not write bid too low. They did not write shop looks empty. Sales forwarded “the new hire needs an account” into the ops group, so ops hung the main password. The store lead made them paste the original back. Pasted back, you see they want this person on the old thread, not another welcome. A full empty-login list does not fill that sentence. The same afternoon Plymouth asked a 3-prong. Truro asked a stainless handle. Three threads, three forks: three owners. Fuse them into one “whole-shop shares the main login,” and all three will think you sell passwords.

If this person still has no email, do not share the main login. Putting an empty mailbox on the main writes an unnamed person as already set. A draft can click. That is not Jinhua naming this fork. Rights write inquiry. The group sends the main. They will order on the main. Do not send the wrong rights unless name, inquiry tick, and this old thread face.

Inquiries still arriving is not a sub-account already set. Someone sees an inquiry and writes see, five sub-accounts. Exeter will plan next week’s farm-tool bay on that sentence. Response is send time. Set is this person’s tick. Data Advisor response rate can be green. Green does not let the new hire into the old thread. Promising we already set on a green light adds a sentence that does not exist: five empty logins equal set.

The 4-prong 1200mm ash is this inquiry. Neighbour 3-prong is not. Someone opens a neighbour shop, sees a longer sub-account list, and sends it to Exeter. Wrong shop. Name the shop entity before you speak. Tine count was not locked. I need 4 prong, then a follow-up adds 3 prong: that locks another grade outside setup. Tine count sits in attributes. The setup sentence still writes five sub-accounts. What you check is whether this person has the inquiry tick. Two words changed do not turn a main password into set.

How-to-sell writes reply soon. Reply soon is this person’s own login, not a faster drop of the main into the group. Account settings writes you can set sub-accounts. Can set is not already set. Response-rate green only proves someone clicked send. The sender may be a departed colleague’s auto-welcome that writes we have five sub-accounts. Green does not name this fork.

Sales opens this inquiry and screenshots Account and Permissions and already-sent on phone and desktop. If the two screens disagree, write from the screen that has this person’s name and the inquiry tick. Keep the shots in this inquiry clip. No old screen, and next week you will not know which sentence they saw when they said a shared password is not a sub-account. Do not send a preview link to the buyer. Preview is not the front.

Sales marked the thread processed. The original is still there. Outward it still says we have five sub-accounts. Processed does not prove setup. The store lead spot-checks processed threads this week that carry garden fork or 4 prong. Each must point at this person’s name, the inquiry tick, and whether the old thread can be entered. Cannot point: send it back to unprocessed. Another 4-prong need in the RFQ hall is not this setup. If the list has none, glance at the hall. Do not treat two stacks as one.

This person faces three ticks first: a login, inquiry on, price edit off

Keep the setup short. The sentences that can go out: we created a sub-account for [name] this week, inquiry on, product edit off, ads off, main password not shared. They asked this person on the old thread. First answer whether the login exists. If yes, write the name and the inquiry tick. If not, write we are creating this person's sub-account this week. Do not invent “official must share the main first.”

A login follows the name Account and Permissions shows today. The name must face the badge and the inquiry owner. If they do not face, write we are checking this person's account this week. Membership paid to ALIBABA.COM HONG KONG LIMITED buys membership and showcase quota. It does not turn a sub-account into already set, and it does not buy an official box-arrival day. Hong Kong-channel Export Tong is about HKD 39,000, Gold about HKD 108,000. That is the year fee, not a licence to set the login for you. An advisor does not recite those two numbers as “paid, so five empty accounts count as set.” Pricing sits at Membership pricing. It writes packages by region. It does not audit which tick this person holds.

Inquiry can open. Inquiry, opportunity, assignment: at least one of them can open the old thread this week. Cannot open: treat as not set. Do not write he will see it Friday. Friday makes them read the new hire as already on the old thread. The chest writes assignment. Assignment is the next step — see the inbox-empty page. Here the login is still missing, so there is nothing to assign.

Do not tick product edit and price first. Week one this person replies on the 4-prong fork. They do not need to change FOB. Price rights on: the revoke page. Here they are still off. Leave them off. Ads the same: leave off. Who can change the daily cap: the budget page. Here the budget cell is not this person’s yet.

Save against the letter that went out. The backend draft still writes five sub-accounts. The front already said a shared password is not a sub-account. Write back from the buyer’s screen. After the change, write back on this thread: sub-account now [name], inquiry on, main password taken off this thread. An advisor does not invent “backend equals front.” Account settings has no such line.

If night shift already pulled the main password from the group and this person is still not created, Exeter’s favourites may still hold old we have five sub-accounts. Check on-site sent first. If yes, write we created [name] on this thread. If not, write we are creating this person's sub-account this week, do not treat five empty accounts as set. Do not write we shared the main login so you know we are staffed. The main is not a sub-account.

Thursday the Jinhua floor already pulled GF-4-1200-ASH off the rack and faced it. 4-prong, 1200 mm, ash. Write that on this inquiry. Do not write it in the group as “already set.” The group’s faced, Exeter cannot see. What they can see is the on-site setup sentence. Floor faced, Account and Permissions still missing this person: treat as not set. Do not cover the owner with “the floor already staged forks.” Staging is a table in the plant. Setup is the screen the farm shop opened. If finance already accrued headcount on “Friday five logins,” that is a book entry. Do not let we have five sub-accounts appear in the inquiry.

Five empty logins and a group main password do not fill Exeter’s sentence

A neighbour backend “12 sub-accounts” looks brighter. Ops drops the screenshot in the group: “see, they split.” “Split” makes Exeter think they cannot see you unless they take the main first. The neighbour is bright on a name list. Exeter asked this person on the old thread. A wrong-shop screenshot is harder to walk back than empty — empty, they still ask how to set; a screenshot, they order as if they must pre-stock.

Smart welcome offers another string: Dear customer we have a large team. Response rate may go green. Green response is not already set. The chest writes assignment as who can see. The page does not prove green lets you keep a shared main, and it does not lock a deal multiple. When the light is red, face the original first. Do not paste a fake badge to pad response.

Night shift wrote “no main login, no reply” into the duty sheet. Strike that line. Not giving the main only proves this person still has no login. Exeter asked the old thread. Change the sheet to account pending / [name] inquiry on. The floor already staged 3-prong and 4-prong for a “Friday whole-shop main.” Staging is the plant. Outward you still only let this person into this 4-prong thread. Goods staged, duty is likelier to say already reserved both. Already reserved does not prove setup.

A WhatsApp add-on we created [name], inquiry on, main password not shared is fine. After it, write the same sentence back on this on-site thread. Locked outside, welcome still five sub-accounts: they hold two sets. Two sets, and next week the person who favourited the shop still reads the main. The sample room still holds old 3-prong. People on the rack can argue tine count. Do not write 3-prong into the follow-up as if 4-prong were already set.

A new mailbox, same fork, I still got the main login, is another conversation. Copy the old setup sentence back onto the old thread. Do not retell five sub-accounts Friday in the new mailbox. The new conversation has no old state. What they favourited is still sales’ daytime shared password. An advisor WeChat “I will ask the platform to weight you” is not a page, and does not prove setup. Write on this thread: chat has no official box-arrival day.

Top exhibit, pinnacle, agency, if someone already added them into a “sub-account plan,” those are separate products. Some shops never bought them. Week one, those receipts are not on the table. Pitching the package advertises a service that does not exist yet. Growth numbers in seller cases on an intro page are not your shop’s result. The factory in the case is not this Jinhua farm-tool mill, and not this Exeter farm shop.

Account settings writes you can set sub-accounts. It does not write a shared main as already set

Open Manage your Alibaba.com account settings and read the original. Sales retelling “official says reply soon so give the new hire the main first” is not having read it. The page writes setting sub-accounts and changing email and password as possible. It can prove this setting exists. It cannot prove Exeter’s thread is already set, and it cannot write a shared main as must-send. Response green, this person may still have no inquiry tick.

The chest writes who can see and how to assign as a note. A note is not five empty logins. How-to-sell writes reply soon. Reply soon is this person. The response lesson sits at Inquiry Quick Response Rate. It writes reply within 24 hours. The reply is this person on the old thread, not a we have five sentence. Services sit at Seller services and list tools. The list has accounts, and inquiries. The list is not “you must share the main first.”

If the group only holds rumours — “an international shop needs five sub-accounts to look real,” “no main, no inquiries” — treat it as nobody opened an official page. Outside posts with “setup conversion 8 is a pass” or “five logins, box in three days” are not words on your page that face this fork. Do not write them to Exeter, and do not write them into the GM weekly. An advisor does not invent setup conversion, an official headcount, or a box-arrival day. Stars dropped: that page. Here stars may not have dropped. If they did, a seventh main-password send does not lock them back.

Box still empty: the inbox-empty page. Box written, here you still give this person a login first. Price already changed: the revoke page. Change is there. Here product edit is still off. Departure walked out: the security page. Security is there. The person is still in post. Account limited: the limited page. Buttons lit, login still missing. How to write the first reply: the reply page. First reply is there. The login still has to exist. Who can change the cap: the budget page. The budget cell is not this person’s yet.

Corpable on the page only checks whether you copied the account-settings page and the chest original, or a group-invented must-share-main. Copied someone else’s “five logins, box must arrive”: strike it. An advisor will not read account settings as “official says you must drop the main into the group first.” If the rules centre currently posts on accounts or permissions, copy the title and keep it. A notice is not which 4-prong this shop should give to whom. partner.alibaba.com can confirm Corpable is an authorised channel. Directory green, setup may still be a main password, or already ticked. Authorisation is not setting for you, and not opening a consulting invoice to stamp an inquiry.

The inbox-empty page stops on a login that already exists. Exeter already asked this person on the old thread, how to set. The assignment page does not audit the fact “login still missing,” and cannot write shared password as a step. The revoke page covers rights already on. Rights still off, do not turn them on. Where open-store stuck: the open-store flow page. Live is not a reason to send another unsettable welcome.

When an advisor arrives, open this person’s ticks first

An advisor arrives. Warehouse puts the GF-4-1200-ASH card on the table. Ops spreads the neighbour twelve-login screenshot. Sales drops Exeter’s English in the middle. The card has one number. The screenshot’s count is not this person. The English asked this thread, this person. When the three do not face, open Account and Permissions and see whether this person has the inquiry tick. Then argue Friday. Argue without the tick, and you argue someone else’s name list.

When you check, write only what is on the page. Inquiry: 4 prong, 1200mm, ash, 800. Account and Permissions: name, inquiry, product edit, ads. Already-sent: whether the main password was pulled off this thread. Outside those three lines — “close enough for a farm-tool word,” “we asked the AM to weight us” — do not write them to Exeter. Close enough is not a page. Asked is not a page. What tine count is on the page is the tine count this person enters. After the sentence changes, write it back on this thread. The old words are not void — Exeter is still planning the farm-tool bay on old we have five sub-accounts.

Farm-tool mills like to give the main login on day one. Given, it looks like they have done export. Exeter’s thread runs the other way: they want this person’s own login written back on-site before they put 800 forks on a farm season. Habit reversed, sales still writes five sub-accounts Friday, the thread splits. The main can stay with the store lead. Pull the password sentence off the follow-up. Preparing a badge and saying already set are two sentences. The first is fine. The second is not, while the inquiry tick is empty.

The buyer side opens the old thread and sees a fork, not your group’s headcount screenshot. An advisor sometimes asks ops to log in with this person’s new account and see whether the old thread is in the box. Box empty, stop arguing “five logins should already be enough.” Should be enough and seeing an empty box differ by this one person. If phone and desktop already-sent disagree, write back which end saw which sentence. Both ends five sub-accounts: treat as not set. Do not fuse them into already professional.

This Jinhua mill likes PI, contract, and Trade Assurance order to face on spec. Outward still we have five sub-accounts, the three sets cannot face. Someone already wrote the PI as 4-prong 1200mm ash and wrote a new HKD account, and still has not given this person a login. Spec written right, setup called done, Exeter still does not know who can enter the old thread. Paperwork can prepare. Outward setup cannot be five empty logins. Prepare is a table in the plant. Fork is a farm-season slot. A messy table can be tidied. A wrong slot waits until next month.

Corpable does not collect. An advisor does not touch your main-account password. The year fee still goes to ALIBABA.COM HONG KONG LIMITED. Sitting beside permissions is fine. The person who decides which tick goes on must hold account rights in the shop. After the look, screenshot at once: name, inquiry tick, product edit off or on, the click time. Keep the shot on Exeter’s thread and on the ops WeChat. No shot, and night shift will again call the still-empty tick “should already be five logins.” Should is not a page.

If a sub-account wrote waiting to create [name] by day and night shift put the welcome back to we have five sub-accounts, that is two stories. Leave one name on the list to change this sentence, then write it back on this thread. Two people each answering setup, the buyer refreshes and sees login and main password jump: messier than a main password the whole time.

Reply to Exeter: which pages this person can enter this week

The person who may speak opened Account and Permissions and faced this person’s inquiry tick. A sales inquiry sub-account without account rights must not say in the group I already checked how to set. Before speaking, at least reciting name, inquiry tick, product edit off or on, and whether the main was pulled off this thread. Cannot reciting: say the main account is still looking at permissions. Do not report “five logins Friday.” Do not add a “sub-account pass count” column to the duty sheet. Account settings and the chest do not give an official how-many. Add the column, and night shift will fill 5.

Keep the reply to Exeter short. Login faced, inquiry on, main pulled: we created a sub-account for [name], inquiry on, product edit off, main password not shared on this thread. Not finished: we are creating this person's sub-account this week, we are not sharing the main login as the setup. Do not add traffic will jump. Do not add already reserved both forks. Do not add any person can log in. Gold does not prove setup. The original already wrote I asked this thread. A shared password is not a sub-account. If the duty board says “main password pending,” the board is internal, and night shift will answer five sub-accounts Friday from it. Change the board to account pending / [name] inquiry on.

A new salesperson first reads whether this inquiry has a setup original and whether five sub-accounts went out. No screen: they may only say we are creating this person's inquiry login. Monday, if last week already locked five logins Friday outward, void it on this thread first, then see whether the tick still holds. Not voided, the buyer holds two sets. Birmingham’s empty box, Chicago’s revoke, Malmö’s selection, are not Exeter’s setup. Neighbour ticket green, this shop’s person still empty: say them as two facts.

Exeter purchasing already wrote “the 800 4-prong forks that can enter the old thread” into next week’s farm-tool bay. The bay is their calendar. You cannot fill it. Reply with the setup state so they can change the plan to account pending or sub-account [name] inquiry on. If an inspection house issued a material page with the carton, the material page can stay. A material page is not setup. Do not change HS to face setup. Classification is another job. Duty-group forwards of “international shops need five sub-accounts” come from outside posts. A post is not Account and Permissions. If finance wants a “setup diagnosis fee” on this grade, the account can open. Outward they still have to see this person’s tick screen. Diagnosis open, duty is likelier to say audit on so share main. An advisor is not an account desk.

Night shift wrote “information score 4.6 so we can send the main first” into the duty sheet. Strike that line. Information score only proves field score. The forging line booked the next shift on a reply. Forging day is their calendar. The inbox-empty page faces an empty box. Here the login is still missing. The revoke page faces rights already on. Here they are still off. A review meeting should not project the welcome. Project the inquiry-tick cell and the sentence that pulled we have five sub-accounts. Welcome hot, this person still empty.

This inquiry still hangs HK invoice OK. Letterhead can walk the payment page. The payment page does not write letterhead as already set. Last reply to Exeter writes only what faces on the page: whether this person has a login, whether inquiry is on, whether the main was pulled off this thread. A slogan does not face a page. The store lead leaves these sentences on this inquiry. Night shift may only repeat them. If the clip still holds we have five sub-accounts, he will use the main account Friday, strike it before duty. Unstruck, the old sentence flies again. How to control ad budget is another page. Do not tick ads for the new hire on this ticket.

Questions teams actually ask

Can the inquiry-not-in-my-inbox page be how to set a sub-account?

That page already has a login. The box is empty. It asks who owns the thread. Exeter’s person still has no account. Assignment sits there. Here first create the login and tick inquiry.

Is the sub-account-changed-price page the same sentence?

That page already has rights on. The price was changed. Pull the rights first. Here you have not ticked product edit for this person. Revoke sits there. Here do not tick price first.

The sub-account security page — use it as the setup steps?

That page covers departure, stolen main logins, and agency overreach. Here the person is still in post and the login is not split. Security sits there. Here first give this person their own account.

Account settings writes you can set sub-accounts. Does sharing the main login count as already set?

The page writes you can set sub-accounts and change email and password. It does not audit whether this person owns the 4-prong fork, and it does not treat a shared main password as already set.

The inquiry treasure chest writes assignment. Do five sub-accounts look more professional?

The chest writes who can see a thread and how to assign. It does not prove five empty logins let this person enter the old thread, and it does not lock a must-arrive day.

Can Corpable set the sub-account for us and guarantee the new hire sees inquiries this week?

We cannot set it for you, and we cannot guarantee the box. Corpable Marketing Limited is a Hong Kong Alibaba.com official channel partner, not an account desk. An advisor can sit with you and see this person’s ticks. Membership still goes to ALIBABA.COM HONG KONG LIMITED.