Content strategy 5 min read
X Delegate: give someone account access without sharing your password
Choose Contributor or Admin for X account delegation, check the invited handle and permissions, and remove access explicitly when the collaboration ends.

How do you give someone access to your X account?
Use X Delegate on x.com to invite the person’s own account as a Contributor or Admin, then have them accept the invitation. X documents delegation as a way to collaborate without sharing passwords. Choose the role from the work they must do, not from an informal job title. Contributor is not a draft-only or approval-only role: X lists posting, Direct Messages, scheduling and deleting posts among its permissions. Admin adds member-management powers and access to post analytics. If you only need someone to suggest wording, exchange drafts outside the account instead of assuming Contributor requires your approval before publication.
On 23 October 2026, we compared searches about delegated access, Community Notes and missing scheduled posts. Delegation results mixed X’s organic account roles, Ads access and third-party tutorials. This guide answers the organic account invitation-and-removal task using X’s current Help pages. The search evidence is qualitative; no measured keyword demand, difficulty or ranking outcome is claimed. We have not invited anyone into a reader’s account. Verify the controls and permissions shown in your actual account before granting access, and keep Ads permissions separate from this workflow.
X Help: Delegate roles, invitations and removalX Help: separate multi-user permissions for X AdsShould you choose Contributor or Admin?
X’s role definitions give the owner control of the password, phone number and login-verification settings. Both owners and Admins can manage delegates. Admins can invite others as Admins or Contributors, act for the account, schedule and delete posts, create lists and collections, and view post analytics. Contributors can also act for the account, including posting, reposting, liking, sending Direct Messages, scheduling and deleting posts, and creating lists and collections. A less powerful role can still expose consequential actions; the name Contributor does not mean read-only access.
For a fictional solo design business, a collaborator who must publish reviewed updates may need the documented Contributor actions but no reason to invite more people. A person responsible for maintaining the account team may need Admin membership controls. If the task is merely editing a paragraph, neither role is necessary for that task. Write a small permission brief before inviting: account handle, collaborator handle, permitted work, decisions needing agreement, support-message boundaries and the date you will review access. This is your working agreement, not a claim that X enforces custom approval rules or disables permissions you have chosen not to use.
Choose clear roles for personal and product accountsKeep private customer material out of public postsHow do you invite and check the right person?
On x.com, sign in to the account whose work you want to delegate. X’s Help directs you to Your account, Security and account access, X Delegate, then Invite a member. Enter the person’s name or @username, select Contributor or Admin, and send the invitation only after checking the exact handle and role. The recipient receives an email and an invitation within Delegate. They can open Accounts delegated to you, inspect Pending invites, then accept or decline. Menu wording can change, so follow the current interface and the linked Help page rather than trying to reproduce an old screenshot.
After acceptance, check the member entry and role from the owner’s account. Have the collaborator confirm the delegated handle before taking any action, especially if they also manage a personal profile. Agree on a reviewed first task; do not publish a test post merely to prove access when reading the accepted role and preparing work is sufficient. If an invitation cannot be sent, X says the recipient may have a setting preventing delegation invitations. Ask them to inspect their own setting rather than requesting their password or verification code. An invitation that was sent is not proof that it was accepted or that the intended person has begun the work.
Review the final post before schedulingKeep release claims accurate when sharing updatesHow do you remove access when the work ends?
From the owner or authorized Admin account on x.com, open X Delegate and Members you’ve delegated to. Find the exact member, choose Change role or Remove from account as appropriate, and confirm. Then review the member list to verify the intended result. A delegate can also leave through Accounts delegated to you, choosing the account and Leave account. X explicitly says changing the owner’s password does not remove delegates. Do not treat password rotation or the end of a contract as confirmation that delegated access has ended.
Use a short handover record: removed handle, account, date, remaining members and any unfinished work. Separately inspect scheduled posts, pending drafts and private support conversations that need an owner; removal of a person is not evidence that their scheduled work was cancelled or reviewed. If another publishing tool was connected, review its own access separately rather than assuming X Delegate controls every integration. X Ads has its own multi-user roles and permission scope, including billing-related access for Ads administrators. Use the relevant interface for the access you actually granted. Keep account maintenance proportionate, verify the result, and avoid sharing the owner’s login as a shortcut.
Verify saved schedule times and actual publicationKeep private account archives in appropriate storage