Two ways to staff one campaign handle
A launch, a festival or a product campaign on X (Twitter) is often run by several people: someone who plans, someone who writes, someone who answers replies. Teams tend to solve this in one of two ways. Either everyone gets the password of a single campaign account, or the team buys a separate account for each member.
Both are usually wrong for a small team. Passing one password around leaves no record of who did what and breaks the moment someone turns on two-factor. Buying an account per person multiplies the cost and creates accounts that have no public purpose of their own. X has a built-in middle path, and knowing how it works tells you how many accounts to buy.
How X Delegate works
Delegate lets one X account invite other X users to act on its behalf, without sharing the password. The account owner invites people by name or @username as an admin or a contributor; the setup happens on x.com, and delegates can also work from X Pro.
The roles are clearly cut. Only the owner manages the password, phone number and login verification. Admins can invite and remove delegates and see post analytics. Contributors can post, repost, like, send Direct Messages, schedule and delete posts. Two details matter for planning: the owner is responsible for everything delegates post, and delegates keep their access when the owner changes the password, so removing someone means removing them in Delegate, not rotating the password.
That last point shapes what you look at after delivery. Once you own a bought campaign account, open the Delegate section and make sure nobody from the account's past still holds a delegated role; clearing leftover delegates belongs on the same list as logging out old sessions.
Who should own the campaign account
If you buy the campaign handle, the owner role is the decision that matters most. Pick the person who is accountable for the campaign and who will still be around when it ends, often the marketing lead or the business owner. That person secures the account after delivery, holds the recovery email and two-factor, and sends the Delegate invitations.
Put the recovery email on an address the organization controls rather than on the owner's private inbox. If the owner leaves, the company can then hand the owner role to someone else without losing the account. Write down who the owner is and where the backup code is kept, so the account does not depend on one person's memory.
When a team member needs an account of their own
Delegates need an X account to accept an invitation, but in most teams that is simply the account each person already uses. A separate bought account for a team member is justified only when that person has a public role in the campaign under a distinct identity, such as a named support handle that answers customer questions apart from the main brand voice. A quick test: would outsiders follow that person's campaign account for a reason of its own? If not, the person needs a role, not an account.
Avoid the pattern X's authenticity policy describes as coordinated inauthentic activity: several team accounts all liking, reposting and replying to the campaign's posts to make them look more popular. Team members engaging from their own accounts in their own words is normal; a set of extra accounts created to amplify the main one is not.
A hypothetical four-person launch team
A small board-game publisher plans a crowdfunding launch with four people. The marketing lead will own a new campaign handle; a community manager needs to manage the team and see analytics; a writer and a part-time illustrator only post. All four already have personal X accounts.
The publisher buys one X account for the campaign handle. After delivery, the lead secures it and invites the community manager as admin and the other two as contributors through Delegate. Nobody else learns the password. The only extra account they consider is a separate support handle for backer questions, and they decide to postpone it until the volume of questions justifies it.
From headcount to an order
Count public identities, not people: one account per distinct public voice the campaign needs, and Delegate roles for everyone who works behind it. For the listing itself, the owner's needs come first, so prefer an account whose email and phone handover is described clearly enough for one person to take full control. When the team grows later, add delegates rather than accounts; the account count only changes when the campaign needs another public voice.
On rStock you buy one product in the quantity you choose, paid from your balance, and the delivered details appear on the order page as a delivery record. If you buy more than one account, check each delivered account separately while the dispute window shown on the order page is open.
Keep X's own boundary in mind: its authenticity policy lists buying, selling and transferring accounts among the things it prohibits, so read X's rules and follow X's terms while the campaign runs and after. rStock remains independent of X and has no affiliation with it.